LAMBDA VS FARGATE COST BREAK-EVEN · RUNS IN YOUR BROWSER

Lambda, Cloud Run, Fargate or EC2: which is cheapest for your traffic?

Enter your monthly requests, average duration, memory, vCPU and concurrency. Get the monthly cost on each platform, the cheapest option, the request volume where always-on containers beat pay-per-request, and how the answer shifts at 0.1x to 10x your traffic.

Nothing is uploaded and no cloud account is contacted. The numbers are used in this browser and never leave your device. This is an estimate, not a bill.

1. Describe the workload

Prices, editable

Re-run Compare after editing. Free tiers, Savings Plans, committed-use discounts, data transfer, load balancers and NAT are not modelled.

Prefer a CLI, or want a CI check?

Same logic, zero dependencies, one command:

node cli.mjs compare --requests 20M --duration-ms 120 --memory 0.5 --vcpu 0.25 --concurrency 10
node cli.mjs compare workload.txt --json
node cli.mjs breakeven --duration-ms 300 --memory 1 --concurrency 1
node cli.mjs compare workload.txt --expect fargate     # exit 1 when another platform is cheapest

Get cli.mjs and engine.mjs — Node 18+, nothing to install, no network call. More: Lambda vs Fargate vs Cloud Run: what each actually costs.

What's recognised

InputHandling

Common questions

Does this connect to my AWS or Google Cloud account?

No. It reads the numbers you type and never contacts a cloud or any server. It cannot see your real invoice, free tier, savings plans or discounts, so every figure is arithmetic on list prices you can edit. This is an estimate, not a bill.

Why does the break-even move so much between workloads?

Pay-per-request platforms charge for every request-second, so cost grows in a straight line with traffic. Always-on platforms charge for a floor of capacity, so cost is flat until traffic outgrows it. Duration, memory and how many requests one container handles at once decide where the lines cross.

What does concurrency mean here?

How many requests one container or task serves at the same time. Lambda runs one request per environment. Cloud Run and Fargate containers usually handle 10 to 80, which is the main reason they get cheaper than Lambda at steady volume.

What does this leave out?

Free tiers, committed-use and Savings Plans discounts, data transfer, load balancer and NAT costs, cold starts and latency, provisioned concurrency, autoscaling lag, ops time and region differences. Treat the result as a first filter, then check your own bill.

Is what I type uploaded anywhere?

No. The page does the arithmetic in your browser and never sends the numbers anywhere. The CLI reads local files and makes no network call.