Built for the day one of them won't open.
Two real backends — AWS and Scaleway — behind three independent domains. A fourth, on a third cloud, is on the way.
Normal traffic — Fastly auto-failover between AWS and Scaleway.
EU residency, no Fastly. Direct to Scaleway end-to-end.
US-direct, no Fastly. Straight line to AWS Lambda.
Hard-disconnect path. A third cloud, fully independent of AWS and Scaleway.
One product. Three doors today. A fourth on the way for the day they're all needed at once. Status dots above are polled live from your browser — open DevTools and you'll see four requests going to four different hostnames.
Glassbreak runs the same product on two independent cloud-compute stacks — AWS Lambda in us-east-1 and Scaleway Functions in fr-par — each with its own database (Neon for the AWS path, Scaleway Managed Postgres for the Scaleway path). Nothing is shared between the two verticals except the user.
Those two backends are exposed through three different domains, because the domain you visit determines the path you take. Same product, different infrastructure underneath.
glassbreak.ioThe front door. Fastly's edge picks between AWS and Scaleway in real time using health checks. You don't notice failover — that's the point.
glassbreak.cloudA side door bypassing the front. Direct line to Scaleway in the EU, no Fastly in the path. Same data, simpler compliance story for EU-residency-conscious buyers.
glass-break.comThe other side door. Direct line to AWS Lambda in the US, no Fastly in the path. Keeps the AWS-end-to-end story whole when the front door is down.
glassbreak.io your request lands at Fastly, which health-checks both AWS Lambda and Scaleway Functions and routes you to whichever is healthy. On glassbreak.cloud and glass-break.com you connect directly — no CDN in between..io fails over to Scaleway via Fastly; .cloud is unaffected..io stays on AWS via Fastly; .com is unaffected..cloud and .com both bypass Fastly entirely.A future glassbreak.dev will be a fully independent third path on a third cloud — Fly.io or GCP, with its own DNS, its own database, and zero shared infrastructure with either AWS or Scaleway. It exists for the day when both production clouds are simultaneously degraded. We're not committing to a date, but the architecture is locked.
Want to see this live? The dots on the cards above are real — each card polls its own domain's /api/public/status endpoint directly from your browser every 30 seconds. Open DevTools and watch the network panel: you'll see requests going to four different hostnames. We don't aggregate the result on a single backend — that would defeat the whole point.
Get product updates and security insights. No spam, unsubscribe anytime.
We respect your privacy. See our privacy policy.