Hosting Options

Self-hosted (Docker Compose)

Run the full Laminar stack locally with Docker Compose:

git clone https://github.com/lmnr-ai/lmnr
cd lmnr
docker compose up -d

The dashboard is available at http://localhost:5667/. Create a project through the onboarding flow, then grab your API key from project settings.

Point the SDK to your local instance

TypeScript
Python

import { Laminar } from '@lmnr-ai/lmnr';

Laminar.initialize({
  projectApiKey: "<YOUR_PROJECT_API_KEY>",
  baseUrl: "http://localhost",
  httpPort: 8000,
  grpcPort: 8001,
});

from lmnr import Laminar

Laminar.initialize(
    project_api_key="<YOUR_PROJECT_API_KEY>",
    base_url="http://localhost",
    http_port=8000,
    grpc_port=8001,
)

For production self-hosting options, see the GitHub repository.

Access control

By default, a self-hosted instance accepts sign-in from anyone who can reach it. To require users to authenticate through an OAuth provider, set that provider’s credentials. GitHub and Google are configured directly:

AUTH_GITHUB_ID=your_github_oauth_app_id
AUTH_GITHUB_SECRET=your_github_oauth_app_secret

AUTH_GOOGLE_ID=your_google_oauth_client_id
AUTH_GOOGLE_SECRET=your_google_oauth_client_secret

Enterprise SSO providers (Azure Entra ID, Okta, Keycloak) are also supported through their own AUTH_* variables.

Configuring a provider controls how users sign in, not who can sign in: anyone with an account at that provider can still create an account on your instance. There is no built-in email allow-list.

Overview

Tracing

Signals

Debugger

Evaluations

Datasets

Platform

Managed (Laminar Cloud)

Self-hosted (Docker Compose)

Point the SDK to your local instance

Access control

​Managed (Laminar Cloud)

​Self-hosted (Docker Compose)

​Point the SDK to your local instance

​Access control

Managed (Laminar Cloud)

Self-hosted (Docker Compose)

Point the SDK to your local instance

Access control