When your site goes down, your returning visitors don't have to.
One script installs a service worker that detects when your origin becomes unreachable — DNS failures, expired certs, dead servers, TLS errors — and redirects returning visitors to a backup URL you configure. No DNS changes. No proxy. No CDN.
The problem
Uptime monitoring tells you the site is down. It does nothing for the visitor already trying to reach it.
Businesses lose returning customers the moment a site becomes unreachable — a lapsed domain, a failed migration, a hosting outage. By the time you're paged, the visitor has already bounced.
Standby is a client-side emergency fallback layer: install once, configure a backup, and stop losing the visitors you already earned.
767,950,813
Domains tracked as expired
582,322,300
Of those already deleted
How it works
Five steps, entirely in the browser.
What you get
Built for engineers who need this to just work.
Under 5KB, no build step, no framework dependency.
Nothing to repoint. Nothing to propagate.
Runs entirely client-side, in the visitor's browser.
Point failover at a new domain, a status page, or a mirror.
By design — it only helps people who already have the worker installed.
Server outages, DNS problems, expired domains, TLS/connection failures.
Example
Migrations, domain lapses, hosting failures — same fix.
Hosting fails, or the domain quietly expires.
A returning visitor's service worker catches the failed request and redirects them there automatically.
Install
One script tag.
data-backup="https://newshop.com"></script>
Registers a service worker scoped to your origin. Under 5KB, no build step, no dependency on your stack.
Pricing
One price. No tiers.
- Unlimited failover redirects
- One configured backup URL per site
- Install script + dashboard access
- Update your backup URL anytime
- Email support
Security & privacy
Nothing routes through us.
Traffic goes straight from visitor to your origin, or your origin to your backup. We're never in the request path.
The service worker only intercepts navigation requests to the origin it was installed on.
No analytics payload, no cookies set by Standby, no data collected beyond standard service worker scope.
The install script and worker source are plain, readable JavaScript — inspect it in devtools any time.
FAQ
Common questions.
No — it complements it. Monitoring tells you something is wrong; Standby keeps the visitor moving while you fix it.