The API Gateway Cost Forecast Estimator projects a future monthly API gateway workload cost from a starting workload, an expected monthly growth rate, a unit price, and any fixed platform charge. It is useful when a team needs a simple run-rate view before traffic or usage has fully materialized.
The result separates projected workload from variable and fixed cost so you can see what is driving the estimate. Use it for budgeting and scenario planning rather than as a provider invoice replica; tiered pricing, regional rates, taxes, credits, and special contracts can change actual charges.
1. Enter the current workload
Use the latest representative monthly gateway request volume in million requests.
2. Set expected growth
Enter the monthly percentage change; a negative value can model contraction.
3. Choose the horizon
Specify how many months forward to compound the growth assumption.
4. Add pricing
Enter the variable price per unit and any recurring fixed monthly charge.
5. Review the forecast
Compare projected workload, variable cost, and total monthly cost.
Projected workload = Current workload × (1 + Growth rate / 100)^Months Variable cost = Projected workload × Unit cost Forecast monthly cost = Variable cost + Fixed monthly cost
Workload is measured in million requests. The model compounds the entered growth rate once per month and applies one constant unit price to the projected workload.
The main result is a planning metric for gateway request volume; use it with consistent units and scope when comparing scenarios.
Actual provider billing or operational limits can differ because of tiers, discounts, quotas, regions, architecture, and contract terms.
Given: 50,000 million requests per month, 5% monthly growth, 6 months, $0.08 per million requests, and $200 fixed cost.
Calculation: 50,000 × 1.05^6 = 67,004.78 million requests. Variable cost = 67,004.78 × $0.08 = $5,360.38. Total = $5,360.38 + $200 = $5,560.38.
Result: Forecast monthly cost is about $5,560.38 after six months.
No. It applies one blended unit price to the projected workload. If your provider uses tiers, enter an estimated blended rate or run separate scenarios.
Yes, as long as it is above -100%. A negative rate models declining monthly workload.
No. The main result is the estimated monthly run rate at the end of the selected horizon.
Include recurring charges that do not scale directly with the workload represented by the unit price. Leave it at zero if none apply.
Use it as a planning baseline and test several growth and price assumptions. Actual billing can differ because of tiers, discounts, regions, taxes, or traffic mix.