Neon · verified backups
Neon's branches are brilliant. They're still not backups.
Point-in-time restore and branching protect you inside Neon. They don't protect you from account-level problems, retention windows, or the platform itself. Firedrill keeps an encrypted, independent copy — and proves it restores.
PITR history has a window
Neon's restore window depends on your plan (hours to days). Slow-burn data corruption — a subtly wrong UPDATE running for weeks — outlives the window. A monthly GFS archive doesn't.
Everything lives in one control plane
Branches, PITR history, and your primary all share the Neon account. Independence means a copy that survives losing that account entirely.
Restore-tested, not just stored
Every Firedrill backup is restored onto a fresh Postgres matching your major version, with schema-hash, row-count, amcheck and query checks. You get the recovery-time number for your runbook, too.
Frequently asked
Does Firedrill work with Neon's pooled endpoints?
Yes — pooled (-pooler) endpoints work fine for pg_dump-based backups. We detect your Postgres major version automatically.
Will backups wake my scale-to-zero compute?
Yes, a backup run wakes the endpoint like any connection would, for the duration of the dump. Schedule-aware jitter spreads the load.
Can I restore a Firedrill backup back into Neon?
Yes — every backup is a standard pg_dump custom-format archive. The dashboard gives you a 15-minute presigned download and the exact pg_restore command.