Off-site, restorable, tested

WordPress Backup Service: Off-Site Copies, One-Click Restore

Get WordPress backups that live somewhere other than your host and restore in one click. Copies run weekly to daily depending on plan, land on separate infrastructure, and are test-restored quarterly — because an untested backup is a hope, not a plan.

Worldwide service, remote. No long-term contracts.

Get a free site audit See what it costs

30-day money-back guarantee · No setup fee · Cancel anytime

Get a free written site audit

Send the address and we return a written report inside one working day: patch backlog, exposure, load timings, restore status.

Written report within one working day · No obligation · We never sell your details

  • Stored off-site, on separate infrastructure from your host
  • Files and database together, so a restore is actually complete
  • One-click restore you can run yourself, or we do it for you
  • Test-restored every quarter, and you get the result in writing
off-site copy schedule and restore point list
The path this interrupts: the job is scheduled then it starts failing then six weeks pass then a restore is needed.

What this covers

  • Weekly copies on Starter, daily on Professional, daily to several locations on Business
  • Files and database captured together as one restorable point
  • Off-site storage, separate from your hosting account
  • Retention of 30, 60 or 90 days by plan, and your own download any time
  • One-click restore, self-service or done for you
  • Quarterly test restores with the result reported
  • Pre-update snapshots before every maintenance cycle
  • Download your own copy any time
1,000+ WordPress sites built
500+ hacked sites recovered
150+ malware removals
100+ sites under management
50+ popular plugins mastered
10+ years on one platform

The backup nobody tested

Most sites we take on have backups. A smaller number have backups that work. The difference only shows up on the day it matters, which is the worst possible time to find out.

Three failures we see repeatedly:

  • Database and files taken separately, hours apart, so a restore produces a site whose content and media do not match.
  • Backups stored on the same hosting account as the site. A compromised login or a suspended account takes both.
  • A plugin that has been failing silently for months because the scheduled task stopped running and nobody was watching the log.

Restoring a hacked site restores the hack

A backup is a recovery tool for accidents, not for compromise. Most infections sit undetected for weeks before anything visible happens, so by the time the site is defaced or blacklisted, every retained copy already contains the backdoor. Rolling back returns you to a working site and a working attacker.

This is why retention length matters more than backup frequency once security is in the picture. Hourly copies of an infected site are hourly copies of the infection. Thirty days of history is what gives you a chance of reaching behind the intrusion, and knowing which copy is clean means knowing when the entry happened — which comes from scanning and file-change monitoring, not from the backup system.

The order that works: identify the entry point, clean the live site, close the hole, then take a fresh backup and treat every older copy as evidence rather than as a restore point. That sequence is malware removal and hack repair, and the reason daily scanning is not optional alongside backups. Backups answer “the update broke it” and “someone deleted the wrong thing”. They do not answer “someone else has been in here”, and buying one expecting the other is the most expensive assumption on this page. Which cadence and which retention you get is set by the plan – maintenance plans and pricing lists all three – and the backup itself is one part of ongoing WordPress maintenance rather than a product bought on its own.

How the work runs

  1. Backup runs on scheduleFiles and database in one consistent point, not a file copy and a database dump taken twenty minutes apart.
  2. Copy ships off-siteTo infrastructure unrelated to your host, so a host account failure or a compromised hosting login cannot take both.
  3. Integrity is checkedA backup that cannot be opened is not a backup. Each one is verified after it lands.
  4. Quarterly test restoreWe restore to a scratch environment and confirm the site comes up. You get the result whether it passes or fails.
  5. Restore on demandYou can trigger it yourself, or ask us. Business carries emergency restore within two hours.

Plans that include this

  • Starter$39/monthor $390 a year — two months freeBlogs, portfolios and brochure sites
    • UpdatesMonthly
    • BackupsWeekly, 30-day retention
    • Uptime5-minute checks
    • Malware removalNot included
    See what is includedKept current and backed up.
  • Business$149/monthor $1490 a year — two months freeStores, membership sites, anywhere downtime costs money
    • UpdatesWeekly, tested on staging first
    • BackupsDaily, 90-day, multi-location
    • Uptime1-minute + 2-hour restore
    • Malware removalIncluded
    See what is includedEverything, including unlimited hack recovery.

Related pages

Questions people ask before calling

How often should a WordPress site be backed up?

Daily for anything that changes daily, and weekly is enough for a site that does not. The gap between copies is the work you are prepared to redo, which is why a store belongs on the daily cadence rather than the weekly one.

Isn't my host's backup enough?

It is better than nothing, and it is on the same account as the thing it protects. A compromised hosting login or a billing dispute can take the site and the backups together.

How long do restores take?

A typical business site is back inside 15 minutes. Large stores take longer, mostly database import time.

Do you test the backups?

Quarterly, restored to a scratch environment, and you get the result. This is the step almost everyone skips and it is the only one that proves the rest worked.

Can I download my own backup?

Any time, including after you cancel. They are your files.