PocketHost makes every effort to protect your data, but you should always keep your own backups. This page covers how to do that well on PocketHost.
The rest of this page explains why, and how to set each one up.
Your bucket is the one copy of your data that you fully control. It sits outside PocketHost, and you decide how long it keeps things.
Versioning is what protects you from mistakes. When a record is deleted or a file is replaced, PocketBase deletes the old file from storage. With versioning on, your bucket keeps the earlier version, so you can bring it back. The same goes for backups: if a backup is deleted by accident, its earlier version is still in the bucket.
PocketBase backups don’t include files stored in S3. A backup holds your database. Your uploads are protected by your bucket’s version history instead. If you restore an older backup, it can bring back records whose files were deleted since. Versioning means those files are still there to recover.
Set a lifecycle rule that removes old versions after a period you’re comfortable with, such as 30 or 90 days, so storage doesn’t grow forever.
Most S3-compatible providers support versioning and lifecycle rules. Check that yours does before you choose it. To connect a bucket, see S3 Storage. Files in your own bucket also don’t count toward your disk storage.
PocketBase has a built-in scheduler. It runs cronAdd jobs and the backup schedule in Settings > Backups. That scheduler lives inside the PocketBase process, so it only runs while your instance is running.
On PocketHost, instances hibernate when they’re idle. While an instance sleeps, its built-in scheduler sleeps too. So on PocketHost the schedule lives in the platform instead. Webhooks call a route on your instance at the times you choose, and wake it up if it’s asleep. Anything you would do with cronAdd, you can do with a webhook.
Here’s why it works this way, and why everybody comes out ahead:
curl, test it locally, and see exactly what it returns. The same route works anywhere PocketBase runs. On your own server, any scheduler can call it.PocketHost adds a backup route to every instance: /api/ph/backup. Point a webhook at it, and PocketHost runs a backup on your schedule, waking your instance if needed. It uses your backup settings: your S3 bucket, and the Max @auto backups setting that removes old backups. It works on every PocketBase version PocketHost runs.
1. Set up backups in the PocketBase admin. Go to Settings > Backups.
0 3 * * *. This shows the Max @auto backups setting. The webhook is what runs backups on time.2. Add the webhook. In your instance dashboard, open Webhooks and add:
/api/ph/backup0 3 * * * (daily at 3:00 UTC), or whatever suits you3. Check the first run. After the schedule comes around, the dashboard shows the webhook’s last response, such as {"ok":true,"name":"@auto_pb_backup_ph_20261110030000.zip","removed":1}, and the new backup appears in Settings > Backups. If the response is Unauthorized, power your instance off and on once so it picks up its backup token.
Unauthorized.PocketBase’s backup and restore tools are in the admin under Settings > Backups. You can restore without powering off your instance.

This applies to backups kept on PocketHost’s disk. Backups in your own S3 bucket aren’t moved.
PocketHost keeps your most recent backup on disk. Once a day, older backups move to cold storage.
In the PocketBase Backups list, each moved backup is replaced by a text file with the same name plus .txt, for example pb_backup_20261101.zip.txt.
.txt file from the Backups list and open it. It contains a download link for the original zip..txt file deletes the backup. When the .txt file is gone from your Backups list, whether you deleted it or PocketBase removed it as an old scheduled backup, the copy in cold storage is deleted 14 days later..txt files toward Max @auto backups, and removes the oldest first, the same as zips..txt file itself does nothing. It isn’t a backup, so PocketBase leaves your data as it is.If the admin isn’t available or your instance won’t start, use the PocketHost CLI. Power off the instance, then run pockethost pull --data pb_data to download the database and uploads. To restore, run pockethost upload ./pb_data. SFTP works too until it is retired on February 6, 2027.