ifivo
The agent control plane

Let agents act,
without losing control.

ifivo is the runtime control plane for AI agents. See what they do, approve what matters, and stop them instantly — with audit-grade logs across every tool, API, and payment rail.

Start freeTry the policy engine
Non-custodial Shadow mode first Policy enforcement Instant kill switch Immutable audit
curl -X POST https://www.ifivo.com/api/gateway/actions \
  -H "content-type: application/json" \
  -d '{
    "agent_api_key": "sk_live_…",
    "vendor": "stripe",
    "action": "refund",
    "amount_cents": 22000,
    "risk_score": 0.55
  }'
# → { "decision": { "outcome": "pending_approval",
#                   "reason": "Refunds over $150 require approval" } }
Same endpoint /api/gateway/actions runs in the public simulator.
ifivo dashboard showing live spend, approvals, and anomaly feed for a seeded tenant

Four screens. One command center.

See the money, approve the risky moves, and shut it all down instantly. ifivo turns scattered agent logs into an operational control plane your security, finance, and engineering teams actually use.

Overview

Daily spend, pending approvals, blocked actions, active agents — all at a glance.

ifivo Overview dashboard showing spend, approvals, blocked actions, and active agents.

See → Control → Intervene → Contain

1

See

Route agent actions through ifivo. Every call and payment attempt is logged with identity, intent, and risk.

2

Control

Define budgets, vendor allowlists, and risk thresholds. Deterministic rules run at the edge — no LLM required.

3

Intervene

Send anything above threshold to a human. Approve in-app or via Slack/email. Full diff of what the agent intended.

4

Contain

Quarantine an agent, freeze spend, or pull the org-wide kill switch. Authority is always revocable.

Shadow mode

Roll out policy without touching traffic.

Run new rules in shadow for a week. Watch what would have been blocked, approved, or flagged, then tune the thresholds against real agent behavior. Flip to enforcement when the numbers look right — no surprise incidents at 2 a.m.

  • Observe. Shadow policies log decisions without changing the outcome.
  • Diff. Every transaction shows the live decision next to the shadow decision.
  • Tune. Adjust thresholds in the policy editor, keep logs.
  • Enforce. Flip the switch when you're confident.
See a shadow decision on /try Shadow mode docs
Last 7 days · refunds-over-150
Shadow
Shadow (observed) Live (enforced)
Approvals sent
82
0
Blocked actions
17
0
Allowed actions
312
411
Next step: flip shadow: false. 82 would-be approvals will start going to the approvals queue.

Simple pricing. Ship today.

Start free. Upgrade when your agents touch real money.

Full pricing & comparison →

Starter

Free

For early pilots

  • 1 org · 5 agents
  • 10k actions / month
  • Shadow mode + dashboards
  • Community Slack
Get started

Team

Most popular
$499/mo

For production agents

  • Unlimited agents
  • 500k actions / month
  • Approvals + kill switch
  • SSO · audit export
  • Email & Slack approvals
Get started

Enterprise

Custom

For regulated orgs

  • SOC 2 / ISO artifacts
  • On-prem gateway option
  • Custom policy rules
  • Dedicated support
  • Stripe MPP + TAP integrations
Get started
FAQ

Straight answers to the common questions.

How is this different from LangSmith, Arize, or Helicone?+
Those tools are observability for LLM calls — great for debugging prompts and tracking quality. ifivo is a control plane for the actions agents take after the LLM decides. It blocks, approves, or routes for humans, and it does it deterministically in the hot path. They're complementary; we see most teams running both.
Do I need to route 100% of agent traffic through ifivo?+
No. Most teams start by wrapping one high-risk action (refunds, provisioning, external emails) and expand from there. Shadow mode lets you onboard more traffic without affecting live behavior.
What latency does the gateway add?+
Target is ≤ 50 ms p50 for a policy decision with the gateway in the same region as your agent. The engine is deterministic JSON — no LLM in the hot path.
Does Shadow Mode affect production behavior?+
No. Shadow policies record what would have happened and return it on the response, but the live outcome is unchanged by them.
What counts as an action?+
One agent call routed through the gateway equals one action. Dashboard reads, webhook deliveries, and MCP tool calls made by humans do not count.
Can I self-host?+
Yes, on Enterprise. You get the same container and policy engine we run in production, deployable in your VPC or on-prem.
How do I define policies?+
Use the visual builder in the dashboard, start from a template, or POST JSON to the policies endpoint. See the policy language reference in the docs.
What happens when the kill switch is triggered?+
Every agent in the org starts receiving blocked from the gateway until a human releases it. Individual agents can also be quarantined without touching the org-wide switch.