Automatic
At 00:00, 06:00, 12:00 and 18:00 UTC. The latest, one a day for the last three days and one weekly are kept, at most five at a time.
Automatic backups for databases and for the volumes of your apps, restores you start yourself, and files that carry a site or a config to another account.
Every 6 hours
on plans that keep backups
Daily or weekly
with the Automatic backups add-on
Plain files
secret values never included
On plans that keep database backups, every database is backed up for you four times a day.
At 00:00, 06:00, 12:00 and 18:00 UTC. The latest, one a day for the last three days and one weekly are kept, at most five at a time.
Take a backup by hand at any time, and save up to three so they stay until you remove them.
Restore over the database, or clone a backup into a new database to compare first.
Deleting a database takes a final backup, and it can be restored as a new database for three days.
With the Automatic backups add-on, everything that keeps data on a volume can be backed up too.
PHP apps, WordPress sites, container apps, database servers, Redis and RabbitMQ, object storage, registries and log collectors.
A backup covers every volume of the app, so one restore brings the whole app back.
Daily or weekly, compressed by default. The five newest automatic backups are kept, plus one you save yourself.
Take a backup whenever you like, for example before an upgrade. A restore replaces every volume with the backup’s contents.
A site’s files come from its branch or archive, so the source already is the backup.
Export a site or a config as a small JSON file. Keep it in your repository, review it in a diff and import it into another account.
Its source, branch or folder and its serving options.
Variables, flags and the names of the log destinations it uses.
Export a config’s values as .env, JSON or shell lines for a runtime that cannot use the client. Secret values are masked unless you may reveal them.
webappmk stack save writes chosen sites, apps, databases and configs to webappmk.stack.json. stack deploy creates what is missing and updates what changed.
Roll a WordPress site back after a plugin update went wrong.
A database backup before every migration.
Set up a client from a file instead of by hand.
Each resource keeps its backups on its own Backups tab, and the command line has the same actions.
| Resource | How | Needs |
|---|---|---|
| Managed databases | Every 6 hours, plus manual and saved backups | A plan that keeps database backups |
| PHP apps and WordPress | Every volume, daily, weekly or now | The Automatic backups add-on |
| Container apps | Every volume of the app | The Automatic backups add-on |
| Database servers, Redis, RabbitMQ | Their data volume | The Automatic backups add-on |
| Object storage, registries, log collectors | Their data volume | The Automatic backups add-on |
| Static sites | The branch or archive is the source; export as .qk-app | Nothing |
| Configs | Export as .qk-def, .env or JSON | Nothing |
A database and login on a shared server that we run. PostgreSQL, MySQL or MariaDB.
A WordPress site of its own with its own MySQL or MariaDB database, installed fresh or moved in from an archive, with SSH, SFTP and wp-cli.
Keep variables, secrets and feature flags out of your code. Your app fetches them when it starts, wherever it runs, and changes reach it without a redeploy.