Backups you never have to think about
An immutable daily backup, written to separate infrastructure away from the server it protects. Restore one file, one database, or everything - over the original or beside it, so you can look before you overwrite.
14 days free. No credit card. No commitment.
Off the server
Separate infrastructure
No add-ons
Security and backups built in
99.99%
Uptime, last 12 mo
Daily
Backups kept up to 30 days
210+
Tasks Ellie handles
Where they live
Off the machine, and impossible to rewrite
Most of what makes a backup trustworthy is decided before anything goes wrong - where it is kept, and whether anything can reach it.
Not on the server they are protecting
Backups are written to separate backup infrastructure in a different location from the machine your site runs on. A backup that shares a disk with the thing it is backing up is a copy, not a backup.
Every backup is immutable
A backup is written once and cannot be edited afterwards. Nothing running inside your hosting account can alter one, overwrite one, or encrypt one - there is no writable path from your site to your backups at all. Ransomware that reaches your files does not reach these.
Your account, and only your account
One volume per account rather than one shared archive with folders in it. Nothing about restoring your site involves reading past anybody else's data.
Nothing to set up
There is no schedule to configure, no plugin to install, and no first backup to remember to take. It starts the day the account does.
What a backup is here, in one line
A complete, frozen copy of your account as it stood that day, held on dedicated backup infrastructure somewhere else. Not an archive sitting in a folder on your own server, and not something that can be rewritten once it exists.
- Daily, automatic
- Immutable
- Separate location
- Per account
- Copy to your own storage
- On every plan
Granular recovery
You almost never need the whole site back
The usual disaster is one file, one table, or one afternoon. Restoring everything to fix one of those causes a second problem, so you can restore at any of three sizes.
A file, or a folder
Open a backup, browse it like a file manager, tick what you want and restore just that. The usual case: one config file, one plugin directory, one image somebody deleted.
A database
Restore a database on its own without touching a single file - and choose whether the database users come back with it or stay as they are.
The whole account
Files and databases together, back to how they were on a given day. The button for the morning after a bad deploy.
Browse a backup
Look inside before you restore anything
A backup opens like a file manager. Walk the tree as it stood that day, find the thing you are missing, and take only that.
Pick a day
Backups are listed by date with their size. Choose the last one you know was good.
Browse it
Navigate the backup the way you would a file manager - folders, sizes, dates. Symlinks are shown but never followed.
Select what you need
Tick individual files, whole folders, or switch to a database or full-account restore instead.
Choose where it lands
Over the original, or into .recovery/ for a side-by-side look. This is the decision the rest of the page is about.
Watch it run
Restores are queued and logged. The log is kept, so "what did we put back, and when" has an answer later.
Symbolic links are shown but never followed, so browsing a backup cannot wander outside it.
Where it lands
Over the top, or beside it
This is the choice that decides whether a restore is a fix or a second incident, and it is one toggle.
Restore in place
Straight back to the original path
The files go back exactly where they came from, and anything currently at that path is overwritten. This is what you want when you know the live copy is wrong - a corrupted upload, a broken edit, a plugin that mangled a template.
Nothing else is touched
Only the paths you selected are written. The rest of the site keeps running on the files it already has, so a one-file restore is a one-file change rather than a rollback of everything.
Restore beside it
Into a .recovery folder instead
Flip one toggle and the same selection is written under .recovery/ rather than over the top. Your live files are left completely untouched.
For when you are not sure yet
Put yesterday beside today, diff them, and copy across only what you meant to. This is the option to reach for when the problem is "something changed and I do not know what" - because restoring in place would destroy the evidence.
If you are not sure what broke, restore beside it
How far back
Your window, and what happens outside it
Two numbers that sound like one, and the difference is worth a paragraph because it decides what an upgrade actually gets you.
Every plan gets a daily backup. How far back you can restore from is what changes with the plan - seven days at the entry level, up to 30 on the top one.
A backup that falls outside your window is not deleted. We still hold it, and it becomes reachable the moment you move up a plan. Upgrading gives you access to backups that already exist rather than starting a new clock.
There is also a way around the window entirely. Send a copy of every backup to storage you own, and that copy is yours for as long as you choose to keep it - on any plan, and after you stop being a customer.
Take one yourself before anything risky
You can trigger a backup at any point, and it sits alongside the daily ones. The right habit before a major plugin update, a theme change, or a deploy you are unsure about - and one you took yourself stays restorable by you regardless of the plan window.
Keep your own copy
Send every backup to a bucket you own
Ours are immutable and already off the server, and for most people that is the whole answer. If you would rather also hold a copy that sits with a provider of your choosing, connect your own object storage and every backup lands there too.
Any S3-compatible storage
Amazon S3, Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces, MinIO, or anything else that speaks the S3 API. Point it at a bucket you already have, give it a key scoped to that bucket, and pick a folder to keep things tidy.
Tested before you rely on it
Saving a destination runs a live check from the machine that will be doing the uploading - it lists the folder, writes a test object and removes it again. If a step fails you are told which one, rather than finding out weeks later that nothing was arriving.
Then it runs on its own
Every backup that completes here is packaged and copied across: one archive per backup, holding the same files and databases. Nothing to schedule, no second tool to keep running, and each copy records where it landed and how big it was.
The copy is genuinely yours
It arrives in your account, on your billing, outside our retention window entirely. Keep every copy or only the newest few - your choice - and if you ever leave Hostney, what is already in your bucket stays there.
Bring your own bucket
Anything that speaks the S3 API works. These are the ones the panel already knows the shape of, so the endpoint and region are filled in for you rather than looked up.
- Amazon S3
- Cloudflare R2
- Backblaze B2
- Wasabi
- DigitalOcean Spaces
- MinIO
- Any S3-compatible storage
What the copy is, and what it is not
Moving in?
Migration has its own pages now
Bringing a site across from another host is a different job from protecting one that already lives here, and it is covered properly elsewhere.
The WordPress plugin
One plugin on your current site, no SSH, and it stays online while we pull it across.
Over SSH
Shell access to the old server means we find the installation ourselves and move it with rsync.
Or we do it
Included on paid plans. Our team runs it, checks the result, and walks the DNS switch with you.
Pricing
Simple, transparent pricing
Every plan includes managed WordPress, SSH access, daily backups, and enterprise-grade security. Start with a 14-day free trial.
Black Friday80% off your first year with code BLACKFRIDAY80Ends Cyber Monday, November 30
Startup
Great for growing businesses
$7.92
$19.00 for your first year, then $94.99/yr
- 1 website
- 10 GB storage
- ~10,000 visits/month
- 5 MySQL databases
- 250,000 inodes
- 5 FTP users
What's included:
SSL & Domain
- Free SSL certificate
- Free starter domain
- 2 mailboxes
- 3 GB per mailbox
- Webmail, IMAP and SMTP
Advanced
For professional websites
$15.00
$36.00 for your first year, then $179.99/yr
- 5 websites
- 20 GB storage
- ~110,000 visits/month
- 10 MySQL databases
- 500,000 inodes
- 10 FTP users
Everything in Startup, plus:
- 5 mailboxes
- 5 GB per mailbox
Backups
- 14 days of backup history
Performance
- Memcached object cache
- Redis object cache
Pro
Maximum performance and features
$22.92
$55.00 for your first year, then $274.99/yr
- 10 websites
- 40 GB storage
- ~200,000 visits/month
- 20 MySQL databases
- 750,000 inodes
- 20 FTP users
Everything in Advanced, plus:
- 10 mailboxes
- 10 GB per mailbox
Deployment
- 2 SSR applications
Backups
- 30 days of backup history
Monitoring
- 1 minute between checks
For new customers on annual plans. Enter the code at checkout, or when you upgrade a free trial before the sale ends. The 80% comes off your first year; renewals are at the plan's regular price. Ends 11:59 p.m. Eastern on Monday, November 30.
On every plan
The layer you are glad of later
Immutable daily backups, kept off the server and out of reach, with a restore you can point at a single file - and a copy in your own storage if you want to hold one yourself. Included in every plan, running from the first day.
Questions