Introduction
Overview
The map of this documentation — the Kaiten model in one paragraph, then where to go to build on it, sell with it, run it, and look things up.
Kaiten is an open-source control plane for B2B SaaS. It unifies feature flags, entitlements, monetization, and deployments into a single data model — so that what you sell, what your customers can access, and what runs for them are one source of truth instead of three disconnected systems.
Kaiten turns your commercial contract into the source of truth for your infrastructure.
This page is the map. What is Kaiten? makes the case in full — what it makes redundant, what it deliberately leaves to the tools around it, and when it is not the right fit.
Start here
Quickstart
Build it yourself, in about ten minutes: a running stack, a customer, a License, and a feature gated by it.
Console Tour
Walk the seeded demo instead: customers, Licenses and their entitlements, flags, service accounts.
What is Kaiten?
The problem it solves, what exists today, and where it is going.
Editions
What the Community Edition carries, and what Kaiten Cloud adds on top of it.
The model
The rest of the documentation builds on these pages.
Core concepts
The model in one diagram: who you sell to, what they bought, and where their product runs.
Vocabulary
The authority on terms — License, Customer, Instance, Entitlement — and why each word was chosen.
Architecture
The pieces of the system and how a request travels through them.
Data model
The exact reference: every table, column, enum and constraint, with the ERD.
Build on it
Feature flags
Flags whose targeting rules read the commercial contract, evaluated through OpenFeature.
Entitlements
What a License grants, how usage is measured against it, and what happens at the limit.
SDKs
The Go and Python clients and the TypeScript packages — which one runs where, and which credential it carries.
Sell and operate
Monetization
License types, how tiers are composed from entitlements, and what the commercial layer will add.
Deployments
Components, releases, deployment zones, and the journal of what landed where.
Integrations
Outbound webhooks, the CRM connectors, and the event stream a self-hosted stack consumes.
Self-hosting
Run the Community Edition: the compose stack, identity, the event pipeline, the operator surface.
Look it up
API reference
Every operation, generated from the specification the API publishes about itself.
CLI
Customers, Licenses, entitlements, flags, and releases from the terminal.
Event catalog
Every domain event Kaiten emits, with the payload contract each one carries.
Guides
End-to-end walkthroughs: gate a feature, meter usage, roll out progressively, audit access.
Capabilities that exist only on Kaiten Cloud carry an edition badge, and the ones still to come carry a "Coming soon" badge. Everything else is in the Community Edition and runs on your own infrastructure.