Local plugin backup
Stay on the WordPress server. Useful when you are not ready for Nought.io.
- Install the Backup product
- Choose what to include
- Run or schedule a backup
- Store the copy somewhere that is not the same disk
A way back.
Away from your server.
Two layers: a conventional WordPress backup product for people who want a plugin, and a remote Nought backup plane that moves the heavy work off the site.
Why Backup
Your server shouldn't have to be healthy enough to back itself up.
Backup is being built as two related products. The local layer is a WordPress/PHP backup experience for operators who want a conventional plugin without buying remote infrastructure. The remote layer, when connected through Runtime and Nought.io, uses Nought's external Rust backup data plane for capture, chunked transfer, off-site storage, manifests and restore. The long-term point is simple: a site that is already struggling should not also be responsible for saving itself.
A better starting point
Use the local plugin when you want a conventional on-site backup product. Connect Nought.io when you want the WordPress worker to stream work to Nought's Rust backup infrastructure instead of building giant archives in wp-content.
- PHP timeouts, disk full errors, and shared-host CPU limits kill backups at the worst moment.
- Full archives on the same server are not an off-site copy.
- Transactional sites change faster than nightly plugin cron.
- Restores are untested until the day you need them.
In practice
From task
to done.
How the product fits into the work you already do.
Remote Nought backup
The intended architecture for anything you actually care about.
- Runtime enrols the site
- Nought.io schedules or triggers a job
- The WordPress worker streams capture to the Rust backup plane
- Chunks land in off-site object storage with a sealed manifest
What’s inside.
The capabilities behind the product.
Local / plugin backup layer
A WordPress backup experience for operators who want a conventional product without purchasing remote infrastructure. Treat this layer as beta.
Off-site architecture
The remote plane is designed around capture sessions, chunked uploads, object storage, manifests and restore points — not a zip left in wp-content/uploads.
On the roadmap
Up next.
Planned work, separate from what is available today.
Incremental and resumable transfers
Chunked, resumable capture so a dropped connection does not throw away the whole job.
Verified restore points
Integrity verification as a separate job from capture. Full rehearsal restores are still being built.
Scheduled and hourly backups
Nightly for standard sites; hourly customer-data backups are intended for transactional / critical sites. Frequency recommendations will follow site class in Nought.io.
Remote restore
Restore from Nought.io rather than only from inside a working wp-admin.
Nought Local as a pull source
Use a Nought backup as the source when pulling a site into Nought Local.
A lighter WordPress
The heavy jobs
leave your website.
Your site serves your visitors. Nought.io handles operational work away from the server you are trying to protect.
Fits your workflow.
Runtime
The intended WordPress worker for remote jobs.
Nought.io
Scheduling, restore points, estate visibility.
Nought Local
Planned pull source from a Nought backup.
Guard
Separate security plane. Backup integrity is not a malware scan.
Technical details
WordPress worker
A lightweight Runtime / PHP worker reads files and database streams. It should not be the place that packs, encrypts and retains everything.
Off-site backup service
Backup handles capture sessions, chunked transfer, encryption, manifests, retention, export and restore. It is not the Guard scanner.
Control plane
Nought.io owns scheduling, policy, restore UX and entitlement. The backup plane stores data; Command decides when work runs.
System requirements
- WordPress site with Runtime for remote jobs
- Enough PHP execution time for the local plugin layer
- Nought.io account for remote backup
Privacy and security
Remote backups leave the WordPress server. Treat backup contents as production data: access control, encryption in transit, and retention policy matter.
Your toolkit, your choice
One product.
Or the connected Suite.
Choose an individual product licence or ask about Nought Suite. Contact us for pricing and availability.
Individual
Backup
Discuss this product and the right licence for your sites.
Ask about Backup ↗The toolkit
Nought Suite
Connected WordPress tools, with individual and agency options.
Explore the Suite ↗Remote operations
Nought.io
Some Nought.io plans include Suite products. What’s included depends on your plan.
Explore Nought.io ↗Questions
Is the remote Rust backup generally available?
The data plane exists and is used in Nought's own operations work. Treat public product access as beta. Do not assume hourly backups, rehearsal restores, or remote restore are live for every site.
Do I have to use Nought.io?
No. The local plugin layer is for people who want a conventional product. Remote architecture, off-site object storage and Nought.io scheduling are the stronger path.
Will this overwrite WooCommerce orders on restore?
A restore replaces what you tell it to replace. Selective, WordPress-aware sync is Sync — not something to assume from a full backup restore.
Also in the toolkit
Nought.io Remote WordPress operations: monitoring, backups, Guard, Optimise, updates, health, Runtime connectivity and agency estate management. ↗ Guard Nought's security layer. Remote checks, site health and integrity signals processed off-site in Rust, with visibility in Nought.io. ↗ Local A WordPress-only desktop app, macOS-first, built with Tauri 2, React, TypeScript and Rust. Designed so local development is not married to a single host. ↗ Nought Suite The collection of WordPress products built by Nought. Buy one, or licence the lot. ↗