Skip to main content
Laminar is open-source, so you can run the full observability and debugging stack in your own infrastructure. Self-host with Docker Compose for local and single-node setups, or the Kubernetes Helm chart for production. Docker Compose runs a lightweight stack (frontend, app server, PostgreSQL, ClickHouse, and Quickwit); the Helm chart runs the full production stack, adding RabbitMQ, Redis, and a dedicated processing consumer.

OSS, Helm, or Laminar Cloud

There are four ways to run Laminar, and they differ only in how Signals and Slack are packaged and in the support that comes with them. Everything else (tracing, search, dashboards, evaluations, the debugger, AI features) is identical across all of them.
  • OSS: the open-source images, run with Docker Compose. Signals and the Slack integration are not included.
  • Helm: the Kubernetes Helm chart. The same platform as OSS, packaged for production Kubernetes.
  • Helm + license: the same chart with an enterprise license key. Unlocks Signals, signal event clusters, and email and Slack alerts, plus priority support and the option to have the Laminar team run your deployment for you (see Managed self-hosting).
  • Laminar Cloud: the fully managed service at laminar.sh. Everything is included and kept up to date for you.

Feature comparison

Tracing & platformOSSHelmHelm + licenseLaminar Cloud
Trace ingestion (OTLP)
Full-text trace search
Custom dashboards
SQL editor
CLI
Evaluations
Datasets
Labeling queues
Browser session recording
Agent debugger
MCP access
AI featuresOSSHelmHelm + licenseLaminar Cloud
Chat-with-trace
SQL-with-AI
Signals--
Signal event clusters--
Alerting & integrationsOSSHelmHelm + licenseLaminar Cloud
Email alerts--
Slack notifications and alerts--
Security & operationsOSSHelmHelm + licenseLaminar Cloud
OAuth sign-in (GitHub, Google, Azure AD, Okta, Keycloak)
Server-side PII redaction
Data stays in your infrastructure-
Managed upgrades--
SupportOSSHelmHelm + licenseLaminar Cloud
Community (Discord)
Priority support--
Operated for you by the Laminar team---
Signals, signal event clusters, and email and Slack alerts require an enterprise license key (LMNR_LICENSE_KEY). The Slack integration additionally uses Laminar Cloud’s brokered OAuth flow. See the configuration reference for details.AI features (chat-with-trace, SQL-with-AI, and Signals) need an LLM provider key on self-hosted deployments; on Laminar Cloud they are included. See AI features and LLM provider.

Managed self-hosting

With an enterprise license key, the Laminar team can take care of running your self-hosted deployment for you. We operate it inside your own AWS or GCP account, close to a forward-deployed model: your data and the entire stack stay in your infrastructure, while we handle provisioning, scaling, upgrades, and day-to-day operations under scoped access to your environment. This is the option for teams that want the data-residency and compliance benefits of self-hosting without standing up and maintaining the platform themselves. Contact us to set it up. If you just want to start tracing, Laminar Cloud is the fastest path: sign up, create a project, copy the project API key, and set LMNR_PROJECT_API_KEY. The rest of this section covers running Laminar yourself.

Choose a deployment

Docker Compose

Single-node setup for local development and small deployments. One command brings up the whole stack.

Kubernetes (Helm)

Production deployments on EKS or GKE. Persistent storage, S3-backed ClickHouse, load balancers, and TLS.

Configure your deployment

The Helm chart exposes every paid and optional feature through values in laminar.yaml. See the configuration reference for the full surface:

What’s next

Start tracing

Point the SDK at your instance and send your first traces.

View traces

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