Auto-protect
Killswitch
Killswitch is the hard budget cap GCP still leaves as opt-in plumbing. Auto-Protect enforces your threshold on any project — detach billing for a full project-wide stop, or surgically halt the high-cost services that cause runaway bills (BigQuery, Cloud Run, Vertex AI and more), resources left intact. Re-enable in one click after review. The single feature that could have prevented the $72,000 overnight invoice.
Walkthrough
Per-project protection — and exactly what happens the moment a threshold is crossed.
An 8×A100 training job left running over a single weekend — and forgotten endpoints bill 24/7.
One un-partitioned query, re-run on every dashboard refresh, scans terabytes — thousands by lunch.
With Zenta, set Killswitch on both. Cap Vertex AI and BigQuery at a budget you choose — so unexpected spikes like these never reach your invoice.
Cross the project threshold and Pulse calls the GCP Billing API to detach the billing account — every service in the project stops incurring cost at once.
Best for sandboxes and non-production.
Give a single service its own budget. Cross it and Pulse stops just that service — cancels BigQuery jobs, pauses Vertex AI endpoints — while the rest of the project keeps running.
Resources stay intact; nothing is deleted.
The full experience
What you see below is a preview. Share your details and we'll email you a private link to the full interactive tour of Killswitch — every module, click-through, at your own pace.
An interactive, click-through tour of every Killswitch module — explore at your own pace. Drop your details and we'll email you a private link. No call required. (Prefer a live walkthrough with an engineer? Book a guided demo.)
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. Native caps are arriving, but only in limited preview for a handful of services. A leaked API key, a runaway Cloud Run scaling event, a $7 budget test that compounds overnight to $72,000 — an alert stops none of them.
When threshold is crossed, Pulse detaches the project's billing account — or halts just the offending service, resources left intact — then fires an email + Slack notification and waits for a human to re-enable. The meter stops within seconds of the data reporting the breach.
Production stays unprotected if you want it to. Sandbox accounts get a hard cap. The toggle is yours — per project, per service, per 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