Cloud cost

Egress

Run a SaaS for a year. The bill is the boss fight.

You play the infra lead choosing instances, scaling policies and where the bytes go. You watch autoscaling lag, spot interruptions, data transfer, and a monthly invoice.

· Not playable yet — see the changelog

What you'll come away knowing

That egress is the tax on everything, and it is charged per byte leaving.
That a NAT gateway bills for bytes processed, not connections — which is how a data pipeline runs up a five-figure line item.
That cross-AZ traffic is not free, in either direction.
That autoscaling lags demand by boot time plus cooldown, and launch day does not wait.
That spot is cheap right up until everyone else wants the same capacity.
That a retry loop is a denial-of-wallet attack you inflicted on yourself.

How the model works

This sim is still being built. The model, scenarios and visuals for cloud cost are on the plan but not yet playable.

The shared engine it will run on is finished: deterministic fixed-timestep model in a Web Worker, checkpoints and seek, replayable share links, and the trace strip every sim uses.

Questions

When will it be playable?

Sims ship one at a time, each with at least eight scenarios, a full test suite and a landing page, before the next one starts. Check the changelog.