A ready-to-go backup web application firewall (WAF) and content delivery network (CDN) for your website, on separate infrastructure. Set up ahead of time, and switched on by you if the unexpected happens.
How it works
Off until you need it.
Standby, not standing
Your hostnames are ready ahead of time: TLS certificates, WAF rules and cache. Until you switch them on they refuse all traffic, so the backup is never a second way in to your site.
You flip the switch
Failover is always your call. Point a CNAME at us, or move your DNS records to our IP addresses, and visitors follow as DNS updates.
Anycast front door
Visitors reach us on anycast IP addresses: the same address announced from many locations at once. Each request lands at a nearby edge, and one location failing doesn’t take your site down.
Static egress addresses
We only reach your origin from a small, fixed set of IP addresses in a region close to it. Allowlist them alongside your existing lockdown, and we check every day that the path is ready.
Rules you already know
OWASP Core Rule Set, rate limits and simple rules of your own, with bypasses where a rule gets in the way. Your cache is kept warm ahead of time.
Separate from your primary
BackupWAF is built to share as little as possible with the provider you use today, so an unexpected issue on one side doesn’t affect the other.
Back to primary
When your primary is ready, point your DNS back and traffic returns as records update. Then switch BackupWAF off and your hostnames go back to standby, ready for next time.
Evidence for auditors
Logs go to your SIEM. Regular failover drills give you timestamped evidence that your website can ride out an unexpected WAF or CDN issue, for frameworks like APRA CPS 230.
Who it’s for
Organisations that can’t just wait it out.
Built for organisations that rely on a WAF or CDN and need to show they can keep their website up through an unexpected issue, however rare.