Get Started
What's Next?
Where to go from here, by role — integrate deeper, operate self-hosted, or learn the model.
You have the chain running. Where to go next depends on what you are here to do.
Integrating Kaiten into your product
The developer track: credentials, permissions, and the exact shapes behind every call you'll make.
Authentication
Service accounts, the ksh_ token lifecycle, and the identity model.
Scopes
What each read:/write: pair gates, per module.
The data model
The exact reference — entities, enums, constraints, and the ERD.
API conventions
Pagination, the error envelope, slug rules, and your own identifiers — what every endpoint shares.
SDKs
The Go and Python clients and the two @kaitencloud TypeScript packages — plus OpenFeature for flags.
API reference
Every endpoint, generated from the OpenAPI specification.
Operating Kaiten yourself
The Community Edition is the full control plane, self-hosted under the Apache License 2.0.
Self-hosting
The operator's reference — what the stack contains, what differs from Kaiten Cloud, and every page that follows.
Docker Compose
Every service in compose.yml, what starts when, the task targets, and where data lives.
Consuming events
The self-hosted event path — attach your consumer to the exchange your own stack publishes to.
Editions
What the Community Edition includes, and what the Kaiten Cloud tiers add.
Understanding the model
The concepts track: why the model is shaped the way it is, and the words it insists on.
Core concepts
One page per concept — customers, licenses, entitlements, flags, events.
Vocabulary
The canonical glossary — the authority on what each term means.
The audit trail
Changes and evaluations in one record — who had access to what, when.
Monetization
The commercial layer: the chain from License to observed usage.
Receive Events
React to what happens in Kaiten — managed webhook endpoints on Kaiten Cloud, or the event stream directly on Community Edition.
Overview
The Kaiten model in one diagram — who you sell to, what they bought, where your product runs for them, and how flags, usage, and events hang off the same records.