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. You pay per environment. 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)
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%.
Common questions
Does Fortem charge per service or per environment?
Per environment. A 12-service environment costs the same as a 3-service environment. You manage environments, not individual services — so that's the unit we charge for.
What counts as an environment?
One ECS cluster. A cluster can contain any number of services. Your dev, staging, QA, and production clusters each count as one environment.
How long does onboarding take?
Seven business days from first call to configured fleet. A Fortem engineer audits your AWS setup, imports your environments, configures schedules per timezone, and hands you the keys.
What happens if I exceed my environment limit?
We'll reach out before anything breaks. You can upgrade to the next tier or we can discuss a custom arrangement. Nothing gets turned off without a conversation first.
Is there a free trial?
No — and on purpose. Onboarding Fortem takes a Fortem engineer's time. A trial that ends in churn helps nobody. Instead, run the Fleet Audit: a free read-only scan of your ECS fleet that gives you real savings numbers in 15 minutes. If the numbers make sense, book a call. If they don't, you saved yourself a conversation.
Are you SOC 2 certified?
Not yet — we won't pretend otherwise. Here's what's true today: read-only by default, a published least-privilege IAM policy you can audit, no access to your data/secrets, and a 2-minute uninstall. Need more for your security team? Download the security packet or ask about self-hosted on the Custom plan.