Stop wasting time setting up databases.
TrashDB provisions a real, isolated database container in under 5 seconds — and destroys it automatically when you're done. No Docker Compose files. No cleanup scripts. No shared test databases causing flaky tests.
runtime
database instances_
instances are auto-destroyed when the TTL hits zero
conn: postgresql://user:pass@localhost:5432/dbBuilt for real workflows
Integration & E2E tests
Each test run gets its own fresh database. No shared state, no test ordering bugs, no manual resets. Just reliable, repeatable tests.
CI / CD pipelines
Add one step to your GitHub Actions workflow. TrashDB creates the database, injects the connection string, and cleans up after your tests run.
Quick prototypes & demos
Spike a new feature, demo to a client, or experiment with a new DB engine — without touching your production infra or local setup.
Why TrashDB
Ready in <5 seconds
Containers are warm and waiting. No waiting for clusters to bootstrap, images to pull, or configs to propagate.
TTL-based auto-destroy
Set a time-to-live and forget about it. TrashDB tears down the container automatically when the timer hits zero — no cleanup code needed.
Zero infra overhead
No Dockerfiles, no Compose files, no Helm charts, no forgotten EC2 instances. One API call creates it. One API call (or a timer) destroys it.
Fully isolated per tenant
Every account gets its own API key. Containers are network-isolated and never shared across tenants. Your data stays yours.
SDK for every stack
Official SDKs for TypeScript, Python and C#/.NET. Or use the REST API directly. A GitHub Action for CI with zero boilerplate.
6 engines, one API
PostgreSQL, Redis, MongoDB, ChromaDB, Qdrant, Supabase — all provisioned through the same interface. Switch engines without changing your workflow.
Your next test shouldn't wait for a database.
Free tier includes 50 containers/month. No credit card required.
Get started for free