Why Kaiten

Your contracts live in HubSpot.
Your code lives on GitHub.
Your customers are stuck in the gap.

Every B2B SaaS scaling past fifty enterprise customers hits the same wall: three disconnected systems — what was sold, what's accessible, what's running — held together by glue code that breaks every quarter. Kaiten is the open-source control plane that closes the gap. One model. One audit trail. One source of truth.

Get Started View on GitHub

The Missing Layer

Three teams. Three tools. Three sources of truth that should be one.

The day you sign your tenth enterprise customer, your stack splits into three worlds. The day you sign your hundredth, those worlds stop talking. This is not a tooling problem. It's an architecture problem.

Sales / Revenue

What was sold

HubSpot · Attio · Stripe

Plans, custom prices, negotiated discounts, vouchers, renewal dates. The contract is signed. Now somebody has to translate it into runtime reality.

Product

What's accessible

LaunchDarkly · Stigg · custom code

Feature flags know the targeting rule says “Pro customers.” They do not know who is on Pro right now. The flag tool and the billing tool never share a primary key.

Engineering

What's running

ArgoCD · Kubernetes · Terraform

Deployments know what's running where. They do not know which customer is on which version, in which region, with what entitlements. Three answers, three tools.

The Cost of the Gap

Glue code. Revenue leakage. 47-minute incident calls.

Every reconciliation script you write is the company telling itself the same lie: that the systems will eventually agree. They never do. The drift compounds, and the bill arrives during the next on-call.

The Problem, Stated Precisely

It's 9:47 AM on a Tuesday. A customer can't load their dashboard.

A real engineering story

Acme Corp says the new dashboard isn’t loading. Three engineers and forty-seven minutes later, somebody finally figures it out.

09:47
Support pages the on-call. Customer reports the new dashboard isn't rendering.“It worked yesterday.”
09:50
Engineer opens the feature flag tool.new-dashboard is enabled for Acme. So far, so good.
09:55
Opens the billing system. Acme is on Pro. Subscription active, payment current. The plan includes the new dashboard.
10:02
Opens the deployment monitor. Acme's instance is running v4.7.2. Release notes say the dashboard shipped in v4.7.0. So they have the right version.
10:15
Senior engineer joins the call. They check the rollout configuration again. The flag is set to 100% for Pro plan customers. Acme is on Pro.
10:34
Eventually they figure it out. Acme's instance was migrated to the EU region last week. The EU deployment is on v4.6.9. The rollout to that region was paused last Friday because of a different bug. Nobody updated the flag's targeting rules.

The flag was right. The entitlement was right. The infrastructure was wrong. And no single tool could tell them that.

Today, answering “why isn’t customer X seeing feature Y?” takes three queries across three tools and forty minutes. It should take ninety seconds and one query.

What Kaiten Is

One control plane. Three engines. One unified data model.

Kaiten is the open-source layer where feature flags, entitlements, and orchestration share a single model — every customer, every feature, every deployment, every event in one queryable graph. We don't replace Stripe or HubSpot. We make them work together.

Feature Management

OpenFeature-compatible flags with CEL targeting and progressive rollouts.Flags that natively know what the customer paid for — something an isolated flag tool can never do.

Monetization & Entitlements

Plans, prices, addons, vouchers, real-time metering. Provider-agnostic — works with Stripe, Lago, or your own billing engine. Vouchers can grant a discount, boost a quota, and activate a flag in one redemption.

Orchestration & Deployments

Deployment Zones, Components, Instances. Track which version of which service runs for which customer — across regions, clouds, and now cloud marketplaces (AWS, Azure, GCP).

The whole story, in one query.

SELECT customer.name,license.tier,flags.active,deployment.version

↓

FROM kaiten.unified_view

↓

90 seconds, not 40 minutes.

The contract is the source of truth. The flags know it. The deployments know it. The audit trail proves it.

Who It's For

B2B SaaS teams scaling past the point where spreadsheets and glue code start failing.

Kaiten is built for engineering and product teams that already shipped something — and now need to operate it across many enterprise customers, many regions, and many pricing tiers. Below the threshold, you don't need us. Above it, you can't keep building without us.

Best fit

B2B SaaS, 50–500 enterprise customers

Multiple plan tiers with custom negotiated terms
Operating across two or more regions or clouds
Engineering team spending more than 20% of capacity on internal glue tooling
Sales asking engineers to “toggle this for the demo” weekly

Strong fit

AI-native SaaS with usage-based pricing

Per-token, per-model, or per-call cost structures
Need real-time visibility on AI consumption per customer
Pricing changing every quarter as costs evolve
Already broke through Stripe's standard subscription model