Driven by a direct user question: why do N+1 and N+N+DR double the hardware while capacity, tokens per second and concurrency stay the same?
Because those figures are what you can guarantee even during the failure you chose to survive. Redundant hardware idles (spares, mirrors, DR standby) or serves day-to-day as burst headroom (Active/Active) that you must not plan sustained load on. The tool now shows this instead of implying it:
- Resilience economics strip under the topology: guaranteed at peak, normal-day capacity, idle hardware, and cost versus bare N. For Active/Active it shows the real day-to-day burst (about 2x) next to the guaranteed figure; for half-size DR it notes capacity halves during a site loss.
- Selector grouped by outcome: no redundancy / survives a server failure / survives a site loss / survives both, with plain-language labels.
- Two practical patterns added: N+2 (two idle spares, the usual step up for larger fleets) and half-size DR (1.5N, degraded failover), drawn in the topology and mirrored in the XLS export.