Skip to content
Home

Migrations

Write to your bucket. That's the migration.

Cardinal is S3-first. Telemetry lands in your object storage from the OpenTelemetry Collector, Vector, Fluent Bit, or code you wrote yourself. A stateless query engine sits downstream, serving Grafana, the Cardinal UI, and agents in Claude, Codex, Gemini, and Cursor. There's no vendor storage to trust, and no proprietary agent to install.

Your Telemetry Datalogs · metrics · tracesObject Storageyour S3 · GCS · Azure Blob bucketthe boundaryCardinal Query Enginestateless · elastic · sits downstream of S3runs in your VPCClaudeCodexGeminiCursorGrafanaCardinal UIConsumers

Pick the source you already run.

Any of these paths lands OTLP-protobuf in your bucket. Pick the one you already run to see the recipe.

Point a writer at a test bucket and see it work.

The fastest way to evaluate Cardinal is to spin up a bucket, drop some telemetry in, and query it. Everything after that is optional.

Start a migrationRead the docsCompare vendors →