Skip to main content
LangWatch is open-core. Some governance surfaces work for every self-hosted deployment under the Apache 2.0 license; others require a paid Enterprise plan. Use this map when planning a rollout: In the LangWatch UI, Enterprise-only surfaces show an “Available on Enterprise plans” card with an upgrade CTA when the org isn’t on an Enterprise plan; the same surfaces gray out the source-type dropdown to otel_generic for non-enterprise users.

Per-file license headers

The repository tree is split 1:1 by license, so the directory a file lives in is its license: The client SDKs are MIT so that integrating LangWatch never puts a copyleft obligation on your own application. MIT still asks you to retain its copyright and permission notice when you redistribute the SDK or a substantial portion of it, which is the usual third-party-notices entry rather than a constraint on how you license your own code. The rows are read most-specific first: the SDK directories are MIT even though they sit outside platform/app/ee/. The header is the first line of the file, written as SPDX-License-Identifier: <identifier> behind whatever the language uses for a line comment: // in TypeScript and Go, # in Python and YAML. It is a single line, no block comment, no preamble, no copyright assignment. Tooling (REUSE, GitHub linguist) reads SPDX identifiers natively, and contributors moving a file across the boundary flip one line to record the result. Recording it is not the same as making it true: the SPDX line states a file’s license, it does not relicense existing contributions, so a move across the boundary needs the rights checked and any applicable notices preserved before the line changes. The Enterprise identifier is a LicenseRef-* because LangWatch EE is not a registered SPDX license; the canonical text lives in platform/app/ee/LICENSE.md, and the per-directory breakdown is in NOTICE. The directory is what the license follows, read most-specific row first rather than as a single Apache-2.0-unless-ee rule. The SPDX header records the result per file, and files that predate the convention do not carry one yet.

Enabling the Enterprise surface

Turning on the Enterprise feature surface takes a real signed license key. There is no environment-variable bypass. See Editions and licensing for how to request a key and where to set it.
Last modified on August 24, 2026