See the Real Cost

Change one parameter. Watch costs cascade through your entire architecture. That's what CloudCostFlow does — and no other tool can.

Example: Static website with CDN

A simple, common architecture — CloudFront serving content from S3. Same setup, two different traffic levels. Look at how costs change when you understand the connections.

UsersHTTP requests
CloudFrontCDN / Cache
S3Origin / Storage
Scenario A: 10M requests/mo
Input Parameters
Monthly requests10,000,000
Cache hit rate92%
GET / PUT ratio95% / 5%
Avg payload size250 KB
Stored objects50 GB
CloudFront
Requests (10M × $0.0085/10K)$8.50
Data out (10M × 250KB = 2,500 GB)$212.50
S3 (origin hits only)
GET requests (760K miss)$0.30
PUT requests (500K)$2.50
Storage (50 GB)$1.15
Data transfer to CF$0.00
$224.95
per month
Scenario B: 100M requests/mo
Input Parameters
Monthly requests100,000,000
Cache hit rate97%
GET / PUT ratio95% / 5%
Avg payload size250 KB
Stored objects50 GB
CloudFront
Requests (100M × $0.0085/10K)$85.00
Data out (100M × 250KB = 25,000 GB)$2,051.20
S3 (origin hits only)
GET requests (2.85M miss)$1.14
PUT requests (5M)$25.00
Storage (50 GB)$1.15
Data transfer to CF$0.00
$2,163.49
per month

See what just happened?

10× the traffic didn't mean 10× the cost. It meant 9.6× the cost — because the cache hit rate improved from 92% to 97%, meaning fewer origin fetches per request. Cost per million requests actually dropped from $22.50 to $21.63. S3 origin requests only went from 800K to 3M (3.75×, not 10×).

And the thing no spreadsheet tells you: S3→CloudFront data transfer is free. That single fact saves hundreds per month at scale. CloudCostFlow knows this because it models the connection, not just the services.

The Parameters That Change Everything

These are the inputs other tools ignore — and they're the ones that determine whether your architecture costs $200/month or $2,000.

Cache Hit Rate

Every 1% improvement in cache hit rate reduces origin requests, S3 GETs, and data transfer. At 100M requests, going from 95% → 97% saves 2M origin hits.

92% → 97% = 62% fewer origin requests

GET / PUT Ratio

S3 PUT requests cost 10× more than GETs ($5.00 vs $0.40 per million). A write-heavy workload has fundamentally different economics.

PUTs at $5.00/M vs GETs at $0.40/M

Average Payload Size

This is the biggest cost lever. CloudFront data transfer is priced per GB. Doubling payload size doubles your data transfer bill — the largest line item.

250KB → 500KB = 2× data transfer cost

Network Context

S3→CloudFront is free. S3→Internet is $0.09/GB. Same data, same bytes — but the connection determines the price. This is why graph-based modeling matters.

Free vs $0.09/GB — same data, different path

Three Steps. Real Numbers.

1

Build Your Architecture

Add services. Connect them. Set traffic entry points — "10M requests hit CloudFront."

2

Set Your Parameters

Cache ratios, payload sizes, read/write splits, instance types. The inputs that actually determine your bill.

3

Change Anything

Slide one parameter. Watch every connected service recalculate. See the full cost impact instantly.

Build This Architecture in 60 Seconds

The CloudFront → S3 example above? You can build it right now. Change the numbers. See what your architecture actually costs.

Open the Builder →