Storage and backups

In preview

Connect the storage you already pay for, or run an S3-compatible store on your own server. Backups are encrypted restic repositories, one per account and target.

Built and lab-tested

  • Connections to S3, Backblaze B2, Wasabi, Cloudflare R2, DigitalOcean Spaces, Azure Blob, Google Cloud Storage, SFTP, FTP(S) and WebDAV, tested on save and rechecked every 15 minutes.
  • A built-in S3-compatible store (SeaweedFS): buckets, scoped access keys, versioning, object lock, CORS, lifecycle rules, quotas and presigned URLs. Standard AWS SDKs work with it.
  • restic backups to a local folder, any connection or the built-in store. Databases are exported first, so a backup is never silently partial.
  • Schedules, retention policies, and immutable backups with S3 object lock.
  • Restore files beside the originals, in place or into another account; restore a database by replacing it (after a safety dump), as a new one or as a download; restore a whole account with a 24-hour rollback.
  • Weekly integrity checks and monthly test restores run on their own.

Coming soon

  • Google Drive, Dropbox and OneDrive connections, and mounts.
  • Mail and container volume backups, point-in-time recovery.
  • Server-level disaster recovery.

Dedicated screens for this area are being built on the RespireCloud design system. Today every action has a generated form in the panel, is one keystroke away in the command palette (Ctrl K), and is callable through the API.

Modules in this area