Benefits
Why reach for 00DB instead of another way to give your team database access.
- No direct prod network access for developers
Developers get access to your Kubernetes cluster, not a network route to production — only the sandbox pod itself talks to prod over the network. See Zero Trust.
- Ordinary Kubernetes RBAC, nothing new to run
Access is scoped with the same role-based access control your platform team already manages — no separate access-control system to stand up or learn.
- Nothing left standing
Every sandbox is a disposable pod that deletes itself on a schedule you can't accidentally defeat by staying logged in — see Zero Trace. There's no lingering copy of production data to lose track of.
- Built-in data governance and an audit trail, on every tier
Your DBA sets limits directly on your own database — a cap on how much sensitive data any one pull can return, a separate daily cap across your whole team, and specific records that only approved users can retrieve. Every check is logged, so there's a real, queryable record of who retrieved what and when. This is a 00DB-only capability — see Zero Trust for the full mechanics.
- Production-realistic data, without production access
Unlike SQL Simulator, which is built for non-production test/dev databases, 00DB is meant to point at real production data — the governance and self-destruct guarantees above exist specifically so that's safe to do, instead of asking every team member to make their own judgment call about what they're allowed to pull and for how long.
- Runs on your own infrastructure
00DB runs as pods inside your own Kubernetes cluster — your source data and every sandbox both stay on infrastructure you control; nothing is uploaded to an external service to build the subset.