Calculator Inputs
Cost Breakdown Chart
The chart highlights which pricing drivers contribute most to the monthly estimate.
Example Data Table
| Scenario | Requests / Month | Duration | Memory | Provisioned Concurrency | Focus |
|---|---|---|---|---|---|
| API Microservice | 2,000,000 | 250 ms | 512 MB | 0 | Balanced traffic with moderate compute demand |
| Image Processing | 500,000 | 1,800 ms | 1,536 MB | 5 | Longer execution and stronger memory requirements |
| Streaming Webhook | 8,500,000 | 120 ms | 256 MB | 10 | High request volume with low average runtime |
Formula Used
1) Total Requests
Total Requests = Monthly Requests × (1 + Retry Overhead ÷ 100)
2) Request Cost
Request Cost = Max(0, Total Requests − Free Requests) ÷ 1,000,000 × Request Price × Architecture Multiplier
3) Compute Usage
GB-Seconds = Total Requests × (Memory MB ÷ 1024) × (Duration ms ÷ 1000)
4) Compute Cost
Compute Cost = Max(0, GB-Seconds − Free GB-Seconds) × Compute Price × Architecture Multiplier
5) Ephemeral Storage Cost
Ephemeral Cost = Total Requests × Duration Seconds × Extra Storage GB × Usage Percent × Ephemeral Rate
6) Provisioned Concurrency Capacity Cost
Capacity Cost = Provisioned Units × Memory GB × Provisioned Hours × Capacity Rate
7) Provisioned Concurrency Compute Cost
Provisioned Compute Cost = Provisioned Units × Memory GB × Hours × 3600 × Utilization × Compute Rate
8) Monthly Forecast
Monthly Forecast = Subtotal × (1 + Traffic Growth ÷ 100)
How to Use This Calculator
- Enter your expected monthly request count.
- Provide average runtime in milliseconds and memory size in MB.
- Select the architecture that matches your function deployment.
- Add retry overhead if failed events commonly trigger reprocessing.
- Enter ephemeral storage only when your workload uses extra temporary disk space.
- Fill provisioned concurrency inputs only if you keep instances warm.
- Review or replace the sample pricing inputs with your own rate card.
- Submit the form and review the summary, chart, CSV, and PDF exports.
FAQs
1. What does this calculator estimate?
It estimates monthly and annual Lambda spending using requests, compute time, memory allocation, ephemeral storage, and provisioned concurrency inputs. It is designed for fast planning, budgeting, and comparing workload shapes before deployment.
2. Does it include free tier adjustments?
Yes. You can enter free requests and free GB-seconds. The estimator subtracts those values before calculating billable request and compute charges, which helps model smaller environments or accounts with remaining allowances.
3. Why is memory important in serverless pricing?
Memory affects billed GB-seconds because compute usage multiplies runtime by allocated memory. Increasing memory may raise per-invocation cost, but it can also shorten runtime and sometimes reduce total spend.
4. What is provisioned concurrency in this model?
Provisioned concurrency represents pre-warmed execution environments kept ready for traffic. This calculator estimates both reserved capacity cost and compute cost while those reserved environments actively execute requests.
5. Does this estimator include data transfer pricing?
No. Average response size is stored as a planning note only. Network transfer, API gateway, storage, observability, and other adjacent services are excluded from this model and should be estimated separately.
6. Why is architecture included?
Architecture can influence cost and performance. This page applies a simple multiplier so you can compare x86 and ARM style deployments. Replace the sample rate logic if your environment follows different pricing assumptions.
7. Can I use custom pricing values?
Yes. All major rate inputs are editable, including request, compute, ephemeral storage, and provisioned concurrency pricing. That makes the calculator useful for internal chargeback models or region-specific rate cards.
8. Is this suitable for production approvals?
It is best for forecasting and comparing scenarios. Before approving budgets, validate pricing, region, sustained usage patterns, retry behavior, adjacent service costs, and discounts against your official cloud billing sources.