Features built for reliability
Backuno isn’t trying to be fancy. It’s trying to be the plugin that finishes the backup, keeps retention clean, and makes remote copies predictable.
Local backups
Store backups on your server with a dedicated folder and retention rules that prevent disk overload.
Remote storage (Premium)
Push backups to Google Drive, FTP, Amazon S3 (AWS endpoints), or Backblaze B2 for off-site safety.
Scheduling (Premium)
Schedule backups with WP-Cron or system cron. System cron is recommended for high reliability.
Export workflow
Generate an archive and an installer pack for site migration and deployment workflows.
Retention rules
Keep the exact number of backups you want. Premium supports separate retention logic for local vs remote.
Restore (Coming soon)
Restore UI is visible and clearly labeled. Restore execution will ship when it’s production-ready.
Designed for large sites
- Handles big file counts (100k–200k+).
- Works with large databases and content-heavy websites.
- More stable behavior on restrictive hosting.
- Clear progress + logs (when enabled) for debugging.
Remote providers (Premium)
- Google Drive — off-site backups.
- FTP — your own server or NAS.
- Amazon S3 — AWS-style endpoints.
- Backblaze B2 — affordable object storage.
What Backuno is not
Clarity builds trust. Here’s what Backuno does not claim today.
Restore (Coming soon)
Restore is Coming soon. The UI remains visible but does not imply availability before release.
No fragile loopback dependency
Backups should not depend on unreliable loopback requests on many shared hosts. The approach is reliability-first.