Home / FAQ
FAQ

Questions engineers ask first

Short answers. If yours isn't here, ask through the contact form.

Least-vulnerable load balancing

Do you sit in front of my traffic?

No. The risk engine runs out of band and only changes backend weights through your load balancer's config API. Requests never touch our infrastructure.

What happens if Doppelstack goes down?

Nothing changes. Your load balancer keeps serving with its last configuration. Stale or unsigned feeds freeze changes rather than guess.

Which load balancers do you support?

GCP Global Load Balancer first. AWS, Azure and Cloudflare are planned. Tell us what you run on the waitlist form; it shapes the order.

Can it drain all my stacks?

No. A capacity guard prevents draining every stack, and won't drain one if the remaining stack can't carry the load. Hard cuts can require human approval.

How do you know what I'm running?

From a signed SBOM tied to each deployed image, cross-checked by an independent scan. Not the Server header (ours is fake; here's why).

What is stay-up mode?

An optional read-only static copy of your site that the load balancer can serve if every stack is hit at once.

Stack duplication

Is this a code conversion service?

No. Stack Duplication is a complete functionality mirror service. We don't translate your source line by line into another language; that would carry your architecture, your bugs and often your dependencies across. We rebuild what your application does (routes, contracts, data flows, edge cases and errors) as an independent, idiomatic implementation on a different stack, and prove the two behave the same with a shared conformance suite.

Which language will the twin be in?

Your choice, or we recommend one that shares as little as possible with your current stack. Typical pairings: Node to Java, Java to Go, Go to Rust, Python to Go, Ruby to Elixir. We also vary framework, TLS library, OS, CPU architecture, build pipeline and signing keys.

How do you keep the two versions in sync?

The conformance suite is the contract. It runs against your current app first, then gates every change to either stack. New behavior lands in the suite before it lands in code.

Do you use AI?

Yes, to speed up the rebuild. Engineers review every line, and the conformance suite decides whether it's done.

Who owns the code?

You do: code, tests, pipeline and docs. Use it with our load balancing or on its own.

Do I need to send you my source code to get a quote?

No. Describe the app on the quote form. Please don't paste code or secrets into it.

Company

Is this available today?

Not yet. We're pre-launch, working with a small group of design partners. Join the waitlist or request a quote.

How much does it cost?

We don't publish pricing yet. Duplication is quoted per project after scoping; load balancing pricing comes with general availability.

Why is there no email address on this site?

Everything goes through the forms so nothing gets lost in an inbox. You'll get a reply from a person.