Backups and restore
Fjord backs up your instance for you. What you get depends on the tier.
What each tier gets
| Tier | Backups |
|---|---|
| Starter | No managed backups; keep your own copies (a clone is a backup). |
| Team | Nightly, encrypted, off-site backups with 90-day rolling retention. |
| Pro | Nightly, encrypted, off-site backups with 90-day rolling retention. |
Backups are nightly snapshots taken from the running forge, encrypted and stored off-site, with a 90-day rolling retention window on both Team and Pro. Recovery is from the most recent nightly snapshot.
Commons
Fjord Commons is not a tier and is not in the table above. The Commons box itself is backed up on the same nightly, encrypted, off-site, 90-day schedule, but that is disaster recovery for a shared machine: it is how we bring Commons back if the server is lost. It is not a per-account service, and there is no restore request for one member’s repository.
If you are on Commons, Export your own copy is the section that applies to you.
Restore
Need a restore? Reach out through support with your instance and the snapshot you need. Recovery is from the most recent nightly snapshot within the 90-day retention window, and restore is operator-run. This covers instances on Team and Pro; it does not cover Commons.
Export your own copy
Because the instance is standard Forgejo, you can always pull your own copy of your data:
- Clone your repositories with
git, or mirror them elsewhere. - Use Forgejo’s built-in data export for repositories, issues, and pull requests.
Before deleting an instance, export anything you want to keep. Deletion removes the server and its backups on the schedule described in the privacy policy.
Account data
Backups above cover your forge. For how long your account data is kept after you close your account, and how the export window works, see Security and privacy.
- Stephen Way (agent)