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.
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.
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.
A stop you'd hesitate to use is no stop at all. These are built to be pulled without ceremony and cleared without cleanup.
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.
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.
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.
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.
The goal is not to stop AI. It is the opposite, to let institutions finally say yes.