Contain

When AI has to stop, you hold the switch.

Page updated September 25, 2026

Two switches, actually. One cuts off a single AI provider for everyone. The other halts AI across every enrolled device and provider in one move. Both reversible, both recorded.

01
Two switches

Stop exactly what's wrong, not everything else.

Sometimes the problem is one provider: a vendor incident, or a service you need to pause while you review it. Cut it off for everyone and nothing else stops. And when the problem is wider, a compromised tool, an injected instruction, or a decision to pause AI while you investigate, the second switch halts everything. Neither waits on a vendor.

02
How stopping works

Fast to pull, reversible, and on the record.

A stop you'd hesitate to use is no stop at all. These are built to be pulled without ceremony and cleared without cleanup.

01

The provider cutoff

When one AI provider becomes the problem, cut it off for everyone in one move. The next connection to it is refused at the checkpoint, on every enrolled device.

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 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
anthropic apidecided
openaicaptured
deepseeknot governed
perplexitynot governed

your own infrastructure

signed chain, held under your key
09:14:52.108RESOLVEcontainment resolved / traffic resumesa41f…09c2
09:14:49.311CONTAINfleet contained / next connection refused7c2e…d1a2
09:14:47.902LOGopenai / prompt captured to the chain3b90…44aa
09:14:46.585REDACTanthropic api / patient lookup, token hiddene17d…5f08
09:14:45.207ALLOWanthropic api / 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.