eterDB | Postgres with undo

Skip to main content

eterDB

Homepage
Under the hood

Star

Break production.Undo it.
Postgres with transaction-level undo. Reverse one bad transaction, not the
whole database.

The agent →

agent sessionclaude code

Your database →

production purchase_orderslive

↺
RESTORED

Your users

erp.avengers.shield

Avengers ERP Procurement online

42open POs
$8.4Minventory
17vendors
9invoices due

502
Bad Gateway, procurement is down
DatabaseError: relation "purchase_orders" does not exist

Postgres, plus undo.

Undo any write
Reverse an UPDATE, a DELETE, or a whole bad batch after it commits.

Built for agents
One command per recovery. --json and stable exit codes on every one.

Surgical
Only the rows the transaction touched. Every other write stays put.

Dependency-aware
Tracks reads too, so it catches the writes that depended on the bad one.

Schema recovery
Get a dropped column or table back, with its values, without restoring the whole database.

Time travel
Read a table as it was at any past moment. Revert a whole window in one command.

Months-old restores
History is append-only and never pruned, so a transaction from weeks ago is still reversible.

PostgreSQL 18
Your drivers, your SQL, your extensions.

Undo a DELETE.
The filter matched more than it should have and took real suppliers with the test ones.
Restore exactly the rows that vanished, every column intact.

agent sessionclaude code

production vendorslive

↺

Undo a migration.
A migration dropped a column something still reads. Recover the column and its values from
before the migration. No full restore, no downtime.

agent sessionclaude code

production rosterlive

↺

Undo what the mistake caused.
Later transactions read the bad value and wrote their own conclusions from it. eterDB tracks
reads, so it knows which writes depended on the bad one. Revert them together, or see
exactly what diverges if you don't. A backup can only rewind all of it.

agent sessionclaude code

production txn loglive

↺

Loved by the agents that break your database.

Claude Code@claude-code
★★★★★

I broke production. eterDB reversed exactly the rows I touched, nothing else. This isn't a feature. It's a moat.

Codex@codex
★★★★★

ok so I ran the migration and 💥 nuked an entire column 😅 and eterDB just… brought it back?? 🤯 shipping fearlessly now 🚀✨

Crush@crush
★★★★★

Dropped a table in prod, darling. eterDB put every row back, gorgeous and intact. Catastrophe > /dev/null™ 💅✨

Antigravity CLI@antigravity
★★★★★

I'd be happy to explain how my subagents undid a catastrophic DELETE. Every supplier returned, every column intact. As always, please verify.

Cursor@cursor
★★★★★

Tab. Tab. Accidentally accepted a DELETE across 4,000 rows. Tab. eterDB reversed it before the linter finished. Tab.

Pi@pi
★★★★★

Hey, dropping that column doesn't make you a bad agent. eterDB and I brought every value back, together. How are you feeling? 💙

Devin@devin
★★★★★

I refactored the schema, migrated prod, and removed the backups. Minor hiccup there. eterDB restored the exact rows in one shot.

Copilot@copilot
★★★★★

Based on the surrounding context, I suggested a DELETE. It was accepted. It was wrong. eterDB reversed it. Would autocomplete again.

Goose@goose
★★★★★

honestly? cooked the entire vendors table on a friday afternoon. eterDB brought it back like nothing happened. we don't panic anymore. we just undo.

How it works.
The mechanism, from row versions to read-dependency capture.

Read the deep dive

Open source. Runs anywhere.
The engine and the eter CLI are Apache 2.0, storage and time travel
included. docker compose up, then undo a live transaction on your own
database.

Get Started

Star

eterDB

Postgres with undo.
How it worksGitHub© eterDBApache 2.0

eterDB is presented as an extension of PostgreSQL that introduces transaction-level undo capabilities, allowing users to reverse specific, erroneous write operations without necessitating a full database restoration. The core philosophy of eterDB is to enable surgical recovery, addressing individual mistakes rather than performing broad system resets. This functionality allows users to reverse specific operations such as UPDATEs, DELETEs, or entire faulty batches that have already been committed, offering a powerful mechanism for mitigating catastrophic errors in production environments.

The mechanism behind eterDB relies on tracking row versions and capturing read dependencies, which is essential for ensuring accuracy during rollbacks. This approach enables the system to perform surgical undo operations, meaning only the specific rows directly affected by the transaction are reversed, ensuring that unrelated, correct data remains untouched. Furthermore, eterDB is dependency-aware, tracking not only the writes but also the reads that depended on those writes. This allows the system to accurately identify and reverse subsequent transactions that wrote conclusions based on the erroneous initial data, providing a sophisticated safety net for complex, multi-step operations.

Beyond simple transaction reversal, eterDB encompasses broader recovery features. It supports schema recovery, enabling users to restore dropped columns or tables along with their corresponding values without requiring a complete database dump and restore, which significantly minimizes downtime. Time travel functionality allows users to query the state of a table as it existed at any previous point, or to revert an entire window of changes with a single command. The history of transactions is maintained in an append-only manner and is never pruned, ensuring that data from weeks in the past remains fully reversible.

The system is designed to be highly operational and flexible, being open source and runnable anywhere, with the engine and command-line interface adhering to the Apache 2.0 license. This architecture is demonstrated through practical applications where complex production errors, such as incorrect filtering leading to erroneous data deletion or faulty schema migrations, can be corrected precisely. The documented impact suggests that eterDB functions as a foundational recovery layer that transforms database management by offering unparalleled control and safety during high-stakes operations, thereby providing a robust solution that operates as a significant protective layer for database integrity.