Backups & Restore

Take a snapshot of your database before a risky change, and roll back to it if something goes wrong. Snapshots live in the Backup tab of the database workspace.

Taking a snapshot

Click Create snapshot and Waymaker captures the full state of your database — all your tables and all their data — at that moment. Each snapshot shows when it was taken and how large it is.

A good habit: take a snapshot right before applying a big migration or a bulk data change. It's your undo button.

Restoring

To roll back, choose a snapshot and click Restore.

Restoring overwrites your current database with the snapshot's contents. Anything changed since that snapshot was taken is replaced. Because it's destructive, you'll be asked to type "restore" to confirm.

Deleting a snapshot

Remove snapshots you no longer need with Delete (type-to-confirm). This frees the space they use.

Who can do this

Only the database's creator can restore or delete snapshots. This keeps a destructive action in the hands of the person who owns the database, even on a team.

What's included today

Snapshots are manual — you take them when you want one. The current version does not include:

• Scheduled or automatic backups — you create each snapshot yourself.
• Retention policies — snapshots stay until you delete them.
• Point-in-time recovery — you restore to a snapshot you took, not to an arbitrary moment.

If you want a safety net before a change, the rule is simple: take a snapshot first.

Snapshots vs branches

Both protect you, differently:

	Use it to…
Snapshot	Freeze production so you can undo a change you're about to make to production
Branch	Test a change on a separate copy so production is never at risk in the first place

For everyday feature work, branches keep production untouched. For a deliberate change to production, snapshot first.

Next Steps

• Changing Your Schema — snapshot before a big one
• Branches — test changes off production entirely
• The Database Workspace — the Backup tab