Documentation
Double Zero Database — Zero Trust, Zero Trace
00DB runs inside your own Kubernetes cluster. A sandbox is a pod — the 00DB app image and a database-engine image running together — and that pod is what talks to your production database, not a developer's laptop or CI runner. Developers get access to your Kubernetes cluster (ordinary RBAC, whatever your platform team already manages), never a direct network path to prod.
This documentation covers the Kubernetes-native version. If you're looking for SQL Simulator — the Docker-based, self-serve version built for non-production test data on your own machine — see the SQL Simulator product page instead; the two products share the same underlying engine and REST API (see API Reference, which applies to a 00DB deployment exactly as written) but are documented separately, since their governance and sandbox-lifecycle behavior genuinely differ — that's the whole subject of the next two pages.
00DB reaches production data, so every tier starts with a sales conversation, not a self-serve signup.
Compare Starter, Standard, and Multi on the 00DB product page.
- Zero Trust — the real network-isolation and data-governance mechanics behind the name.
- Zero Trace — how and when a sandbox pod deletes itself, and why that's guaranteed rather than best-effort.
- Benefits — why you'd reach for 00DB over another way to give a team database access.
- Supported Databases — which engines, and how each sandbox pod is put together.
- Kubernetes Install Guide — what the Helm chart sets up, what it deliberately doesn't, and what else you need running.