One product. Three doors.
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.
Fastly-routed primary. Scaleway → AWS Lambda failover on 5xx.
EU-pure direct path. No Fastly, no AWS.
US-direct path. CloudFront-fronted Lambda.
Hard-disconnect future path. No shared infra with AWS or Scaleway.
Hover or focus any cube to see the provider + region that layer terminates at.
One product. Three doors today, a fourth in flight. Each door is a full end-to-end stack — registrar, DNS, edge, compute, and database — so a failure at any one provider leaves the other doors operational.
Two backends, three doors
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.io
The 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.cloud
A 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.com
The 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.
How traffic flows
- You visit one of the three domains. Each has two independent DNS authorities serving the same records, so losing one DNS provider does not unresolve the name.
- On
glassbreak.ioyour request lands at Fastly, which health-checks both AWS Lambda and Scaleway Functions and routes you to whichever is healthy. Onglassbreak.cloudandglass-break.comyou connect directly — no CDN in between. - Each compute origin uses its own database: Lambda talks to Neon, Scaleway Functions talks to Scaleway Managed Postgres. The two replicate to each other over HTTPS with HMAC-signed requests — no shared message queue, no shared region.
What survives
- AWS outage —
.iofails over to Scaleway via Fastly;.cloudis unaffected. - Scaleway outage —
.iostays on AWS via Fastly;.comis unaffected. - Fastly outage —
.cloudand.comboth bypass Fastly entirely. - DNS provider outage — every domain has a second authority serving identical records.
A fourth door, for the rare day
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.