- Is the self-hosted version really free?
- No catch. The engine is open source under Apache 2.0: the full control plane, the console, and the whole public API — 117 HTTP operations across REST and OFREP, plus a read-only GraphQL endpoint. You run the API and the console on your own Postgres, plus the event pipeline that feeds the audit trail and the event stream. Kaiten Cloud exists for teams who would rather we handled the ops.
- Does the open-source edition depend on any vendor?
- One, today: the console signs users in through a hosted identity service. Beyond that, the API trusts any JWT issuer you configure, needs no billing provider, and reports no usage to us. Everything specific to our hosted offer lives in a separate, private repository: every write it makes to the engine goes through the same public API you use, and Go’s internal-package rule keeps it from importing the engine’s internals.
- Why are there no prices on this page?
- Every tier except Community is in private beta, and their prices are not published yet. The tiers above say what each one is built to include, and details can still move during the beta. Community, the open-source edition, is free.
- What’s the difference between self-hosted and Kaiten Cloud?
- Who runs Kaiten, and where. Self-hosted, you run the open-source edition on your own infrastructure. On Kaiten Cloud, we run the same engine for you, on shared infrastructure or, on Cloud Enterprise, in a dedicated environment — and we deliver its webhooks to your endpoints, signed. Self-hosted, you consume the same events from the event stream.
- Can I start self-hosted and migrate to Cloud later?
- Yes. The data model is identical across self-hosted and Cloud, and the API contract is generated from the same source, so your configuration can be recreated in Cloud through the public API. No migration tool ships today; Cloud Enterprise includes migration assistance.
- What happens when I reach a tier’s limits?
- What already runs keeps running. Kaiten’s API is built to check a limit when something new is created: past the limit, the create is refused with a 409, and a limit it can’t verify returns a retryable 503 instead of letting the create through. Your existing customers keep being served, sign-in and reads are never quota-gated, and usage data is never silently dropped. It is the same mechanism Kaiten gives you for your own plans.
- Is Kaiten SOC 2 compliant?
- SOC 2 Type II certification is on the roadmap. The self-hosted edition gives you full control over compliance in the meantime — you audit the code, you hold the data, and every create, update or delete of a customer, instance, license, entitlement, flag or release commits its event in the same transaction; the audit trail is built from that event stream.