Ship agents on the flows that move money.Pay for the work they run.
Put your agents on the production flows you've held them back from — refunds, payouts, collections — with KIFF Cloud as the boundary that runs in the path. The framework is free and the domains you build are yours; Cloud is the managed runtime you pay for, by the governed operations your agents actually run. Start Cloud monthly; commit only after usage has a measurable floor.
The unit is a governed operation — one authenticated action proposal KIFF evaluates against current state and your domain contract and records with an outcome. You are not billed per domain, action, agent, integration, control, or seat. Build and connect as many as you like; you pay as your agents put them to work.
Developer to Enterprise.One consumption path.
Launch prices and allowances are deliberately simple — and explicitly provisional — while the first production tenants prove the unit economics. The bill tracks governed operations, never the number of domains, actions, agents, or seats.
- ✓ 1,000 governed operations / month
- ✓ Domains, actions, agents, integrations, and dev environments — unmetered
- ✓ Observe a guard runtime and draft a domain from real traffic
- ✓ Short evidence retention
- — No production posture
- ✓ 50,000 governed operations / month (launch allowance)
- ✓ Everything in Developer, in a production posture
- ✓ Approval-required decisions, held until resolved
- ✓ Signed receipts and audit export
- ✓ Standard evidence retention
- ✓ Private beta: cap disclosed and raised by hand before you reach it
- ✓ Discounted governed-operation rate, fixed for 12 months
- ✓ One pooled balance across domains, agents, teams, and environments
- ✓ Overage instead of shutdown — no billing outage on a production path
- ✓ Up to 10% unused value rolls into a same-or-larger renewal
- ✓ Longer retention and private domain distribution
- ✓ Dedicated or customer-controlled deployment, private networking
- ✓ SSO, SCIM, organization policy, separation of duties
- ✓ Availability and latency commitments, incident response
- ✓ Customer-managed retention and compliance export
- ✓ Same pooled-commitment principle as Scale
Launch status. $199/month, the 50,000-operation allowance, and the annual floors are launch hypotheses, to be reviewed after the first five production tenants or ninety days of usage. Cloud Growth is in private beta: its monthly cap is disclosed and raised by hand before your traffic reaches it, and automatic metered overage does not bill yet — it ships only once usage telemetry, budgets, alerts, and a paid-plan grace path are live.
One governed operation.Exactly this.
A governed operation is one unique, authenticated action proposal that KIFF evaluates against the entity's current state and your active domain contract, and records with a terminal outcome. allowed, blocked, and approval_required all count — KIFF did the production work in each case.
What never counts: unauthenticated requests, malformed proposals rejected before evaluation, infrastructure failures where KIFF returns no decision, retries resolved from the same idempotency key, and reads — receipt views, dashboard, and domain authoring. A transport that retries ten times is still one billable operation.
The objects you build are free to create and connect: domains, actions, agents, integrations, and environments are expansion vectors, not toll booths. They never appear as a line on the bill. See RFC 029 for the consumption model.
propose ISSUE_REFUND → recorded
A commitment you buy for what it gives you.
Cloud Scale and Enterprise are optional — taken after monthly usage shows a floor. The commitment is portability and price protection, not locked-in spend.