Skip to main content
Private Preview·Early access by invitation.Request access →
Kirimana.
Pricing

Free to self-host. Eventually Apache.

Kirimana’s engine and CLI are source-available under the Functional Source License (FSL-1.1-ALv2). Install it, fork it, run it in production — for any purpose except building a competing product or service out of Kirimana itself. And every release automatically converts to Apache-2.0 two years after it ships, so the code becomes fully open over time.

The ODCS contract-spec layer — the canonical data-contract model, the kiri.* extensions, and the validator — is Apache-2.0, forever, so the contract format itself is never encumbered.

What that means concretely

  • Free to self-host. Run the full single-player engine — contracts, plan/apply, the DuckDB and Databricks runtimes, silver modelling, ingestion, lineage, quality, the AI Gateway (bring your own key), the compliance generators (DORA, EU AI Act, GDPR), incident dispatch, the MCP server — for your own use, at no cost.
  • No feature paywalls. There is no “community version” of the engine with the good parts removed. The single-player platform you self-host is complete.
  • No telemetry-gated features. Run it air-gapped. The product doesn’t phone home to enable anything.
  • Delayed open source, not open-core. The one restriction is a Competing Use — you can’t offer Kirimana itself as a rival commercial product or service. Everything else is permitted today, and each release drops that restriction entirely on its second anniversary, when it becomes Apache-2.0.

Why this model

Governance tooling has to be auditable by everyone who runs it — you can always read, modify, and self-host every line. The FSL keeps that true while giving the project a sustainable way to fund the work, and it does so with a hard guarantee that the code becomes fully open (Apache-2.0) on a fixed clock rather than staying source-available indefinitely.

Specialist commercial offerings

Some teams need curated, certified, calendar-maintained accelerators on top of the engine — for specific migration scenarios, regulated verticals, or managed deployments. Those live as separate offerings. More information coming soon.

For now, the kirimana.io product surface is the self-hosted engine. If you have a specific need (migration off a legacy tool, regulated-industry templates, hands-on deployment help), email hello@kirimana.io and we’ll route you appropriately.

Source

GitHub — issues, discussions, pull requests welcome.