Dry-run a new agent policy against past activity before it goes live. See how it works

Skip to content
Gaten

Why Gaten

A prompt is a request. A checkpoint is a rule.

Once an AI agent can refund, pay, email or change a system, the question isn't what it might say — it's what it's allowed to do. That needs to be decided outside the model, on every action, in rules people can read.

The options

Ways teams try to limit agents today.

Each of these has its place. Here's how they compare for one job: controlling the actions an agent takes.

ApproachChecked outside the modelSees the action and its argumentsHuman approval built inRules business owners can readDecision audit trail
Instructions in the prompt“Never refund more than $100.”
Content guardrailsFilters what a model reads and writes.PartlyPartly
Checks written into each toolif amount > 100: raise …You build itYou build it
Framework approval stepsPause the agent and ask a person.You build it
General authorization enginesPolicy-as-code for apps and APIs.You build itPartly
GatenA checkpoint built for agent actions.

A general comparison of approaches, not of specific products. Capabilities vary by tool and by how it's set up.

Use them together

Guardrails watch what agents say. We decide what they do.

Content guardrails catch harmful or off-topic text. Your agent framework runs the loop. Your identity system says who's who.

Gaten sits at a different point: the moment an agent tries to act. It works alongside the tools you already have, rather than replacing them.

Build or buy

What you'd build to do this yourself.

Checking one threshold in code is easy. Running agent limits across a company is a product of its own.

  1. 01

    A rule language and versioning

    Rules people outside engineering can read, with history and one-step rollback.

  2. 02

    Approval routing

    Who approves what, how they're notified, timeouts, escalation, and safe defaults when nobody answers.

  3. 03

    Dry-run on real activity

    Replaying past agent actions through a draft rule to see what would change.

  4. 04

    A tamper-evident log

    Every request and decision, linked to the rule version, searchable and exportable.

  5. 05

    One place for every agent

    The same limits and records across teams, frameworks and model providers.

Conceptual black gateway with a blue sphere passing through
A rule, not a requestConceptual illustration

Compare it on your own agents.

Bring the checks you've written today, and an expert will show what changes.