Bring your own
storage.Start Free TrialBook a Demo
-
Written as Parquet
-
Remote query
-
No retention limit
-
No rehydration cost
Stored once. Queried remotely, never moved.
Coralogix analyzes every event in-stream and writes logs, traces, metrics and profile data to your object storage. Query it with the DataPrime engine, against the files in your bucket. Nothing to rehydrate, nothing to reindex, and no overage charges.
Parses, enriches and alerts on every event in-stream, before anything is stored.
Routing rulesFile each event into the dataset its rules name, creating new datasets as data arrives.
Every event lands as open files, in the dataspace it belongs to.
Object storage you own, in your own cloud account. Dataspaces group your datasets by how you use them, like databases and tables.
Open files in the region of your account, encrypted with your key. Logs, traces and metrics arrive in the default dataspace; routing rules file them into yours.
Receives the forwarded stream.
Read the same files with any Parquet engine.
DataPrime reads the files in your bucket directly. No rehydration, no reindexing.
Trusted by teams in regulated markets
Rather than navigating backup archives and painfully restoring data, Tradeweb’s forensic analysis team can swiftly access compliance-level logs directly in their archive with rapid Archive Querying.
Read case study →average daily data volume
rehydration before a forensic query
while keeping more data
Owned. Open. Organized.
Owned
Encrypt the bucket with your own key. Coralogix writes through a single identity you grant, scoped to one bucket by a policy you control. Retention is a policy you set, with no ceiling.
Open
Logs and traces land as Parquet, partitioned by day and hour. Metrics rest in an open, machine-readable format. Any Parquet reader opens the archive, with or without Coralogix.
Organized
Dataspaces behave like databases, datasets like tables. Every dataset inherits its path, retention and access rules from its dataspace. Routing rules create new datasets as data arrives.
Data you own is data you can use
Archived logs open from Explore with DataPrime or Lucene. No reindex, no rehydration ticket.
Parsed, enriched events go on to your own Kafka cluster, filtered with a DataPrime expression.
Background queries write their results to summary datasets you can chart and join later.
Keep compliance data for as long as policy says, and search it the day someone asks.
Connect a bucket
Run the Coralogix template. It creates the bucket and the policies it needs. Read the guide →
Set the region and bucket names, add your encryption key, and apply. Read the guide →
Create the bucket and grant the Coralogix archive identity access to it. Read the guide →
Bring your own storage
Keep every event,
in your own bucket
Connect a bucket in your own cloud account and Coralogix writes there from the first event.
Open files, any reader
No rehydration, no reindexing
Set by your policy, not your plan
