OSS vs Enterprise

OpenDome is open-core. The engine you run and consume is open source under Apache-2.0. The managed/Enterprise tier layers central orchestration, a console, curated packs and compliance tooling on top of the exact same cell charts — nothing in the open core is crippled to sell the upgrade.

One spec, one model

Both editions speak the same OSL spec and serve the same /osl/* API. The Enterprise tier adds operation, experience and packaging around the cell — not a different data model. Anything you build against OSS keeps working.

Feature comparison

Capability	OSS Apache-2.0	Enterprise Commercial
Cell (per-tenant data plane, Helm)	✅	✅
OSL engine — the 13 /osl/* endpoints	✅	✅
OSL spec, JSON Schemas, conformance	✅	✅
Connectors — Postgres, MySQL, Salesforce, custom Singer taps	✅	✅
Embedder + Lance hybrid retrieval	✅	✅
Policy enforcement (SQL allowlist, row filters, projection) — fail-closed	✅	✅
Local token issuer (HS256 per tenant)	✅	✅
Self-hosted on your own Kubernetes	✅	✅
Console — domain-map UI, semantic modeler, governed previews	—	✅
Control-plane — multi-tenant provisioning, lifecycle, JWT rotation	—	✅
BYO-OIDC — front the engine with your IdP, trust X-Actor-Roles	—	✅
Vertical packs — Finance / Legal / HR curated models & metrics	—	✅
Premium connectors — SAP, Workday, banking ERP	—	✅
Compliance pack — audit chain, AI Act / DORA / GDPR artifacts	—	✅
Agent packs — pre-configured MCP manifests	—	✅
Managed cloud + SLA + support	—	✅

Note

Throughout these docs, a Enterprise badge marks a capability that requires the Enterprise tier. Everything unmarked is in the open-source distribution.

How the upgrade works

The cell is the same artifact in both editions. The differences are what runs around it:

OSS — standalone cell

You install charts/standard-tenant + charts/tenant-semantic-api. The cell mints its own HS256 tokens, enforces policy in-process, and serves OSL over its own Ingress. No control-plane namespace ever exists.

Enterprise — managed fleet

A central control-plane provisions and rotates many cells, issues JWTs, proxies the console’s calls (forwarding X-Actor-Roles so the cell still enforces the caller’s ACL), and adds packs, compliance and support.

Honesty about scope

A few capabilities are documented in the OSS spec but ship behind the Enterprise tier or are still landing — the docs say so inline rather than implying full coverage:

• MetricFlow resolution in POST /osl/query is planned; today the endpoint serves a governed SQL slice. See the query reference.
• The osl CLI and the conformance test suite are upcoming epics.
• Cross-model joins / the metric engine for JointEntity attributes are deferred — those attributes resolve to null in the current slice.

Roadmap, not marketing

Where something isn’t done yet, you’ll find a status note on the page, not a silent gap. That’s the contract: the spec describes what exists; the engine implements it additively.