Skip to main content
Docker Compose runs a lightweight, single-node Laminar on one machine: frontend, app server, PostgreSQL, ClickHouse, and Quickwit for full-text search. It is the fastest way to self-host for local development and small deployments. For the full production stack (with RabbitMQ, Redis, and a dedicated processing consumer), use the Helm chart on Kubernetes.

Install

The dashboard is available at http://localhost:5667/. Create a project through the onboarding flow, then grab your project API key from project settings.
docker compose up -d brings up the lightweight stack. For a heavier single-node setup closer to production, the repo also ships docker-compose-full.yml (docker compose -f docker-compose-full.yml up -d), which adds RabbitMQ for queued span processing.

Point the SDK to your instance

Initialize the SDK with the local app server’s host and ports. baseUrl / base_url is the scheme and host only; the ports go in httpPort / grpcPort.

Access control

By default, any user can sign in to your self-hosted instance. To restrict access to specific GitHub users, enable GitHub OAuth:
Then create an allowed-emails.json file in your project root:

AI features

Chat-with-trace, SQL-with-AI, and Signals need an LLM provider. Set the provider and key in your environment before bringing the stack up:
The Helm chart exposes the same variables plus per-tier model overrides and OpenAI-compatible gateways. See the configuration reference for the full set.

What’s next

Kubernetes (Helm)

Move to a production Kubernetes deployment when you outgrow a single node.

Configuration reference

AI features, Signals, Slack, OAuth, storage, and TLS.

Start tracing

Send your first traces to the local instance.

View traces

Read the transcript view instead of a tree of span names.