A second WordPress, waiting in the wings.
AlwaysUp sits in front of your domain, watches your site the way visitors see it, and keeps a working copy ready. When your site goes down, for any reason, the copy steps in within minutes and keeps selling. When your host is back, everything goes home, checked, and AI tells you what happened. You never touch a server.
Install. Connect. Point 1 DNS record to us.
About ten minutes, and your host stays exactly where it is. We find your host, your DNS provider and your email records ourselves, and prepare everything before we ask you for anything. Copy, paste, done.
- See it before you commit. Browse your own protected site on a preview link before you change any DNS.
- The AI setup assistant tells you exactly what to click at your DNS provider, and explains every record in one plain line.
- Virtually zero downtime while you switch, and you can switch back any time.
- If your provider can't do it, we can host your DNS for you, and you change it once.
- The check turns green live. We watch the change go out and confirm the moment you're protected.
We see what your visitors see.
Your site is checked from several places, including one completely independent of the rest. We look at the content, not just the status code, and AI page QA catches error pages disguised as “200 OK”. Your site's own plugin sends a heartbeat, so we can tell a dead server from a network problem.
- Slow is not down. A slow site is never switched over.
- A block or challenge page is reported to you, not treated as an outage.
- AI anomaly alerts explain slowdowns and traffic spikes before customers notice.
- Every decision is logged with its evidence.
From error page to selling again in about 4 minutes.
Saved pages in about a minute, your working site a few minutes later. Every step is recorded.
-
03:12Tuesday
Your host stops answering.
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”.
Watching -
03:13About a minute later
Confirmed. Your saved pages go up.
Confirmed 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 copy -
03:164 minutes in
A working copy of your WordPress takes over. You're selling again.
Not 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 site -
07:40Your host is back
We bring everything home. Carefully.
Your 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.
Returning -
07:58Before you wake up
Back on your server. AI report in your inbox.
Traffic 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.
Protected
Not a screenshot. A working WordPress.
The saved copy is the bridge for the first minutes. The backup site is the real thing: your WordPress, your theme, your plugins, your database, running on our infrastructure under your own domain, isolated from every other site.
- Logins, registrations, forms, bookings and comments work.
- Your store keeps selling: cart, checkout and payments work, and every order comes home afterwards.
- Your custom plugins run as they do on your host.
- Changes are saved continuously and brought back to your server.
- We promise it works and stays online. We don't promise it's as fast as your own server.
Back to your host, only when it's safe.
When your host answers again, we don't just flip back. Traffic returns only after your server holds everything the backup site did, and we've checked it.
- Your server's own state is archived first and kept for 30 days.
- Anything that changed on your server meanwhile is detected and reported to you.
- Every table and every file is compared before the switch back.
- If any check fails, the backup site keeps serving and nothing is lost.
- Your AI incident report explains what happened, the likely cause and what came home.
Six statuses. Each one means exactly what it says.
Your dashboard and your WordPress admin show the same status, and it only ever says what actually happened. If there's no saved copy to show, it says so.
Offsite backups that prove themselves.
The backup site is built from your backups, so they have to be right. They're encrypted on your site before they leave, stored away from your host, and light on your server.
- Encrypted before they leave. Each site has its own key. Backups travel straight to storage, never through our servers.
- Only changes after the first run, so even large sites stay light.
- Gentle on your server. Backups slow down and pause when your site is busy.
- Honest about consistency. Your dashboard shows your real recovery point and how your database was captured.
- Restores you can undo, checked automatically and rolled back if anything fails.
- Restore anywhere, including a brand-new server after a hack.
Who we can't protect yet.
Any WordPress site, on any host, in a few clicks covers almost everyone. Not quite everyone, and we'd rather tell you now. The free readiness check tells you before you pay anything.
- Nobody can get into the domain's DNS settings (for example, a former developer holds the login).
- DNSSEC is switched on and can't be changed.
- A company's IT team won't allow the DNS change.
- The host's firewall blocks our traffic. We expect this to be rare.