Replay any run
Run a past task again, step by step, against the same inputs.
Replay 14:31:40 · refunds-agent v14 · 6 steps
AI agent control plane
Every agent,on the board.
Signalbox routes every AI agent you run in production, records each action in one register, and lets one person hold them all.
Time
Agent
Task
Route
Cost
Status
14:32:24
Lever 1
4 live runs held at signal
All routes
£0.000
held by you
14:32:18
invoice-agent v6
Match INV-30927 · $1,284.00
NetSuite → Slack
£0.031
Running
Held
14:32:09
renewals-agent v4
Quote Q-5521 · $18,400.00
HubSpot → Gmail
£0.022
Waiting
Held
14:31:57
triage-agent v9
Credit ZD-20417 · £15.00
Zendesk → Stripe
£0.004
Cleared
14:31:42
chargeback-agent v8
Dispute order 48213 · £42.10
Stripe → Gmail
£0.044
Waiting
Held
14:31:42
Read dispute dp_1190 from Stripe
OK
14:31:43
Interlock: order 48213 is on refunds-agent v14’s route
Locked
14:31:43
Waiting at signal S4 for Finance on-call
Approval needed
14:31:40
refunds-agent v14
Refund order 48213 · £42.10
Stripe → Zendesk
£0.018
Running
Held
14:31:22
access-agent v3
Figma seat IT-7712 · $15.00
Okta → Jira
£0.006
Cleared
14:31:05
payouts-agent v2
Payout PO-88140 · $3,960.00
Stripe → NetSuite
£0.027
Cleared
Hold all runs
Clear all runs
Pull to hold. Pull again to clear.
In production at
Fernhollow Bank
Quillo
Tallowmere Health
Orbisly
Cobble & Kite
Vantagrid
Sample names. Yours could be here.
Three lines to the board.
To begin, install the SDK and wrap the agent you already have. No rewrite, no new framework.
On its next task, every run lands in the register with its route, cost and status.
From then on, your rules set the routes. An agent can only take the routes they allow.
import { Signalbox } from "@signalbox/sdk";
const box = new Signalbox({ apiKey: process.env.SIGNALBOX_KEY });
export const agent = box.wrap(refundsAgent, { name: "refunds-agent" });
Python and Go SDKs too.
Conflicting routes can’t be set.
Signal boxes have used interlocking since the 1850s. Set one route and the levers for any crossing route lock. Signalbox does the same for AI agents: guardrails that block conflicting actions before they run.
Two agents want order 48213.
refunds-agent v14 sets its route first. It locks.
chargeback-agent v8 gets a red signal. It waits, on the record.
Order 48213
S3
S4
Route A · refunds-agent v14
Refund £42.10
Clear
Locked
Route B · chargeback-agent v8
Dispute £42.10
Clear
At danger
Plan view. Two routes, one crossing, one order.
Controls, not dashboards.
Six things you can change while the agents are running.
Budget cap per agent
Set a spend limit per agent. At the cap, its runs wait at a signal.
Cap £40.00 a day · £31.12 used
Human approval step
Put a person on any step, and the run waits until they say yes.
Step 3 · Refund over £100 · Approver: Support lead
Swap models, no redeploy
Change the model behind an agent in config, and the next run uses it.
Model A → Model B · from next run
PII masked in transit
Names, emails and card numbers are masked before a prompt reaches the model.
j***@f***.com · •••• 4417
Alerts in Slack
Get a message in the right channel when a run waits, fails or hits a cap.
#finance-ops · invoice-agent v6 is waiting at S2
Held at red until you clear it.
Mark the steps that need a person. The run stops there, and moves when someone says so.
Arriving
refunds-agent v14
Refund order 51877 · £240.00
Running
The run reaches a step you marked for review.
Waiting at signal
refunds-agent v14
Refund order 51877 · £240.00
Waiting
Cleared
Decline
It stops. Nothing moves until someone approves.
Cleared
refunds-agent v14
Refund order 51877 · £240.00
Cleared
Approved. The run finishes, and the register keeps who said yes.
Support refunds
A refund over the £100 limit waits for a support lead.
Finance ops
A matched invoice waits for a controller before payment is booked.
IT access
Admin rights on a billing workspace wait for the system owner.
Sales ops
A discount past the 15% rule waits for the deal desk.
Built for the audit.
The register is your audit log, and the record. Here is how it is kept, and who can touch it.
Hosting
Run it in our cloud, or self-host it inside your own VPC.
Data region
Pin your register to one region, and it stays there.
Sign-in
SSO over SAML or OIDC. SCIM adds and removes people for you.
The register
Every entry is signed and kept for 400 days. Nobody can edit it, us included.
Lever access
Roles decide who can hold, clear or approve, agent by agent.
Audits
SOC 2 Type II (sample). Report on request, under NDA.
Priced per run, not per seat.
Your whole team can watch the board. You pay for the runs it records.
Depot
One team putting its first agents into production.
Recommended
Junction
Several teams, several agents, rules that cross between them.
Network
Agents across regions, with self-hosting and audit needs.
Price
Per 1,000 runs · TBC
Per 1,000 runs · TBC
Annual contract
Agents on the board
Up to TBC
Up to TBC
As many as you run
Interlocking rules
Ready-made rules for common conflicts
Your own rules, across teams
Your own rules, across teams and regions
Human approval
On any step, one approver
On any step, with approval chains
Approval chains with deputies and out-of-hours cover
Register kept for
30 days
400 days
As long as your policy says, in your own storage
Hosting and sign-in
Our cloud, Google or Microsoft sign-in
Our cloud, SSO and SCIM
Self-host in your VPC, SSO, SCIM, region pinning
Every plan: unlimited seats, the hold lever and Slack alerts. Prices and limits are placeholders on this concept site.
Before you book.
What is Signalbox?
Signalbox is a control plane for AI agents in production. It routes each agent task, records every action in a signed register, blocks conflicting actions with interlocking rules, and lets one person hold any run, or all of them, with a single lever.
How is Signalbox different from an AI observability tool?
Observability tools show you what an agent did. Signalbox also decides what it may do next. Each action is checked against your rules before it runs, so a conflict is stopped at the signal, not found in a dashboard the next morning.
Which agent frameworks and models does Signalbox work with?
Signalbox wraps the agent, not the model, so it works with the stack you already run. Changing the model behind an agent is a config change. The next run uses it, with no redeploy.
What happens when someone pulls the hold lever?
Every live run stops before its next step and waits. Nothing is cancelled and no state is lost. The register logs who held the runs and when. Pull the lever again and each run carries on from the step where it stopped.
Can we self-host Signalbox?
Yes, on the Network plan. Signalbox runs inside your own VPC, so prompts, outputs and the register stay on your network. On Depot and Junction we host it, with your register pinned to the region you choose.
What happens in a Signalbox demo?
A call with an engineer. We connect a sample agent, put its runs on the board, set one interlocking rule and pull the lever. Bring the workflow that worries you most, and we’ll map its routes with you.
Book a demo
Signal cleared. We’ll email you to find a time.
That didn’t go through. Check the address and try again.
We’ll email you once to find a time. This is a concept site, so please don’t send real details.