Built to fail safe, not fail open
A tool that moves production traffic has to be more careful than the threat it reacts to. Here is how we think about access, data and failure.
Access model
- Config-only access to your load balancer, scoped to backend weights. No proxy, no agent, nothing in your request path.
- Inventory arrives as signed SBOMs that you publish; we verify signatures before using them.
- Hard cuts can require human approval under a policy you set.
Failure behavior
- Fail static: stale, missing or unsigned feeds freeze changes rather than guess.
- Capacity guard: the engine never drains every stack, and won't drain one if the remaining stack can't carry the load.
- No flapping: hysteresis and dwell timers keep weights stable.
- We go dark, you keep serving: your load balancer keeps its last configuration.
Stage, honestly
Doppelstack is pre-launch. We don't hold compliance certifications yet and we don't publish uptime numbers for a service that isn't generally available. When that changes, this page will say so, with evidence.
What this website stores
Only what you type into our forms, plus coarse metadata (time, country, browser string, and a keyed hash of your IP address used for rate limiting). No cookies, no analytics, no third-party scripts. Details on the privacy page.
Reporting a vulnerability
Found something? Please tell us through the contact form with the topic Security report. We don't publish an email address; the form goes straight to the team. Machine-readable details live in security.txt.
- Give us a reasonable chance to fix the issue before you disclose it.
- Don't access other people's data, degrade the service, or run automated scanners at volume.
- We won't pursue good-faith research that follows these rules.
About our Server header
It lies, on purpose. Each response picks a name from a costume rack of common web servers and runtimes (nginx, Apache, Caddy, Kestrel, Jetty, gunicorn, uvicorn, Express, Go, hyper and friends), with no version numbers. It does not describe what serves this site. Fingerprinting software from response headers is exactly the kind of inventory we tell customers not to trust; we match vulnerabilities against signed SBOMs instead.
This site actually runs as a small Rust program compiled to WebAssembly on Fastly Compute. See humans.txt.