90-day evaluation — no credit card required

All your telemetry.
One platform.

Unified metrics, logs, and traces in a fully managed cloud platform. Built in Rust for speed. OpenTelemetry native. Start with a free evaluation.

Start Free Evaluation Read the Docs

OTLP

OpenTelemetry native

Query surfaces

Signals unified

Cloud

Managed by PackDB

Sending data in 2 minutes

Point your OpenTelemetry collector at PackDB. That's it.

yaml

# otel-collector-config.yaml
receivers:
  otlp:
    protocols:
      grpc:
      http:

processors:
  batch:

exporters:
  otlphttp/packdb:
    endpoint: "https://ingest.packdb.io"
    headers:
      x-api-key: "<YOUR_PACKDB_API_KEY>"
    compression: gzip

service:
  pipelines:
    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlphttp/packdb]
    logs:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlphttp/packdb]
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlphttp/packdb]

Then verify your first telemetry and run your first queries in the quickstart.

The workflows, not the feature list

Every card is something you do in the product today — and links the proof.

The PackDB service dependency graph highlighting an erroring service with its request rate and latency. — The service graph — where most investigations start. Real workspace telemetry.

Investigate from the service graph

Spot the erroring service in the dependency map, open a representative trace, and jump from a span straight to the logs it emitted — or to that service's metrics over the same window. One platform, no tab-hopping.

Watch the investigation loop

Send data in minutes

Point your OpenTelemetry collector at PackDB with one exporter block, then verify each signal is flowing from the workspace readiness checks.

Follow the quickstart

Keep your Grafana dashboards

Provision Prometheus, Loki, Tempo, and Jaeger datasources against PackDB with one API key — existing Prometheus dashboards import unchanged.

Set up the datasources

Query in your language

PromQL for metrics, LogQL for logs, TraceQL for traces, and SQL over FlightSQL or REST for cross-signal analytics — plus a Jaeger-compatible API for the tooling you already run.

Browse the docs

Link evidence in incidents

Use Copy link in the explorer to preserve the query and time window — or the selected trace and span — behind an incident claim.

See it in the product tour

Predict your bill

One included telemetry bucket across all three signals and a single flat overage rate — the whole usage charge fits in one line of arithmetic.

See full pricing

Works with your existing stack

Compatible APIs mean no migration headaches.

OpenTelemetry

Prometheus

Grafana

Jaeger

LogQL

TraceQL

SQL (FlightSQL / REST)

Start observing in minutes

90-day evaluation with 5 GB/month included. No credit card required.

Start Free Evaluation View Pricing

All your telemetry.One platform.