Skip to main content

Editions & licensing

Splyntra ships as one source-available core, built into three editions. The core is the version of record: it builds, runs, and is genuinely useful on its own, and the commercial features are layered on through build-time seams and configuration rather than forked code.

The three editions​

EditionWhat it includesDeploymentLicense
CommunityThe full core: OTel collector, traces, logs, metrics, cost analytics, detection, evaluation, and the dashboard. Single implicit org, email/password + API keys.Self-hosted, docker compose up. Free forever.FSL-1.1 → Apache-2.0
EnterpriseCommunity plus the ee/ modules: governance, agent identity/federation, SSO/SAML/SCIM, and advanced scorers (llm_as_judge).Self-hosted (Helm) on your infrastructure.Commercial
CloudEnterprise feature set plus the cloud/ control plane: multi-tenant orgs, OAuth signup, managed billing, per-plan gating.Managed by Splyntra at app.splyntra.com.Commercial

For the Cloud per-plan feature matrix (Free / Pro / Team / Enterprise), see Plans & pricing.

The license split​

Splyntra uses two licenses, enforced per-file with SPDX identifiers.

Core — Functional Source License (FSL-1.1-ALv2)​

The repository default and everything under apps/* (collector, security, evaluation, web) is FSL-1.1, converting to Apache-2.0 two years after each release.

FSL allowsFSL forbids
Free internal and production use, at any scale"Competing Use" — using Splyntra to build or offer a product that competes with it
Reading, modifying, and self-hosting the sourceReselling Splyntra as a service
Building on it for your own applications—

Every FSL release automatically becomes Apache-2.0 two years later, so the core is permanently open on a rolling basis.

SDKs and integrations — Apache-2.0​

sdks/python, sdks/typescript, and everything under integrations/ are Apache-2.0 with no conversion delay, so you can embed them freely in any project, including commercial and closed-source ones.

Commercial modules​

Governance, agent identity, SSO/SCIM, the cloud control plane, billing, and the llm_as_judge scorer are commercial and are not in the public repository.

The three build-time seams​

Editions differ by which modules are compiled or composed in — there is never a runtime if (cloud) branch in shared code.

  1. Backend (Go). cmd/collector-cloud blank-imports the ee/* modules; each module's init() calls extension.Register(...) to mount its /v1 routes. The community core binary imports none of them, so those endpoints 404 in Community.
  2. Dashboard (Next.js). A compose step overlays the cloud screens onto the published @splyntra/dashboard core through a slot registry (registerNavItem / registerWidget), so cloud-only screens mount without editing core code.
  3. Scorers (Python). The ee/scorers-pro package registers llm_as_judge via the splyntra.scorers entry point; the Cloud evaluation image installs it.

Next steps​