For cloud consultancies, AWS partners & MSPs
CloudCostFlow models the whole system, not the parts — traffic, caching, cross-AZ, data transfer — so the number in your proposal is one you can stand behind. Win more engagements. Stop eating the overruns.
Traffic flows through your architecture like a real system. A CloudFront cache hit means fewer ALB requests, fewer EC2 cycles, fewer database queries. We model the cascade.
Double your traffic and see exactly where costs spike. Change your cache hit ratio from 80% to 95% and watch downstream costs plummet. One slider, full impact.
Know exactly what each API call costs you — broken down by variable vs fixed components. See how per-request cost drops as you scale.
Interactive topology diagram showing every service, connection, and traffic flow. Click any node to configure it. Click any edge to adjust the flow.
EC2 auto-scaling groups calculate instance count from your traffic. Set a threshold, define min/max, and the engine figures out how many instances you'll actually run.
The hidden killer. Cross-AZ, cross-region, internet egress — we calculate the real data transfer costs between every service pair in your architecture.
Every other tool prices services in isolation — so your estimate is a ±50% guess with your margin riding on it. We model how they connect.
Add the services they'll actually run — ALB, EC2, RDS, CloudFront, Lambda and more — or start from a reference architecture. Configure each with real parameters.
Requests/month, cache hit ratio, read/write split, network context (same-AZ, cross-AZ, internet) — the real-world inputs that move the number.
Cost lands service by service, cross-AZ and data transfer included. Change anything and watch it cascade — then hand the client a proposal you can defend.
Not a personal toy. Lead with the plan that fits how consultancies buy — a solo option for individuals, Enterprise for larger practices.
For the individual architect
One avoided overrun pays for the year
Large practices & partner networks
Free tier: try the engine with up to 5 services, no account required. Open the builder →
Why I built this
“I built CloudCostFlow because I was tired of pricing architectures with brittle spreadsheets and gut feel — and tired of tools that price cloud like a parts catalogue when the real costs cascade through the system. It’s the tool I wanted every time I had to put a number in front of someone who’d hold me to it.”
— Graham, platform engineer & founder