Kirimana OSS Edition
Kirimana OSS Edition is the prescribed open-source path alongside the Databricks flagship. The component stack is on the roadmap and will be published when the first design-partner deployment is exercised end-to-end. Currently not generally available; the Databricks path is the supported route today.
For organisations who want the full Kirimana architecture on a true open-source operating layer alongside the Databricks flagship. Kirimana OSS Edition is a prescribed open-source path, not a menu of interchangeable tools — kept narrow on purpose so teams can install, operate, and govern one coherent stack.
On the roadmap. Not generally available today. The Databricks path is the supported route; Kirimana OSS Edition is in early design-partner shaping. The component stack will be published once the first design-partner deployment is exercised end-to-end.
The same governance model as the Databricks path
What stays identical regardless of the operating layer underneath:
- ODCS v3 contracts on disk as the canonical artefact — same format as the Databricks path
- Mandatory ownership, enforced structurally —
owner: unknownis rejected at apply - Fail-closed authoring guardrails — inferred PII cannot be
authored as
publicwithout an audited override and a written reason - Same Kiri — same CLI, same MCP surface, same PR-time
governance gates (
kiri contract lint / validate / diff) - Federation across three transports with
health()returning OK / STALE / UNAVAILABLE; federated reads fail closed when a source isn’t reachable - Migration as a verb set — translate · parity · cutover · KEEP/DROP/MERGE/REDESIGN review actions, quarantine reprocess as a typed state machine
- AI-readable by default — contracts as YAML on disk, audit as JSONL, lineage as a graph. Every Claude Code / Cursor / Continue / Cline agent reads your data platform’s state by reading the files
- Apache-2.0 today, no BSL planned
What’s on the roadmap
The operating runtime — ingestion, orchestration, table format, SQL engine, catalog metadata, policy enforcement, transformation — is being shaped with design partners and will be published once the first end-to-end deployment runs.
Compliance evidence generators (DORA / EU AI Act / GDPR) are on the roadmap on both editions. When they ship, the outputs will be structured evidence artefacts, not legal certification — human attestation and review by qualified personnel remain part of every regulatory framework we cover.
Who this is for
- OSS-first organisations evaluating the path in advance of GA
- Public sector and regulated teams seeking platform sovereignty
- Enterprise architects who want a portable contract format from day one so the contracts they author against Databricks today travel unchanged
Pricing posture
- Apache-2.0 today, no BSL planned. There is no “community edition” feature-gating in the codebase today. We don’t plan a BSL relicense; if that ever changes, we’d say so before doing it. See /pricing.