Stress-test architecture choices before committing infrastructure
A lightweight estimator for founders and engineering leads planning an AWS workload. Pick your primary compute profile, set traffic and data volume, and get a monthly spend projection with a breakdown of the line items that usually dominate the invoice.
Why use it
What you'll get out of five minutes with this tool
Compare ECS, Lambda, and RDS cost profiles at your scale
Forecast burn rate impact of projected traffic growth
Back-of-envelope check against vendor or IaC proposals
Inputs
Describe the workload
Storage + inter-service and egress data transfer.
Primary service
Your estimate
Monthly AWS spend
Midpoint estimate
$970
Range: $825 – $1,310 per month
Compute (ECS Fargate)$940
Storage & data transfer$30
Excludes NAT Gateway, WAF, support plans, and data-transfer out to the public internet — the top hidden-cost drivers in our 2026 startup cost report.
Get a precise architecture estimateQuestions
Frequently asked
Why is this a range and not a single number?
Actual AWS invoices depend on traffic shape, data access patterns, reserved-instance coverage, and region — all of which drift over time. A range is honest; a single number is fiction.
What's excluded?
NAT Gateway, WAF, support plans, and data-transfer egress are excluded. These are the top hidden-cost drivers in our 2026 AWS startup cost report.
Should I pick ECS, Lambda, or RDS?
ECS suits predictable, always-on workloads. Lambda shines for bursty or event-driven patterns. RDS is for data-intensive workloads — the estimator prices it as the primary compute so you can compare apples to apples.