> ## Documentation Index
> Fetch the complete documentation index at: https://laminarai-docs-lam-1786-dataset-cli-lmnr-cli.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Self-hosting Laminar

Laminar is [open-source](https://github.com/lmnr-ai/lmnr), so you can run the full observability and debugging stack in your own infrastructure. Self-host with [Docker Compose](/self-hosting/docker-compose) for local and single-node setups, or the [Kubernetes Helm chart](/self-hosting/kubernetes) 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](https://github.com/lmnr-ai/lmnr), run with [Docker Compose](/self-hosting/docker-compose). Signals and the Slack integration are not included.
* **Helm**: the [Kubernetes Helm chart](/self-hosting/kubernetes). The same platform as OSS, packaged for production Kubernetes.
* **Helm + license**: the same chart with an [enterprise license key](mailto:founders@lmnr.ai). 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](#managed-self-hosting)).
* **Laminar Cloud**: the fully managed service at [laminar.sh](https://laminar.sh). Everything is included and kept up to date for you.

### Feature comparison

| Tracing & platform        | OSS | Helm | Helm + license | Laminar 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 features                      | OSS | Helm | Helm + license | Laminar Cloud |
| -------------------------------- | :-: | :--: | :------------: | :-----------: |
| Chat-with-trace                  |  ✓  |   ✓  |        ✓       |       ✓       |
| SQL-with-AI                      |  ✓  |   ✓  |        ✓       |       ✓       |
| [Signals](/signals/introduction) |  -  |   -  |        ✓       |       ✓       |
| Signal event clusters            |  -  |   -  |        ✓       |       ✓       |

| Alerting & integrations                           | OSS | Helm | Helm + license | Laminar Cloud |
| ------------------------------------------------- | :-: | :--: | :------------: | :-----------: |
| Email alerts                                      |  -  |   -  |        ✓       |       ✓       |
| [Slack](/signals/alerts) notifications and alerts |  -  |   -  |        ✓       |       ✓       |

| Security & operations                                                  | OSS | Helm | Helm + license | Laminar Cloud |
| ---------------------------------------------------------------------- | :-: | :--: | :------------: | :-----------: |
| OAuth sign-in (GitHub, Google, Azure AD, Okta, Keycloak)               |  ✓  |   ✓  |        ✓       |       ✓       |
| [Server-side PII redaction](/self-hosting/configuration#pii-redaction) |  ✓  |   ✓  |        ✓       |       ✓       |
| Data stays in your infrastructure                                      |  ✓  |   ✓  |        ✓       |       -       |
| Managed upgrades                                                       |  -  |   -  |        ✓       |       ✓       |

| Support                              | OSS | Helm | Helm + license | Laminar Cloud |
| ------------------------------------ | :-: | :--: | :------------: | :-----------: |
| Community (Discord)                  |  ✓  |   ✓  |        ✓       |       ✓       |
| Priority support                     |  -  |   -  |        ✓       |       ✓       |
| Operated for you by the Laminar team |  -  |   -  |        ✓       |       -       |

<Note>
  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](/self-hosting/configuration#slack-notifications) 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](/self-hosting/configuration#ai-features-and-llm-provider).
</Note>

## 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](mailto:founders@lmnr.ai) to set it up.

If you just want to start tracing, [Laminar Cloud](https://laminar.sh) 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

<CardGroup cols={2}>
  <Card title="Docker Compose" icon="container" href="/self-hosting/docker-compose">
    Single-node setup for local development and small deployments. One command brings up the whole stack.
  </Card>

  <Card title="Kubernetes (Helm)" icon="server" href="/self-hosting/kubernetes">
    Production deployments on EKS or GKE. Persistent storage, S3-backed ClickHouse, load balancers, and TLS.
  </Card>
</CardGroup>

## Configure your deployment

The Helm chart exposes every paid and optional feature through values in `laminar.yaml`. See the [configuration reference](/self-hosting/configuration) for the full surface:

* **[AI features](/self-hosting/configuration#ai-features-and-llm-provider)**: chat-with-trace, SQL-with-AI, and Signals all run through one LLM provider (Gemini, OpenAI, or Bedrock).
* **[Signals](/self-hosting/configuration#signals)**: natural-language outcome and failure extraction, on by default once an LLM key is set.
* **[Slack notifications](/self-hosting/configuration#slack-notifications)**: brokered through Laminar Cloud with an enterprise license key.
* **[OAuth login](/self-hosting/configuration#oauth-login)**: GitHub, Google, Azure AD, Okta, and Keycloak.
* **[Storage](/self-hosting/configuration#storage)**, **[TLS and ingress](/self-hosting/configuration#tls-and-ingress)**, **[PII redaction](/self-hosting/configuration#pii-redaction)**, **[secrets management](/self-hosting/configuration#secrets-management)**, and **[image pinning](/self-hosting/configuration#container-images)**.

## What's next

<CardGroup cols={2}>
  <Card title="Start tracing" icon="play" href="/tracing/introduction">
    Point the SDK at your instance and send your first traces.
  </Card>

  <Card title="View traces" icon="eye" href="/platform/viewing-traces">
    Read the transcript view instead of a tree of span names.
  </Card>
</CardGroup>