Names the culprit. Offers the fix.
Acme Slider 4.1 broke your site after last night's update. Visitors are seeing your last good page meanwhile.
Apply one-click fixRoll back to 4.0Host outage, traffic flood, fatal error, bad update. Whatever takes your WordPress site down, AlwaysUp puts a fully working copy in its place within minutes, on your own domain, checkout included. Orders keep coming in. And AI tells you exactly what happened.
All checks passing from several locations.
You refresh. You refresh again. You open a ticket and wait. Meanwhile your ads keep running, your orders stop and your reputation takes the hit. And WordPress gives it plenty of ways to happen.
Monitors tell you you're down. Backups rebuild you tomorrow. Neither saves today's sales.
| Capability | Uptime monitorTells you | Backup pluginRebuilds later | AlwaysUpKeeps you open |
|---|---|---|---|
| Notices when your site is downIncluding blank pages that still say “OK” | ✓ | – | ✓ |
| Visitors keep reaching your site during the outageOn your own domain, within minutes | – | – | ✓ |
| Logins, forms and checkout keep workingA real WordPress, not a static mirror | – | – | ✓ |
| Takes orders and payments during the outageEvery order brought home afterwards | – | – | ✓ |
| AI explains what broke and how to fix itPlain English, with a likely root cause | – | – | ✓ |
| Offsite, encrypted backupsEncrypted before they leave your site | – | Often | ✓ |
| Who has to act at 3 a.m.? | You | You | Nobody |
No alarm, no ticket, no panic. Here's what happens while you sleep.
A host outage, a traffic flood, a fatal error, a database crash. Without protection, visitors start getting error pages. We see it from the outside, the way they do, including the sneaky blank page that still says “200 OK”.
WatchingConfirmed from several independent locations, so a blip or a slow page never triggers a switch. Visitors see a verified saved copy of your site on your own domain while your working copy starts.
Serving saved copyNot a screenshot. Your real site, running on our infrastructure, on your domain. Logins, forms, comments and your custom plugins all work, and your store keeps taking orders: cart, checkout, payment confirmed.
Running on backup siteYour server's own state is archived first. Then every order, sign-up and edit made on the backup site is copied back and verified, table by table and file by file. The backup site keeps serving the whole time.
ReturningTraffic returns to your host only after the check passes. Your AI incident report explains what happened, the likely cause, what you sold during the outage and what came home. You didn't have to do a thing.
ProtectedIt reads every check, every error and every incident, then tells you what matters in plain English. No dashboards to decode, no logs to dig through.
Traffic was about 4× normal from 14:05 to 15:10, almost all of it to /sale from one newsletter link. Pages took up to 3.8 s at the peak. The site never went down, so nothing switched over.
Suggestion: your host's plan tops out around this level. Next time, schedule the newsletter outside lunch hours or ask your host about a short-term upgrade.
One thing: Acme Slider 4.1 caused a fatal error on Thursday at 02:14. Visitors saw your last good page for 6 minutes until you applied the fix. Nothing else.
Acme Slider 4.1 broke your site after last night's update. Visitors are seeing your last good page meanwhile.
Apply one-click fixRoll back to 4.0What happened, the likely root cause and how sure we are, what visitors saw and what came home.
Error pages disguised as 200 OK never make it into your saved copy.
Every step and every DNS record explained in one plain line, for your provider's screens.
What would happen to your site today, and three specific things to fix.
Traffic spikes and slow pages spotted automatically, with the reason, before customers complain.
No migration. No server work. No tech skills. Install, connect, copy one record. AI tells you exactly where to paste it.
From your WordPress dashboard, like any other plugin. Nothing to configure.
We find your host, DNS provider and email settings ourselves, then show you your protected site on a preview link.
Your domain's DNS is managed at your registrar. Open DNS settings, click Add record, choose CNAME and paste this:
Most sites change one record, some two. If your DNS provider can't do it, we can host your DNS for you, and you make one change.
Outages are rare. Protection is every day. Here's what runs in the background while you run your business.
We see what your visitors see, from several places at once. AI page QA spots a blank page that says “OK”, and a slow afternoon doesn't set anything off.
Encrypted on your site before anything leaves it, stored away from your host. After the first run, only changes are sent.
Every restore is checked and rolls back automatically if anything fails. Change your mind within 72 hours and undo it.
We restore a sample of backups on separate machines every night, so “we have a backup” means “it restores”.
Restore a clean, verified point onto your server or a brand-new one, and undo it if you need to.
When an update crashes your site, visitors see your last good page while AI names the culprit and offers a one-click fix.
What happened, the likely cause, what visitors saw, what was sold and what came home. Written so you can forward it to your boss, your client or your host.
Tuesday, 03:12. Your host's database server stopped responding (likely cause, high confidence). Within about a minute visitors were seeing your saved pages, and from 03:16 your working site ran on our backup for 4 h 42 m. It took 7 orders worth $412 and 2 new accounts, all brought back to your server and verified at 07:58.
Promises are easy. These are rules the system is built on.
We check your mail records before any change. If we can't prove your email stays safe, setup stops and tells you why.
A slow site is still your site. We step in when it has stopped answering, confirmed from several places.
If a form or order can't be delivered, the visitor gets an honest “try again”, never a fake “thank you”.
Logged-in pages, carts and checkouts always come from a live WordPress, never from a saved copy.
Every incident ends with an AI report in plain English: what broke, what we did, and what came home.
Once the backup site has served visitors, traffic returns only after your server is brought up to date and verified.
Your site stays with the host you chose. We add a safety net, not a migration.
Switch back any time: change one DNS record back and you're exactly where you started.
“A monitor tells you you're down. A backup lets you rebuild later. Neither keeps a business selling at 3 a.m. That's the gap we built AlwaysUp for.
We'd rather show you exactly how it works, including what it can't do yet, than promise you something nobody can measure.”
[PLACEHOLDER: real customer quote]
One price per site. Everything you need to stay open and keep selling, nothing to manage.
For simple sites: portfolios, brochures, blogs and local businesses.
For sites that earn: stores, bookings, memberships and lead generation.
For large sites, busy stores and agencies' most important clients.
Early-access pricing, per site, billed monthly. Plans and limits are indicative and will be confirmed before launch.
We never switch off a working backup site automatically when an allowance ends.
Rescue from bad updates on your own server: visitors see your last good page instead of a fatal error, while AI names the plugin or theme that broke it and offers a one-click fix. Plus an AI readiness report, a local last-known-good copy and basic uptime alerts. No account needed.
We're writing a short, specific promise: if a defined outage happens and we don't keep your site reachable, that month is on us. The exact terms will be published here once they're final and reviewed. Until then, we won't use the word.
AlwaysUp checks your site from the outside, the way visitors see it. Whatever the cause (a host outage, a traffic flood, a fatal error, a database crash), we confirm the failure from several independent locations so a blip or a slow page never triggers a switch. About a minute in, visitors see a verified saved copy of your pages on your own domain. A few minutes later, a fully working copy of your WordPress site takes over: logins, forms and checkout all work. When your host is back, everything that changed is brought back to your server and checked before traffic returns, and an AI incident report tells you what happened.
It does the reading and explaining for you. After every incident it writes a plain-English report with the likely root cause. When an update crashes your site it names the plugin or theme responsible and offers a one-click fix. It checks pages before they go into your saved copy, so an error page dressed up as "OK" never gets served. It walks you through setup, writes your readiness report, explains slowdowns and traffic spikes, and answers questions about your sites in plain language. Every AI answer is labelled as AI-generated.
Yes. On the backup site your WooCommerce store keeps working: customers browse, add to cart, check out and pay. Every order taken during the outage is brought back to your server afterwards and verified, and your AI incident report tells you what you sold while your host was down.
They're saved continuously and brought back to your server. Before traffic returns, we archive your server's own state, copy everything over, and verify it table by table and file by file. If that check can't pass safely, the backup site simply keeps serving until it can.
No. Your host stays exactly where it is. Install the plugin, connect, and point one DNS record to us. AI tells you exactly what to click at your DNS provider. No API keys, no storage accounts, no server configuration and no tickets to your host.
Set it up once in about 10 minutes, keep your host, and stop worrying about the night it fails. Join early access and we'll walk you through it.