Compressed Docker DB snapshots
Pull a masked, prod-like DB into compose or minikube. Source from production, a read replica, or staging.
Trusted by world class organizations
From production to your laptop in three steps
Connect your source once
Production, a read replica, or staging: a connection string is all Baseshift needs. Masking happens during the copy, so nothing sensitive ever enters a snapshot.
Snapshots build themselves
Baseshift packages your masked database as a compressed Docker image, rebuilt daily by default or on demand. Tagged and versioned like any other image your team ships.
Start locally
Change one image line and get a prod-like database on localhost. Works anywhere Docker works, and keeps working with no connection to Baseshift.
$ docker compose up
Real data on your laptop, without the problems that usually brings
Seed scripts are easy. They are also why the bug never reproduces locally.
Real data, not fixtures
Seed scripts produce tidy rows that never crash. Production distributions, NULLs, odd unicode, and tenant skew are where bugs live, and they come through in every snapshot.
Masked before it reaches a laptop
Anonymization is part of building the snapshot, so sensitive values never leave your infrastructure. The image your developers pull was never anything but clean.
Share it like an image
Teammates in other regions, accounts, or VPCs pull the same tag from the registry. Nobody re-copies from production, and nobody waits for a dump.
A real database in a container. Not a mock.
Standard databases in standard containers, with storage that was built for databases.
PostgreSQL, MySQL, MongoDB, and DocumentDB.
Compression up to 1:5. Baseshift snapshots start up while staying compressed, because storage decompresses in flight.
Baseshift clones are hyper lightweight. Run as many local copies as you need without multiplying storage the way a normal Docker volume would.
Snapshots rebuild automatically every day. Need the state from an hour ago? Rebuild on demand.
Once pulled, a snapshot runs with no connection to Baseshift. Trains, planes, and bad hotel wifi included.
Pull one or more tenants, a time window like last month, or another slice of the database for smaller, faster local snapshots.
Start free. Stay free until it's useful.
The free tier includes 150 GB of snapshots, enough to put a real database on every laptop on the team. Pro from $30/month when you need more.
Get started for freeSee pricing →FAQ
Can I host Baseshift on prem/BYOC?
Yes, and the data never leaves your network.
Does my laptop need to hold the full database?
No. Snapshots stay compressed on disk and while running, and flexible subsetting lets you pull a fraction of the data: one or more tenants, a window like last month, or another slice. Compression up to 1:5, so a 50 GB database can land around 10 GB.
Is sensitive data ever on my machine?
No. Masking happens while the snapshot is built, before anything is published to the registry. The image your team pulls never contained the real values.
How fresh is the data?
Snapshots rebuild daily by default, or on demand when you ask. On-prem deployments can also build replication-based delta snapshots for Postgres and MySQL, where each day's changes ship as a thin additional image layer.
Which engines are supported?
PostgreSQL, MySQL, MongoDB, and DocumentDB. Self-serve SaaS covers PostgreSQL 9.6-18; on-prem includes MySQL, MongoDB, and DocumentDB.
Does it work offline?
Yes. Once a snapshot is pulled, everything runs locally with no connection to Baseshift.
Do I need to change my app?
No. The snapshot is a standard database on a standard port. Your client, ORM, and migrations behave exactly as they do against production.
What permissions does Baseshift need on my database?
A read-only role on your source. Baseshift never needs write access to production.