Your next agent should not need another backend.
Start with one consequential action. We build the minimum shared domain around it, connect your existing agent, and leave an operational foundation the next agent can reuse.
Ship the next action.Build the foundation for every one after it.
Bring one real agentic feature. We map the entity lifecycle, define the shared action contract, connect Guard and KIFF Cloud, and stay with it until the agreed paths pass.
The governed path can be implemented and verified in under two hours once secure access and a testable execution path are ready. Production deployment follows your release process.
KIFF Action Launch
- 01 One entity lifecycle mapped to your existing systems
- 02 One reusable action contract: state, authority, and approval
- 03 Your existing agent connected through KIFF Guard
- 04 KIFF Cloud runtime, approvals, and signed history
- 05 A documented connection path for the next agent
You are not buying one isolated guard. The first action proves a foundation your next agents reuse. Continue on an annual Cloud commitment and the €5,000 is credited in full.
Operate the shared foundation.Add agents without rebuilding it.
Start free, move to Growth when a real action enters production, and commit only after usage establishes a baseline. Cloud meters governed operations. Domains, actions, agents, frameworks, and seats remain unmetered.
- ✓ 1,000 governed operations / month
- ✓ Unmetered domains, actions, agents, integrations, and dev environments
- ✓ Observe a guard runtime and draft a domain from real traffic
- ✓ Short evidence retention
- not included 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, so billing never stops 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
Cloud Growth is in private beta: your monthly allowance is disclosed up front and raised with you before your traffic reaches it, so a billing limit never becomes a production outage.
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, then records with a terminal outcome. allowed, blocked, and approval_required all count because 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 such as receipt views, dashboard access, 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. Create as many as you need; they never appear on the bill. What you pay for is the verifiable evidence stream each operation produces: a signed, tamper-evident receipt. 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. You take them only after monthly usage shows a floor. The commitment buys portability and price protection, not locked-in spend.