Laminar AI

license

Apache-2.0(OSI)

source

public(Rust core + TS UI)

core features withheld

yes — the self-hosting docs say Signals, signal event clusters, and email and Slack alerts require an enterprise license key (LMNR_LICENSE_KEY

SDKs

Apache-2.0

Laminar's source is Apache-2.0 and public, and tracing, evals, datasets and SQL query run when self-hosted without a key. Signals, signal event clusters and email and Slack alerts on a self-hosted instance need an enterprise license key from Laminar, which is why Laminar is open core rather than fully open source.

• https://docs.laminar.sh/hosting-options recorded 2026-09-29

  Self-hosting options page, whose note says "Signals, signal event clusters, and email and Slack alerts require an enterprise license key" and whose Helm plus license option "Unlocks Signals, signal event clusters, and email and Slack alerts".

• https://docs.laminar.sh/self-hosting/configuration recorded 2026-09-29

  Self-hosting configuration reference, whose Slack section says the instance "authenticates to the broker with an" enterprise license key set in laminar.yaml.

• https://github.com/lmnr-ai/lmnr recorded 2026-08-13

  Repository page. The license sidebar resolves LICENSE.md to Apache-2.0 (spdxId "Apache-2.0"), there is no ee/ or enterprise directory in the root listing, and the root carries docker-compose.yml plus four variants (full, local-build, local-dev, local-dev-full), which is the self-host path.

• https://raw.githubusercontent.com/lmnr-ai/lmnr/main/frontend/lib/features/features.ts recorded 2026-09-29

  Feature-flag source in the public frontend; the Slack broker path is enabled only when "process.env.SLACK_BROKER_URL && !!process.env.LMNR_LICENSE_KEY" holds.

• https://raw.githubusercontent.com/lmnr-ai/lmnr/main/LICENSE.md recorded 2026-09-29

  The repository LICENSE.md is the unmodified text of the "Apache License" "Version 2.0, January 2004", with no separate enterprise license text in the file.

• https://raw.githubusercontent.com/lmnr-ai/lmnr/main/README.md recorded 2026-09-29

  README self-hosting section, which tells readers to "clone the repo and start the services with docker compose".

Laminar's lmnr package is a client SDK: applications install it to send traces, so its downloads measure instrumented applications rather than direct use of Laminar itself. No other usage figure exists, and GitHub stars are not a use, so the reading reflects Laminar's standing as a known platform rather than a measured count.

• https://github.com/lmnr-ai/lmnr recorded 2026-09-14

  Apache-2.0 tracing platform, 3,251 GitHub stars, last pushed 2026-09-13; the star count is recorded for the record and is not what the level is derived from.

Laminar covers OpenTelemetry-native tracing, evaluations run from its SDK, CLI and CI, datasets built from production traces with labeling, LLM cost tracking, and a SQL query and dashboard layer over traces. It does not surface explicit prompt versioning, which keeps it a step behind Langfuse on breadth.

• https://docs.laminar.sh recorded 2026-09-29

  Docs home: "Run evals against datasets locally or in CI. Catch regressions before they ship." and "Build evaluation datasets from production traces." plus "Realtime traces, full-text search, raw SQL access from the UI, CLI, or MCP, and custom dashboards."

• https://docs.laminar.sh recorded 2026-09-29

  Docs home: "Replay any traced span. Swap prompts or models and compare results side by side." and the sidebar lists "LLM cost tracking".

• https://github.com/lmnr-ai/lmnr recorded 2026-08-13

  README feature checklist - "Evals. Unopinionated, extensible SDK and CLI for running evals locally or in CI/CD pipeline", "UI for visualizing evals and comparing results", and "Query traces, spans, metrics, and events with SQL". No prompt-versioning or prompt-management item appears.