Cross the line — with peace of mind.

Your agents are ready. The actions that move money, change state, or are hard to undo are the ones you’ve kept them away from — not because the model isn’t capable, but because you had no way to make a guarantee that holds regardless of what the agent reasons. KIFF is that guarantee: a state-aware boundary outside the agent that decides before the action runs, allows what’s legitimate, turns the unsafe attempt into a no-op, and records every decision with a receipt you can verify independently.

Build the operational domain once. Connect any agent.

Where the foundation earns its keep: the action.

The reusable domain pays off at the one boundary that matters: the moment you let the agent act. Put the agent on the action — the boundary is what makes it safe — so you can hand it the consequential route and rely on what it cannot do.

An agent proposes an action. KIFF checks it against the current state of the thing it touches — is this invoice already paid, is this order already refunded — and lets the legitimate action through, refusing only what the state forbids, before it executes. KIFF decides; your system runs the action. Every decision is recorded as evidence.

Six real agents on the routes that move money.

Four flows you can now ship — a real agent does the revenue work, live on Bedrock — and two where the boundary simply holds the line. Every card is a runnable proof: real agent, real framework, real terminal output. The first four are live in the browser.

The four enablement flows are live in the browser at kiff.dev/spot — switch recipes, run a real agent, watch the boundary hold. The finance wedge is the entry scenario, not the boundary of the platform — any domain whose actions map to a state machine fits the same loop.

The evidence is the proof the boundary ran.

For every decision, KIFF emits a signed record: what was proposed, the state it was checked against, the decision, and the policy that produced it — produced at the moment of the decision, not reconstructed later. It is a protocol output, not the thing you buy: strong proof for an auditor, a regulator, or a cyber-insurer that the runtime decided before execution. What you buy is the reusable operational foundation and the Cloud that operates it.

Where KIFF is worth it.

The path: build free, run production monthly, commit on a floor.

Build the domain on the free framework. Operate it on Cloud when you want it run for you. Numbers below are launch hypotheses.

You build the domain once and connect any agent; Cloud operates it and meters governed operations, never domains, actions, agents, or seats. Full detail at kiff.dev/pricing · talk to us: hello@kiff.dev