01
The agentic kill switch
An autonomous agent doesn't get to finish what you didn't approve. Flip it and the agent's next action is refused mid-run, so the step it was about to take is the step that never happens.
Contain
When AI has to stop, you hold the switch.
Two switches, actually. One stops an autonomous agent before its next action. The other halts AI across every enrolled device and provider in one move. Both immediate, both reversible, both recorded.
01
Two switches
Two emergencies, and a switch for each.
Sometimes the problem is one agent: it's autonomous, it's mid-run, and it's about to take a step you never approved. Sometimes the problem is wider: a compromised tool, an injected instruction, or a decision to pause AI while you investigate. You shouldn't have to chase either one down device by device, so Verillian gives you a stop for each. Neither waits on a vendor.
02
How stopping works
Immediate, reversible, and on the record.
A stop you'd hesitate to use is no stop at all. These two are built to be pulled without ceremony and cleared without cleanup.
02
The fleet-wide halt
One move halts every connection through the checkpoint, on every enrolled device and for every provider, with no parsing in the way and no vendor's cooperation needed. The tools nobody registered go quiet with everything else.
03
Stops that leave proof
The activation itself lands in the signed record, and so does the moment you bring things back. Later, you can show exactly when AI stopped, who stopped it, and when it resumed.
03
The switch itself
Deliberate by design, typed to confirm.
Halting a fleet shouldn't be a stray click, so the console makes you type the confirmation before anything stops. Clearing it works the same deliberate way, and both moments are sealed the instant they happen.
04
The sequence
All clear, contained, and back again.
Watch the whole arc: traffic flowing, containment landing, the fleet coming back. Each next connection is refused at the checkpoint the moment containment lands, and every transition seals its own entry in the chain.
demo / all clear, contained, resolvedVerillian
all clearcontainedresolved
36
requests
32
decided
32
sealed
4
refused
your endpoints
ep-01
ep-02
ep-03
ep-04
ep-05
deciderefuse
every provider
claude.aidecided
openaicaptured
deepseekcaptured / unapproved
perplexitycaptured / unapproved
your private server
signed chain, held under your key09:14:52.108RESOLVEcontainment resolved / traffic resumesa41f…09c2
09:14:49.311CONTAINfleet contained / next connection refused7c2e…d1a2
09:14:47.902LOGperplexity / prompt captured to the chain3b90…44aa
09:14:46.585REDACTclaude.ai / patient lookup, token hiddene17d…5f08
09:14:45.207ALLOWclaude.ai / summarize the note90bc…12e7
Ed25519 signed / SHA-256 hash-chained / held under your key / demo data
Contain the fleetstandby
The point
The reason the switch exists.
The goal is not to stop AI. It is the opposite, to let institutions finally say yes.