Databases
Backups
Automate and manage database and WordPress backups per project
Overview
The Backups tab lets you configure automated backup schedules for databases and WordPress sites within a project. You can also trigger manual backups and restore from any saved backup file.
Backups are available on paid plans only. Trial accounts cannot create backup configurations — the create backup button is disabled on trial.
Backup retention
Your plan’s backup retention period is shown at the top of the Backups page. Backup files older than this period are automatically removed.
| Plan tier | Retention |
|---|---|
| Trial | Backups disabled |
| Paid plans | Shown in your billing page |
Creating a backup configuration
- Go to your project → Backups tab
- Click create backup
- Choose the Backup type:
- Database — backs up a specific PostgreSQL database
- WordPress (full site) — backs up the entire WordPress installation
- If Database is selected, choose which database to back up
- Choose a Schedule:
- Daily at 2:00 AM (default)
- Daily at 3:00 AM
- Daily at 4:00 AM
- Weekly on Sunday at 2:00 AM
- Monthly on the 1st at 2:00 AM
- Click Create backup
Managing backups
Each backup configuration card shows:
- Type (Database or WordPress)
- Status (
activeordisabled) - Schedule in human-readable form (e.g. “Daily at 02:00”)
- Last backup time
Trigger a manual backup
Click backup now on the backup card to run an immediate backup outside the schedule.
View backup files
Click view files to list all stored backup files for that configuration. Select a file to restore from it.
Restoring a backup overwrites all current data in the target database. This cannot be undone.
WordPress restores
WordPress backup files can be viewed but restore is not available through the dashboard. Contact support if you need to restore a WordPress backup.
Delete a backup configuration
Click delete on the backup card to remove the configuration. This deletes the configuration but does not delete stored backup files from the destination.
Backup destination
Backups are stored in the destination configured for your organization (typically an S3-compatible object store). The destination ID is shown when viewing backup files and can be changed if needed.