DEV & CI
Dev, test & CI environments
A full copy of the database for every branch, every CI run, every experiment — in under a second, at any size.
THE STATUS QUO
One shared staging database, seeded from a dump that takes an hour and drifted from production months ago. Every team knows this pain; almost none fix it.
HOW EzraDB DOES IT
Copy-on-write hard links — cloning is O(files), not O(data). A terabyte clones as fast as a gigabyte: sub-second.
Spin a clone per PR, run the suite, drop it. Detach one to keep as a long-lived environment.
Migrations and test suites run unchanged — Django, Rails, Prisma, SQLAlchemy, and TypeORM suites pass against EzraDB.
Real pg_dump works for fixtures and portability — verified against stock PostgreSQL 18.
Clone the database as it stood at a timestamp — reproduce yesterday’s bug with yesterday’s data.
*In development — not yet production-ready.
IN PRACTICE
When environments cost nothing, you stop rationing them.
-- sub-second, copy-on-write: hard links, not data copies
CREATE CLONE dev FROM ezra;
ALTER CLONE dev DETACH;
DROP CLONE dev;
MORE WAYS TEAMS USE EzraDB