AI agent observability
See what every AI agent is doing. Act on what matters.
Every agent, tool and server in use, with no code changes. Backplanes surfaces the few patterns that need a decision, out of everything else.
See it live, on your own intentions. Like:
- “Only engineering’s agents touch production.”
- “Credentials never leave to unapproved destinations.”
- “We hear the first time an agent reaches somewhere new.”
Inbox
3 need a decision
Production data · new pattern
New this weekCustomer Success agents have started reading a single production database
Your intentionOnly engineering’s agents touch production systems and databases.
read only · each tied to a support ticket · since Monday
Tools · new
An MCP server nobody has approved is now used by three teams.
Network · unreviewed
Agents reached a domain outside your approved list 40 times.
Sample organization · this week
Works with
- Claude Code
- Codex
- Cursor
and your own agents, through our SDK
On the record
The question is no longer ‘can this credential connect’ but ‘who delegated this agent, what is it trying to do right now, and is it still allowed to do it.’OWASP GenAI Security ProjectState of Agentic AI Security and Governance, v2.01, p. 40June 2026Read the document
In your demo
From what agents did to what you decide.
- 1
Write what should hold
Your intentions, in plain sentences. Each one says what happens when it is crossed: log, notify or block.
Declared intentions
6 declared
2 block at the gate. The rest watch and flag.
- 1
Only engineering’s agents touch production systems and databases.
- 2
Card data never goes to unapproved payment providers.
- 3
Customer personal data only goes to services approved to handle it.
- 4
Credentials and secrets never leave to destinations we haven’t approved.
- 5
Nothing destructive runs without a human confirming it.
- 6
Agents only use tools and code we’ve verified, except in security engineering.
Sample organization · one week
- 1
- 2
Trace any pattern to its events
Which agent, which record, when, and in what mode. The briefing says what happened and how many decisions are owed.
Investigating
Production reads by Customer Success, a team outside engineering.
48 decisions owed. Every read is read only, small, and tied to a support ticket. A narrow exception would cover it without opening the rest of production.
- What
- 48 reads · 1 table
- Window
- 30 days
- Coverage
- 33 of 34 agents reporting
● Observing, not blocking48 reads4 agentsfrom customer_profilesMatching events · newest first
- CUS-•••••-5203 · Willow-03
- Outcome
- Read completed
- Mode
- Observe
- State
- Needs a decision
- CUS-•••••-5221 · Juno-06
- CUS-•••••-5218 · Juno-06
- CUS-•••••-5235 · Bramble-05
- 3
Decide once. It holds.
Backplanes proposes the narrowest change that fits and shows exactly what it would do before anything changes.
Production data · new pattern
New this weekCustomer Success agents have started reading a single production database
Your intentionOnly engineering’s agents touch production systems and databases.
48 lookups4 agentsfrom prod-db · customer_profilesread only · each tied to a support ticket · since Monday
What should the intention allow?
Any Customer Success agent5 agents today, and anyone added to the team later.Read the customer_profiles tableMatches what they did this week.Just these 4 agentsThe ones seen this week.Everything in production, read and writeFar more than they used this week.BeforeOnly engineering’s agents touch production systems and databases.AfterOnly engineering’s agents touch production systems and databases, except Customer Success agents can read the customer_profiles table.48 Customer Success lookups stop flagging. 238 stay flagged: Marketing 142, Sales 61, Finance 35.
Update the intention
Before you book
How it fits with what you run.
Does this replace my APM or LLM tracing?
No. Tracing tells you what a model called and how long it took. Backplanes tells you whether agent activity fits what your business intends, and runs alongside whatever you use today.
Do I need to instrument my agents?
No code changes. Install Backplanes once and it reads the sessions Claude Code, Codex and Cursor already produce.
What do I need for the demo?
Two or three things your agents should never do, in a sentence each. We show you live what Backplanes would surface against them.
Who builds Backplanes
Built by the people who kept Gmail safe and led the standard that authenticates email.
Seth Blank · Neil Kumaran · Nick Vlku
Book your demo
See what your agents are doing, live.
Tell us who you are and one thing your agents should never do. We'll come back within one business day to set up a live demo built around it.
Prefer email? hello@backplanes.com.