Backups
Backups you can actually restore.
Encrypted, deduplicated snapshots of volumes, databases and folders, sent to any S3-compatible bucket you own. Every snapshot is verified, and a restore is one click away.
How a backup moves: on your server, the database is dumped and encrypted with a key that stays on the server. Only the encrypted snapshot is uploaded to your own S3 bucket. The Fwoop control plane schedules and checks the run but never sees the data.
Retention
Keep what your policy says. Prune the rest.
Set how many daily, weekly and monthly snapshots to keep. Fwoop deletes the rest after every run, so your bucket never grows without a reason.
A year of nightly snapshots. A retention policy of 7 daily, 4 weekly and 12 monthly snapshots keeps 23 of them; the rest are pruned automatically.
- snapshots kept for a year of nightly runs
- 23
- snapshots kept for a year of nightly runs
- less storage, thanks to deduplication
- 9.2×
- less storage, thanks to deduplication
- decisions about what to delete
- 0
- decisions about what to delete
Restore
Restores are boring. That's the point.
Pick a snapshot and restore a whole volume, one database or a single file, to the same server or a new one. Weekly test restores tell you it works before you need it.
A backup plan for the main Postgres database sending encrypted snapshots to an S3 bucket, with five recent snapshots, their sizes and verification checks, one passed test restore, and a retention policy of 7 daily, 4 weekly and 12 monthly snapshots.
What you can back up
Database-aware, not just files.
- Postgres
- pg_dump, consistent while the database keeps serving
- MySQL and MariaDB
- single-transaction dumps
- Redis
- a fresh RDB snapshot
- Docker volumes
- paused briefly, or snapshotted live with a hook
- Folders
- any path on the server, with include and exclude rules
No lock-in
Plain restic, readable without us.
Snapshots are standard restic repositories. With your key, you can list and restore them with the restic CLI, even if you stop using Fwoop.
$ export RESTIC_REPOSITORY=s3:s3.example.com/acme-backups/postgres
$ export RESTIC_PASSWORD_FILE=./postgres-main.key
$ restic snapshots
ID Time Host Size
a91f3c2e 2026-10-26 02:30:04 nyc-db-01 2.41 GiB
$ restic restore a91f3c2e --target ./restore
Summary: Restored 1 files/dirs (2.41 GiB) in 0:38Questions about backups
Who holds the encryption key?
You do. The key is created when you set up the backup and you're asked to store a copy. Fwoop keeps it sealed in your workspace secrets so scheduled runs work.
Which storage can I use?
Anything with an S3-compatible API: AWS S3, Backblaze B2, Cloudflare R2, Wasabi, MinIO and others. Use a bucket in a different provider or region from your servers.
How do test restores work?
On the schedule you choose, the agent restores the latest snapshot into a throwaway container, checks it can be read and reports the result. Nothing touches your live data.
Which plans include backups?
Team and above. See pricing for the details.
Bring your first server online in five minutes.
Start free with three servers. No credit card, no sales call, and your workloads stay on machines you own.