Reduce 60–70% dev/staging costs
not touching infra code
Safely shuts down dev and staging on nights and weekends, restarts them before your team logs in. Developers restart staging themselves — no platform tickets. Your infra code stays untouched.
| ENV ↑ | STATUS | SVCS | SCHED | COST ↑ | ACTIONS |
|---|---|---|---|---|---|
use1-dev-dev1 us-east-1 | Running | Mon-Fri 9-19 Starts in 21h 42m | $99 | ||
use1-dev-qa1 us-east-1 | Running | Mon-Fri 8-20 Starts in 20h 42m | $103 | ||
use1-prod-main us-east-1 | Running | — | $1.2k | ||
use1-prod-stg1 us-east-1 | Running | Mon-Fri 8-22 Starts in 20h 42m | $890 | ||
usw2-dev-data1 us-west-2 | Running | Mon-Fri 8-18 Starts in 20h 42m | $445 | ||
usw2-dev-demo us-west-2 | Running | — | $142 | ||
usw2-dev-dev1 us-west-2 | Running | Mon-Fri 9-19 Starts in 21h 42m | $98 | ||
usw2-dev-ml1 us-west-2 | Running | Mon-Fri 9-18 Starts in 21h 42m | $890 |
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. Your first month pays for itself and then some.
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%.
Stop the 24/7 bleed.
Run environments only when your team works. Per-env timezones. Weekends off by default. Most teams cut dev/staging spend by 60–70% in the first month.
One screen, every environment.
Every ECS environment — status, cost, owner, last deploy. Services, databases, CI/CD branches. One screen. No more checking six different consoles.
| ENV | SERVICES | COST |
|---|---|---|
| use1-prod-main | 10 up1 down | $2.4k |
| use1-dev-qa1 | 7 up1 deploying | $890 |
| usw2-dev-ml1 | 4 up | $350 |
| euw2-dev-demo | — | — |
Friday 6pm — your developer restarts staging without you.
Developers restart, redeploy, and view logs for their environments. RBAC by environment — scoped to what they own. Platform engineers go home on time.
Root cause + suggested fix in ~8 seconds.
When a task fails, Fortem reads CloudWatch, checks IAM, and proposes the fix in ~8 seconds — you approve, it applies. Nothing mutates state without you.
Build it, hire for it, or let Fortem ship next week.
Flightcontrol is the right answer for 1–3 apps moving off Heroku. We mean it — point your friends there. Fortem starts mattering around the fifteenth environment, when their per-service line item crosses $5k/mo and your team starts forgetting which staging cluster is which.
Task fails. Fix proposal in 8 seconds. You approve.
When an ECS task fails to start, the diagnostic agent reads CloudWatch, walks the task definition, and checks the IAM role. Median time to a fix suggestion: 8 seconds. State only changes on your click.
Your task definition references an image in acme-prod ECR. The execution role ecsTaskExecutionRole is missing ecr:GetAuthorizationToken. Add it to the inline policy or attach the managed AmazonECSTaskExecutionRolePolicy.
Incident diagnostics in seconds
When an ECS task fails, Fortem reads CloudWatch logs, inspects the task definition, checks IAM, and proposes a fix — usually within 8 seconds. 6-minute response times become 30-second response times.
The cost watcher
Weekly scans surface specific optimization opportunities — not generic recommendations. "Your eu-staging-qa-02 environment hasn’t received a deploy in 41 days. Schedule it off-hours or archive it? Saves $284 / mo."
The environment doctor (chat)
Ask in plain English. "Why is staging slow today?" The doctor checks recent deploys, traffic patterns, downstream services, and external API latencies. Returns a diagnosis with the supporting data — not a summary.
We don’t run your infrastructure with AI. AWS does. Fortem’s agents observe, diagnose, and suggest — humans approve anything that mutates state. The agent doesn’t have an IAM role to apply changes without you.
What the auditor will ask for — answered before they ask.
The engineer who built Fortem's IAM model spent six years answering SOC 2 questions for 85+ regulated banks running on AWS. The list below is the answer to those questions, written into the product. Full security breakdown →
SOC 2 Type II
Audit in progress. Download the security packet with IAM policy, architecture diagram, and data-flow — bring it to your security team today.
Your data, your AWS
Fortem runs inside your AWS account. Your workloads, secrets, and data live in yours. We never touch them.
Secrets stay in your KMS
Env vars go to your AWS Parameter Store or Secrets Manager. We store references, not values.
Audit logs
Who scheduled what, who cloned which env, who approved which AI suggestion. Exportable.
SSO & SCIM
SAML SSO, SCIM provisioning, IP allowlist management — included from the Business plan.
GDPR
Your workloads and data never leave your AWS account. Fortem holds metadata only — service names, schedule configs, task counts. Your jurisdiction, your control.
We charge per environment. Not per service.
Per-service pricing punishes you for breaking up a monolith. A 12-service environment shouldn't cost 4× a 3-service one — same blast radius, same on-call rotation, same staging fleet. Pay for environments. That's the unit you actually manage.
- Up to 20 environments
- 1 AWS account
- Single region
- Scheduling
- Unified environment view
- Basic AI diagnostics
- 2 external connectors (e.g. Atlas, Firebase)
- 30-day audit log in Fortem UI
- Email support (24h response)
Small fleet? See your real numbers first →
- Up to 80 environments
- 3 AWS accounts
- Multi-region
- Everything in Starter, plus:
- Templates
- AI Ops (cost watcher, environment doctor)
- RBAC + SSO/SAML
- 5 external connectors (e.g. Atlas, Firebase)
- 90-day audit log in Fortem UI
- Email + Slack support (8h response)
Want to check the math? Audit your fleet →
- Unlimited environments
- Unlimited AWS accounts
- Multi-region
- Everything in Scale, plus:
- Custom integrations
- Unlimited connectors + custom
- 365-day audit log, custom retention
- Slack + on-call support (2h SLA)
Common questions (aka FAQ)
Stop paying for environments nobody opened this weekend.
Run the Fleet Audit — free, read-only, 15 min. Or book 20 minutes with an engineer. Either way, you'll see exactly what you'd save.