Revertix

Hi HN, I'm Martin. I built Revertix and I'm the only person working

on it.

I maintain WordPress and WooCommerce sites, and recovery was always

worse than it should be. An update breaks something, and the way back

is restoring a full host backup - if the host kept one, and if losing

the last few hours of orders is acceptable.

The tools that solve this are split up. A backup plugin doesn't know

about your staging copy. A migration plugin doesn't help you recover.

So you run three plugins that disagree about the current state of the

site. Revertix does staging, backups, import/export and plugin

rollback from one dashboard, because they're all the same problem:

knowing what a site looked like at a point in time, and being able to

put it back or move it somewhere else.

Two things took most of the work:

PHP timeouts. This is the number one reason these tools fail. On a

large site or a slow shared host, one long clone or backup hits the

execution limit and dies halfway through, leaving you worse off than

before. Every heavy job in Revertix runs as a resumable,

time-budgeted task - it works in short steps, saves its position and

picks up where it left off. Getting the database export to behave

under a low memory_limit meant rewriting it to stream rows in chunks

instead of assembling the dump in memory, which is where most of my

debugging time went.

Serialized data. WordPress stores serialized PHP arrays in the

database with byte-length prefixes, so a naive search-and-replace on

a URL corrupts every Elementor layout and WooCommerce setting on the

site. The replace has to unserialize, walk the structure, replace,

and reserialize.

The free version does staging, full backups, migration and rollback,

with no signup or account. Staging copies are login-protected and set

to noindex, and a safety backup runs automatically before any push to

live, so the action is reversible. Pro adds a detailed push/pull sync

where you review changes file by file and row by row and apply only

what you pick, plus scheduled backups.

I run it on my own client sites, which is most of the reason it keeps

getting better. Happy to answer anything, and I'd like to hear where

it breaks for you.