Math you can defend in a budget meeting.
Calculators, frameworks, and content for engineering leaders making infrastructure investment decisions — including the AI ones nobody handed them a playbook for.
Open the EC2 calculatorCalculators
Each calculator shows the math, surfaces its assumptions, and produces output you can paste straight into a budget memo. No hidden defaults. No false precision.
On-Demand, Reserved, and Spot pricing in one view. Compare 1-year and 3-year RI savings against current usage. Built for the conversation that happens after the AWS bill arrives.
Open calculator →Standard, provisioned concurrency, and ARM (Graviton) pricing modeled together. Free tier shown explicitly. Built for production Lambda workloads, not hello-world examples.
Open calculator →Compare in-house build cost against SaaS subscription over 1, 3, or 5 years with realistic maintenance growth and price escalation. Find the break-even year.
Open calculator →Translate any uptime percentage into actual downtime minutes per month and year. Optional revenue impact estimate. Compare 99% to 99.999% with the math shown.
Open calculator →How we work the problem
InfraMath borrows from capital planning discipline used in regulated and enterprise environments. State assumptions. Source claims. Surface ranges, not point answers. Date-stamp pricing references. Name what we don’t know.
Every calculator shows its rates, multipliers, and discount assumptions. Every cited number traces back to a source.
Cloud costs vary by region, tenancy, and contract. We surface the spread so you see the trade-offs, not a false-precision single number.
Every calculator displays when its pricing was last reviewed. Stale pricing is a trust failure, not a footnote.
Frameworks structured so a reader could reproduce the answer later. The standard you’d want if your spend got reviewed.
Browse by topic
Five content pillars. Calculators, frameworks, and reference content organized around the decisions engineering leaders actually make.
AWS, Azure, GCP cost calculators, vendor comparisons, FinOps frameworks.
SLA, uptime, error budgets, multi-region architecture economics.
Build vs buy, vendor evaluation, tooling ROI, platform engineering.
Multi-year forecasting, AI infrastructure cases, scenario modeling.
Engineering compensation, FinOps career paths, role economics.
Found something to push back on?
The work gets sharper when readers disagree well. Email hello@inframath.dev with corrections, sharper benchmarks, or anything we got wrong.
About InfraMath