Inspiration

Autonomous agents can move faster than human operators, but cloud infrastructure gives mistakes a real cost: overspend, unsafe teardown, data leakage, and actions that are difficult to reconstruct. Warden was built to give agents useful freedom inside enforceable boundaries.

What it does

Warden is a zero-trust governance control plane for Gemini-powered agent fleets. Every proposed action passes through policy before it reaches a provider. Warden enforces approved regions and machine types, authoritative spend ceilings, mandatory resource lifetimes, mission-scoped approval envelopes, role-aware human approval, and multi-party quorum for sensitive operations.

The operator dashboard combines a fleet terminal, approval inbox, live budget and TTL status, policy simulation, historical replay, cloud-security findings, and a cryptographically chained audit trail. In live mode, durable workflow state and approvals are stored in Firestore, while Cloud Tasks can resume parked workflows after approval.

How we built it

The fleet uses Google ADK and the Google GenAI SDK with Gemini 3.5 Flash as the primary model. A runner-level ADK plugin intercepts tool calls before execution. Pure policy evaluation, a trusted cloud rate card, transactional reservations, and single-use approval grants keep authority outside the model.

Cloud Run hosts the control plane. Firestore provides durable workflows, approvals, mission envelopes, reservations, memory, and ledger checkpoints. Optional Google Cloud integrations collect asset drift, Security Command Center findings, billing evidence, Model Armor results, and Cloud Trace telemetry.

Challenges

The hardest problem was making controls durable under retries and concurrency. An approval cannot become reusable authority, a provider timeout cannot silently release budget, and two operators must not accidentally cast the same quorum vote. We addressed these with idempotency keys, transactional reservations, distinct verified identities, expiring grants, and conservative accounting for unknown outcomes.

We also separated simulation from enforcement. Policy Lab and replay never call providers, while the enforcement path fails closed.

What we learned

Governed autonomy works best when policy is visible before approval and evidence is useful afterward. Solo builders need safe templates and clear spending limits; enterprises need identity hierarchy, quorum approvals, durable workflows, and immutable evidence. The same control plane can serve both when the underlying contracts stay explicit.

What's next

Next we will expand the bounded live GPU lifecycle into additional managed-cloud adapters, deepen production evidence from Cloud Run, Cloud Trace, and security posture sources, and preserve the same policy and approval boundaries as fleets scale.

Built With

Share this project:

Updates