Your Fargate bill, broken into the line item nobody on your team can quote.
Drop in your fleet shape. The math uses published AWS rates (us-east-1, Linux/x86, on-demand) — same numbers your bill is built from — and shows the 24/7 baseline against a Mon–Fri 9-to-7 schedule.
A week has 168 hours.
Your team works 40 of them.
You're paying for the other 128 hours. See exactly how much ↓
Rates verified May 2026 from the AWS Fargate pricing page. Savings shown are for scheduling only — right-sizing and Fargate Spot add on top. Fixed overhead (ALB ~$22/mo, NAT ~$32, CloudWatch ~$36 ≈ ~$90/mo per environment) stays even when tasks stop. See our cost optimization guide for the full breakdown.
How much are you paying for environments nobody's using right now?
Adjust the sliders to match your fleet. Numbers update live using published AWS Fargate rates (us-east-1, Linux/x86).
How often do your dev/staging environments actually need to run?
Fortem starts at $790/month. Fortem starts at $790/month — it pays for itself in month one.
Show the math
All rates from AWS Fargate pricing page (us-east-1, Linux/x86, on-demand):
Baseline monthly cost (24/7, on-demand):
12 envs × 8 services × (0.5 vCPU × $0.04048 + 1 GB × $0.004445) × 730 hrs
= $1,730 / month
Schedule multiplier:
50 hrs ÷ 168 hrs/week = 29.8%
Optimized monthly cost:
$1,730 × 29.8% = $515/mo
Monthly savings:
$1,730 − $515 = $1,215/mo
Months to recoup Fortem plan ($790/month):
⌈$790 ÷ 1,215⌉ = 1 month
Compute-only — fixed overhead (ALB, NAT, CloudWatch ≈ ~$90/env) stays even when tasks stop. Full breakdown → That's why we say 60–70%, not 90%.