Auto-protect
Killswitch
Killswitch is the hard GCP budget cap Google won't ship. Per-project Auto-Protect — cross your threshold and Pulse disconnects billing automatically. Re-enable in one click after review. The single feature that could have prevented the $72,000 overnight invoice.
Walkthrough
Per-project Auto-Protect with threshold and toggle.
Auto-Protect (Kill Switch) automatically disconnects billing for a project when spending exceeds the threshold, preventing further costs. Configure it per project below.
When threshold is exceeded, Pulse disconnects the project's billing account automatically and notifies your team via email and Slack. One-click re-enable after review.
Why this exists
“Budgets do not automatically prevent the use or billing of your services.”
— Google Cloud Documentation, verbatim
GCP budget alerts are informational — emails after the fact. They have never been able to cap usage. A leaked API key, a runaway Cloud Run scaling event, a $7 budget test that compounds overnight to $72,000 — none of those are stopped by an alert.
When threshold is crossed, Pulse's Killswitch service disconnects the billing account on the project, fires an email + Slack notification, and waits for a human to re-enable. The meter stops the same minute.
Production stays unprotected if you want it to. Sandbox accounts get a hard cap. The toggle is yours — every project, every threshold, decided by your team.
We walk you through every Pulse module — BillPulse, SecureMonitor, PulseArc, Ollie, Killswitch — on a representative GCP environment loaded with realistic data, together with a certified engineer from the D3V team. About 30 minutes.
What you'll see in the demo
A one-off, no-charge audit that surfaces critical SCC findings in your GCP — a complimentary service from D3V to help teams understand their security gaps before adopting Pulse.
Get in touch