agent governance / control plane

Your AI agents are already touching production. Are they governed?

Exemplar is the policy layer that governs what agents can do — token budgets, approval gates, and a full audit trail across every model, tool, and framework.

exemplar / agent-monitorlive

token_spend.week

$0

↓ 61% vs last week

calls.blocked.today

0

policy enforced

model_routing.savings

0%

auto-optimised

audit_trail.completeness

100%

all runs logged

How it works

Every agent call passes through the same policy surface.

The same visuals that power Exemplar Console — Relay's decision wire, the living MCP gateway, and guardrails — live here so you can see the control plane before you sign in.

Marshal

Every tool. One endpoint.

Marshal serves your connectors, memory, prompts, and skills over MCP — any agent or IDE can use all of them the moment it connects.

Explore Marshal

Marshal offerings

View all →
Teams using Exemplar
Rigi TVSharpsellFundsIndiaDevDynamicsOnFinance AI

The problem

Your agents are running in production. Nobody knows what they're spending.

No budget limits. No access controls. No audit trail. Most teams discover the problem after it becomes an incident.

3.2×

average token overspend when agents run without model routing or budget enforcement

74%

of agent failures traced to unrestricted tool access — agents calling APIs they should never reach

0

audit records kept by most teams — no log of what ran, what it touched, or who approved it

Before vs. after

The same agent. Two very different outcomes.

One runs ungoverned — expensive, unrestricted, unaccountable. The other runs through Exemplar.

Without Exemplar

Agent triggered by engineer
Calls GPT-4o for every task — no routing logic+$340 wasted
Accesses GitHub, Jira, billing API — no restrictionsunrestricted
Writes to production DB — no approval requiredincident risk
No log. No audit. No record of what happened.no trail

With Exemplar

Agent triggered by engineer
Exemplar intercepts — policy engine evaluatesharness
Routed to Haiku for simple tasks, Sonnet for complex↓ 61% cost
Billing API blocked. Slack message requires approval.guarded
Full audit log: who, what, when, approved / blocked.logged

The numbers

What governed agents actually look like.

Data from engineering teams running AI agents through Exemplar — before and after governance was enabled.

Weekly token spend

before vs. after Exemplar

↓ 61%
Wk 1
Wk 2
Wk 3
Wk 4*
Wk 5
Wk 6
Before Exemplar
After Exemplar (Wk 4+)

Model routing distribution

tasks auto-matched to right model

auto
Haiku — simple58%
Sonnet — mid32%
Opus — complex10%

Blocked calls by category

last 30 days across all agents

147 total
Billing API
42
Prod DB write
38
Slack (unappd)
31
AWS IAM
24
GitHub force
12

Agent run outcomes — daily

passed / approved / blocked

98.2% safe
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Passed
Human approved
Blocked

Guardrails

Define exactly what your agents can and cannot touch.

Set access policies once. Every agent — on every framework — operates within them.

Tool access control

agent-code-review · last run 4m ago

github.readallowed
github.pushneeds approval
db.production.writeblocked
jira.readallowed
aws.billing.modifyblocked
slack.message.sendneeds approval

Cost governance

budget tracking · all agents · this week

agent-code-review$142 / $200
agent-pr-triage$38 / $100
agent-deploy-checklimit hit · paused
agent-doc-writer$12 / $50
model-routing.savings↓ 61% this week

The autonomous agent era is here. Run it on Exemplar.

Marshal for production agents. Relay for Cursor and Claude Code. Studio and DevX Assist for the rest of the stack — one policy surface.

Blog

From the team

View all