Backups
Every Flokk database is backed up automatically. Retention depends on your plan.
Backup schedule
| Plan | Frequency | Retention | Method |
|---|---|---|---|
| Starter | Continuous | 3 days | WAL archiving (PITR) |
| Pro | Continuous | 7 days | WAL archiving (PITR) |
| Dedicated | Continuous | 7–30 days (configurable) | WAL archiving (PITR) |
Where backups are stored
Backups are stored in UpCloud S3-compatible object storage in the same region as your database (Frankfurt, de-fra1). Transfer between the database and object storage uses the private network — no public egress, no extra cost.
Restoring a backup
From the dashboard: go to your database → Backups tab → click Restore next to the backup you want to restore.
Warning: restoring replaces all current data in the database with the backup contents.
Exporting your data
You can export your database at any time using standard pg_dump:
pg_dump "postgresql://flokk_mydb:PASS@mydb.db.flokk.dev:5432/mydb?sslmode=require" \
--format=custom -f mydb.dump
This produces a standard PostgreSQL dump file that can be restored anywhere with pg_restore. No vendor lock-in.
Point-in-time recovery (Dedicated)
All tiers use continuous WAL archiving via CloudNativePG's Barman integration. You can restore to any point in time within your plan's retention window. Initiate a PITR restore from the dashboard or API.