Solutions
One codebase. Multiple editions, one for each stack you run.
Same contracts. Same governance. Same Apache-2.0 core. The difference between editions is the platform adapter wired underneath. All editions are free. The commercial offering is Professional Services + Enterprise Support, available for any edition below.
Private Preview
★ Most mature
Kirimana for Databricks
Databricks Lakehouse + Unity Catalog + Workflows
- AI gates Databricks alone can't enforcePer-contract classification blocks every LLM call (Databricks AI Assistants included) from touching restricted data. Workspace ACLs don't get this granular.
- Unity Catalog stays — backed by a contract source of truthOwner, classification, lineage pushed bidirectionally. UC keeps its UX; Kirimana is the artefact your auditor reads.
- DORA / EU AI Act / GDPR — generated, not assembledReports synthesised from contract metadata + audit log. The audit takes minutes, not weeks.
See full comparison
Private Preview
Kirimana for Fabric
Fabric Lakehouse + Warehouse + Purview + Azure OpenAI
- AI controls Copilot alone can't deliverEvery LLM call — Azure OpenAI, Bedrock, Anthropic — classification-checked before the model sees a token. Restricted data stays in your tenant.
- Purview stays the catalog — fed by contractsOwner, classification, lineage pushed bidirectionally. Microsoft tenants keep Purview's UX; Kirimana is the source of contract truth.
- DORA / EU AI Act / GDPR for the data productCompliance Manager covers the Fabric platform. Kirimana generates the data-product reports your DPO actually has to file.
See full comparison
Private Preview
Kirimana Enterprise OSS
Trino + Iceberg + Polaris + Ranger (or your choice)
- The AI gate Ranger never imaginedAnthropic, Azure OpenAI, Bedrock, Ollama — all gated by per-contract classification. Air-gapped path via Ollama. Ranger doesn't see AI calls; Kirimana does.
- Polaris stays the catalog — Kirimana is the contractBidirectional sync of owner, classification, lineage to Polaris. The OSS stack gets a contract artefact it never had.
- DORA / EU AI Act / GDPR — built, not bolted onReports synthesised from contract metadata + audit log. The OSS stack alone has no compliance generators; Kirimana ships the templates.
See full comparison