Summary#
Your applications are backed up every day, and the backups are kept in the region your environments run in, for 7 days on the Beta plan and 30 days on a paid plan. They are not copied to another region unless your plan includes Off-region backups. If you want a copy that survives the loss of that region, download your backups and keep them where you choose. Restoring from a download is yours to do.
Description#
What is backed up, and when. From 03:00 UTC each day, each environment of an application is backed up by the zone that runs it: a dump of that environment's database, recorded on the application's Backups page with the trigger Scheduled. An organization or application whose backup schedule is Weekly is backed up on Sundays; one whose schedule is Off is not backed up at all. A zone that cannot take the backup at 03:00 is asked again later the same day.
How long it is kept. As long as the plan keeps backups: 7 days on the Beta plan, 30 days on a paid plan. The application's Backups page says which. An application's own retention setting can make it shorter, never longer. Older backups are deleted, except that an application's newest three backups of each database are always kept, whatever their age — so an application whose backups stopped still has its last good ones. When an organization changes plan, the new retention applies to the backups it already has, within the hour. To keep a backup longer than the plan does, download it.
Backups on demand. On a paid plan you can take a backup whenever you want: Request backup on the Backups page, or
osyrin app backup. On the Beta plan you cannot. The nightly backup is what the plan includes, and the request is refused
with a message saying so. The nightly backup is still taken. The backups the platform takes for itself, before a platform
release changes the database or before an application is deleted, are not requests and still run on every plan.
Where it is kept. In the zone's own storage, in the same region as the environment. On the standard plans, including the Beta plan, no copy leaves that region: keeping one somewhere else is a cost the plan does not include. If the region were lost, backups kept only there would be lost with it.
Off-region backups is the plan feature that adds a nightly copy of the organization's backups to storage outside the region. It is not part of the standard plans. The organization's Settings page lists it under Platform features, with any decision the platform operators made about it.
Downloading. Download any backup whose status is Success:
- in the console, on the application's Backups page, with Download on the backup's row; or
- with
osyrin app backups download --backup <id> --app <slug> --out <file>, which checks the download against the SHA-256 the backup recorded.
The download is a Postgres dump in custom format, for pg_restore. It is the environment's whole database, so keep it
as safely as you keep the application's data.
Who may download: an owner or admin of the organization, or a member of the application who is not only a developer.
Restoring. To restore inside Osyrin, use the application's Backups page or osyrin app restore (see
Restoring a backup taken on an older version). To restore a download somewhere else, use a pg_restore at least as new
as the pg_dump that made it. A restore you run outside Osyrin is your own: the platform does not check or support it.
Examples#
osyrin app backups list --app billing-acme --json # find today's Scheduled backup, and its id
osyrin app backups download --backup 3f1c… --app billing-acme --out billing-2026-10-19.dump
pg_restore --list billing-2026-10-19.dump | head # look inside it before you need itSee also#
Restoring a backup taken on an older version — restoring a backup inside Osyrin, into a copy beside the environment.
What your plan allows, and how much of it is used — what your plan includes.
An organization's environments — the environments that are backed up.