Request Pricing Hub: calculators, guides, and next steps
Start with a calculator if you need a first-pass estimate, then use this guide to validate the assumptions and catch the billing traps.
This is the request boundary page. Retries, bots, cache misses, and other traffic amplifiers belong in this model
before you price the bill.
Use the calculators only after the boundary is defined so every estimate inherits the same definition of billable
requests.
Choose your next step
Use this hub when you only need routing
- Use this page when you already know the topic and just need the shortest path to the stronger guide or tool.
- Do not use this page as your main explainer if you still need unit mapping, traffic-shape modeling, or validation steps.
- That full job belongs to request-based pricing explained.
The biggest mistake on this page is reading a hub like a full guide
This page exists to reduce confusion, not to reteach the whole request-pricing workflow. If you still need a
complete estimate method, jump to the main request guide instead of trying to piece the workflow together from a hub.
Fast exits by problem type
For the full workflow, continue with request-based pricing explained.
This page should stay a lightweight navigation stop.
Related tools
More request pricing guides
API Gateway access logs cost: how to estimate ingestion and retention
A practical guide to estimate API Gateway access logs cost: estimate average bytes per request, convert to GB/day, model retention (GB-month), and reduce log spend safely.
API Gateway cost optimization: reduce requests, bytes, and log spend
A practical playbook to reduce API Gateway spend: identify the dominant driver (requests, transfer, or logs), then apply high-leverage fixes with a validation checklist.
API Gateway pricing: what to model (requests + transfer)
Model AWS API Gateway pricing across request charges, data transfer, logs, and adjacent add-ons, with a clearer checklist for what belongs in the API bill versus downstream systems.
API Gateway vs ALB vs CloudFront cost: what to compare (requests, transfer, add-ons)
A practical cost comparison of API Gateway, Application Load Balancer (ALB), and CloudFront. Compare request pricing, data transfer, caching impact, WAF, logs, and the hidden line items that change the answer.
AWS CloudWatch Metrics Pricing: Custom Metrics, API Requests, Dashboards, and Resolution
Understand AWS CloudWatch metrics pricing through custom metrics, metrics API requests, dashboards, high-resolution usage, and the alarm or external observability costs that belong beside the metrics bill.
AWS cost checklist: model the drivers that actually move the bill
A practical AWS cost checklist for planning and reviews: define scope, identify top cost drivers (requests, GB, GB-month, hours), and avoid the common blind spots (data transfer, logs, and cross-AZ).
AWS Lambda pricing (what to include)
A practical checklist for estimating AWS Lambda-style costs: requests, duration × memory (GB-seconds), provisioned concurrency when used, logs, and common hidden line items.
AWS Network and Data Transfer Cost Guide
A practical AWS network cost hub for data transfer, NAT Gateway, VPC endpoints, PrivateLink, and cross-AZ or cross-region pricing. Built to support AWS data transfer calculator and network-cost workflows.
AWS SQS cost optimization (high-leverage fixes)
A practical playbook to reduce SQS costs: reduce requests per successful message with batching and long polling, prevent retry storms and poison loops, and validate savings with sent/received/deleted metrics.
AWS SQS pricing (what to include)
Estimate AWS SQS pricing by separating request-driven queue charges, retries, Receive/Delete and polling behavior, and the downstream compute or logging costs that belong beside the queue bill.
AWS WAF Pricing: Web ACLs, Request Charges, Bot Control, and Logging Boundaries
Understand AWS WAF pricing through Web ACL baselines, rule and request charges, blocked-traffic evaluation, Bot Control, CAPTCHA or Challenge actions, and the logging or SIEM costs that belong beside WAF.
AWS WAF vs Cloudflare WAF cost: a practical comparison checklist
Compare AWS WAF vs Cloudflare WAF cost using a practical checklist: request-based charges, rule/policy baselines, logging/analytics costs, and what to model for your traffic shape.
Azure API Management pricing: model requests, transfer, and log volume
A practical API Management estimate: request volume, response transfer, and logs/observability. Includes a checklist to validate retries, payload size, and usage tiers.
Azure Application Gateway pricing: how to model L7 load balancer costs
Model Azure Application Gateway pricing with gateway hours, request volume, traffic processed, WAF exposure, and log volume so peak traffic and the second bill do not disappear from the estimate.
Azure CDN pricing: estimate bandwidth, requests, and cache fill
A practical Azure CDN estimate: edge bandwidth, request volume, and origin egress (cache fill). Includes validation steps for hit rate, purge behavior, and big endpoints.
Azure Front Door pricing: model requests, bandwidth, and origin traffic
A practical Azure Front Door cost model: edge bandwidth, request volume, logging, and origin traffic (cache fill). Includes a checklist to validate hit rate and avoid double-counting egress.
Azure Key Vault pricing: estimate operations, keys/secrets, and request spikes
A practical Key Vault cost model: baseline objects (keys/secrets/certs) plus operation volume. Includes a workflow to map traffic to Key Vault calls and validate caching, retries, and hot-path mistakes.
Azure Load Balancer Pricing: Rules, Data Processed, and Bandwidth Boundaries
Understand Azure Load Balancer pricing through rules, data processed, and bandwidth boundaries. Learn when outbound rules, NAT Gateway, Application Gateway, and internet egress belong beside the load balancer line instead of inside it.
Related guides
API Gateway pricing: what to model (requests + transfer)
Model AWS API Gateway pricing across request charges, data transfer, logs, and adjacent add-ons, with a clearer checklist for what belongs in the API bill versus downstream systems.
GCP Cloud Run Pricing: Request-Based vs Instance-Based Billing, vCPU, Memory, and Egress
Understand Cloud Run pricing through request-based billing, instance-based billing, vCPU-seconds, memory GiB-seconds, request charges, jobs, egress, logs, and adjacent build or image storage costs.
S3 CRR vs SRR Cost Comparison: Transfer, Storage, and Request Fees
Compare S3 CRR vs SRR cost by separating cross-region transfer exposure, same-region replication, replica storage, request fees, and changed-data volume instead of relying on total bucket size.
S3 pricing explained: storage vs requests vs egress
A practical breakdown of S3-like object storage pricing: GB-month storage, request fees, and data egress - plus how to estimate each without missing hidden line items.
S3 pricing: a practical model for storage, requests, egress, and replication
Estimate S3 pricing by separating GB-month storage, requests, egress, replication, and delivery boundaries so the main object-storage bill is modeled from real usage drivers instead of copied price tables.
Storage Costs Explained (GB-month, requests, retrieval)
Build a practical storage cost model across GB-month, requests, retrieval, replication, and transfer, with a parent-guide view that helps map the whole storage budget before narrower pages.
Related calculators
FAQ
What services are request-priced?
Many edge and API products: API gateways, CDNs, WAFs, serverless invocations, and some messaging services. The unit varies by provider (per 10k, per 1M, per 100k).
How do I estimate quickly?
Convert RPS to monthly requests, then model retries separately. For fan-out systems (messaging), estimate deliveries per message and multiply.
What breaks estimates?
Retry storms, bot traffic, and unit mistakes (per 10k vs per 1M). Also, average RPS can hide spikes that dominate cost on bursty workloads.
Last updated: 2026-03-27. Reviewed against CloudCostKit methodology and current provider documentation. See the
Editorial Policy
.