Testate

Git for your test database. Snapshot it, break it, put it back in seconds.

Testate runs beside the system under test, takes data-only snapshots of its databases, and puts any of them back on demand. One container, one volume, no account, no telemetry. Version 1.1.0.

"Could you wipe the transactions on UAT? I can't create another order." "Reset DEV to the seed again please, the master data is off."

So a developer stops, SSHes in, and resets a database by hand. Or writes a reset endpoint that must never ship, and sometimes ships. Meanwhile QA does not automate, because every automated run needs a clean database first. And nobody lets an AI agent near a shared database to debug anything, because one hallucinated DELETE is one too many.

Take a state. A data-only snapshot of every database in a project, at one moment, with a name and tags.

Break it. Run the suite, click through the app, edit rows in the grid, load a fixture.

Check it out. One click or one API call puts every database back and reports per database. A stash is taken first, so even that is reversible.

See what moved. Diff two states, or a state against the live database, down to the changed cell.

Nothing gets added to your application. Testate is a separate service that talks to the databases directly.

The same image is on Docker Hub as snowfluke/testate , under the same tags.