Skip to content
Oriel

Start with Oriel

Oriel is built around OTLP and a fixed scope hierarchy. A working deployment has one oriel binary, PostgreSQL for metadata, ClickHouse for telemetry, and Valkey for runtime state.

The Oriel overview screen for the _oriel self-observability workspace, showing 24 hours of throughput, latency, and service data.

What Oriel stores

Section titled “What Oriel stores”

Oriel organizes telemetry by a fixed hierarchy:

workspace -> project -> environment -> service

Every telemetry row is resolved to a workspace, project, environment, and service during ingest. The workspace is the tenancy boundary; projects and environments are the operational slice users work inside.

What you need

Section titled “What you need”

For the local path:

  • Docker and Docker Compose
  • Ports 6743, 4317, 4318, 5432, 8123, and 9000 available locally
  • A browser for the UI

For a production path:

  • PostgreSQL for metadata
  • ClickHouse 25.3 or newer for telemetry
  • Valkey for runtime cache/pub-sub
  • A stable oriel.toml or equivalent ORIEL_* environment variables
  • TLS termination, either native Oriel TLS or a proxy
  • A migration step before serving a new binary

Where to go next

Section titled “Where to go next”

For the first local run:

For day-to-day use: