SOURCED · published-list estimate · runs in your browser
Kubernetes Cost Optimization Calculator
Model Kubernetes rightsizing, spot/preemptible, and autoscaler savings from requested-vs-used capacity. Published-list estimate only. The math runs in your browser — your numbers never leave this page.
rates verifiedPublished-list scenario. Not your bill, not a quote, not financial advice.verified —view sources ↓
▮ Assumptions
🔒Computed on your device. No accounts, no bill upload, nothing sent to a server or any vendor.
▮ Scenario result
Decision guidance
Kubernetes cost decisions this calculator can test
The Kubernetes model starts from node-pool cost and requested-versus-used CPU and memory. It treats the most-utilized resource as the binding constraint, keeps explicit headroom, and then tests spot capacity and autoscaler reductions on the remaining baseline.
Questions it answers
How much requested capacity is genuinely idle when CPU and memory are evaluated together?
How much headroom must remain for bursts before rightsizing requests and node pools?
Which workloads are safe for spot or preemptible nodes, and what on-demand capacity must remain?
When it returns zero or refuses a claim
Used CPU or memory cannot exceed requested capacity; inconsistent utilization inputs are rejected.
The model will not shrink below the more heavily utilized of CPU or memory, so the less-used resource cannot manufacture extra savings.
A high spot mix produces a reclamation warning because stateful and critical workloads still need dependable capacity.
Verify against your invoice
Export node-pool type, count, and running hours from the cluster or cloud billing report.
Measure requested and used CPU and memory over a representative peak-and-off-peak window, not a single quiet sample.
Confirm disruption budgets, workload retry behavior, and autoscaler limits before treating spot or scale-down scenarios as deployable.
The calculator remains a published-list scenario, not a quote or your actual bill. Use the source links and invoice lines below before acting.
Representative published-list prices, re-verified on a freshness schedule. When a rate goes stale or a resource is not in the verified table, the total is suppressed rather than guessed.