Define scenarios
Each scenario picks a resource and one of: DOWNSIZE (newInstanceType), RESERVED_INSTANCE (1y/3y term), SCHEDULE_STOP (start/end window), DELETE, or STORAGE_LIFECYCLE (transition + delete after N days).
5 primitives · per-resource
An interactive scenario engine that re-runs your last 90 days of cloud usage against any hypothesis: a new Savings Plan, a 30% traffic spike, a region migration, or a switch from on-demand to Spot — all on real data.
By the numbers
DOWNSIZE · RESERVED_INSTANCE · SCHEDULE_STOP · DELETE · STORAGE_LIFECYCLE
0
scenario types
simulation is fully read-only
0
writes to your accounts
totalEstimatedAnnualSavings
0
multi-scenario aggregation
DRAFT · RUNNING · COMPLETED · FAILED
0
simulation states
How it works
Each scenario picks a resource and one of: DOWNSIZE (newInstanceType), RESERVED_INSTANCE (1y/3y term), SCHEDULE_STOP (start/end window), DELETE, or STORAGE_LIFECYCLE (transition + delete after N days).
5 primitives · per-resource
POST /simulations/{id}/run executes a strategy per type: DownsizeStrategy compares current vs new instance price; ReservedInstanceStrategy applies the term discount; ScheduleStopStrategy applies the off-hours fraction; DeleteStrategy zeroes the cost; StorageLifecycleStrategy combines transition + retention math.
deterministic · per-resource
Each run returns scenarioBreakdowns[] (with insights + warnings) plus a totalEstimatedAnnualSavings — share the URL with the team, decide, then act through the recommendation flow.
share · decide · act
What's inside
Drag a slider for commitment coverage, pick a target instance family, dial workload elasticity. The simulator replays 90 days of usage and produces a band, not a point estimate, so you sign with eyes open.
Combine 'move 40% of stateless to Spot' + 'sign 60% commit on m6i' + 'consolidate 3 regions to 2' and see the joint effect — including the second-order networking cost.
Save a simulation and send the URL to finance, security or your cloud rep — they see the same numbers without poking around your account.
Capabilities
Before vs after Lumicost
Without Lumicost
With Lumicost
Where teams use it
Stop signing the renewal at last year's coverage — re-baseline against the last 90 days, not the last quarter's spike.
Model a 4× burst with realistic auto-scaling latency and find the cheapest instance mix that doesn't blow your SLO.
See egress, latency and cost effects of collapsing two regions into one — before kicking off the migration sprint.
From the field
“Five primitives composed cleanly will save more money than ten that nobody understands. We resisted the urge to ship a Monte Carlo for a reason.”
Plays nice with your stack
FAQ
Within ±5% on customers with stable workloads, ±10% during seasonal events. Confidence bands are always shown.
Yes — JSON import. Useful for replaying a vendor proposal against your real footprint.
Connect read-only credentials. First insights in 24 hours. No credit card.
90 seconds · read-only credentials · no credit card