EterDB, a Postgres fork that makes it easy to recover from incidents
Undoes one bad Postgres transaction — no full restore, no other rows touched
EterDB is a Postgres 18 fork with transaction-level undo — reverse one bad UPDATE, DELETE, or migration and it restores exactly the rows touched. It tracks read-dependencies too, so it also catches later writes that relied on the bad one, something a normal backup can't do since a backup only rewinds everything at once. It's built for coding agents: one CLI command per recovery, with --json output and stable exit codes. History is append-only and never pruned, so even a transaction from weeks ago stays reversible, and the engine plus the eter CLI are open source under Apache 2.0, self-hosted via docker compose.
What holds up
- +Reverses a single transaction's rows, not a full restore — everything else stays untouched
- +Tracks read-dependencies, so it also catches later writes that relied on the bad one
- +Open source under Apache 2.0, self-hosted with docker compose — no vendor lock-in
- +History is append-only and never pruned — a transaction from weeks ago is still reversible
Mind the limits
- −Postgres only — no undo for MySQL, MongoDB, or other databases
- −Self-hosted via docker compose — no managed cloud version mentioned on the page
Featured here? Take the badge
Put it on your site — it links back to this review. Free for every listed product, always.
<a href="https://stillworks.dev/products/p/eterdb-a-postgres-fork-that-makes-it-easy-to-recover-from-in/"><img src="https://stillworks.dev/badge/eterdb-a-postgres-fork-that-makes-it-easy-to-recover-from-in.svg" alt="Picked by StillWorks" width="250" height="54"></a>