One CVE shouldn’t take everything down
Doppelstack exists because production fleets are monocultures: one language, one TLS library, one kernel, copied everywhere.
The idea
Aviation and rail have used design diversity for decades: independently built systems that fail differently, so one fault can't take out both. Software infrastructure mostly hasn't, because running two implementations of the same app used to be too expensive.
Two things changed. AI-assisted engineering makes a second, independent implementation practical. And open vulnerability data (OSV, CISA KEV, EPSS, VEX) is now good enough to decide, minute by minute, which stack is safer to serve from.
What we're building
- Least-Vulnerable Load Balancing: a risk engine that shifts weights on the load balancer you already run.
- Stack Duplication: a complete functionality mirror of your app on a stack that shares nothing an attacker can reuse.
Where we are
Pre-launch. No customers to brag about, no metrics to inflate. We're looking for design partners who run production traffic on GCP and care about zero-day exposure.