Backups

Backups snapshot the database and write it to a JSON file you can download. It is belt-and-braces cover — something you hold yourself, independent of the platform underneath.

Sessions and verification tokens are left out on purpose. A backup should hold your data, not a record of who happened to be signed in when it was taken.

Running one

Back up now starts the job. When it finishes, the confirmation names the file that was written, how many rows it holds and how large it came out.

Recent backups lists the previous ones with their creation date, size, row count and number of tables. Download fetches the file; Delete removes it, and that cannot be undone.

Restoring is not a button

There is no one-click restore, and that is a deliberate choice: a button that overwrites the whole database has too much reach to sit out in the open.

If you need to restore, it is an operational procedure we run together with you. The steps are on the page, and they amount to provisioning a fresh database, bringing the schema to the same revision the backup was taken at, and loading the tables back in. Everyone signs in again afterwards, since sessions are not in the backup.

The platform has its own safety net too

The database can be rolled back up to 30 days through Cloudflare. The backups here are in addition — for retention off Cloudflare, and for testing against a particular schema version.