Fastly API Gateway pricing : Compute@Edge plus NGWAF
Fastly tiered request + bandwidth pricing applied to API workloads, plus NGWAF and API Security add-ons. Edge-API economics versus Cloudflare.
// vendor.fastly-api-gateway{"name": "Fastly API Gateway","pricing_model": "Tiered request + bandwidth + Compute@Edge per-invocation","public_pricing": "true","cheapest_published_rate": "50 /month (minimum commit)","primary_source": "https://www.fastly.com/pricing","verified_date": "2026-06-20"}
POST primary pricing verb for Fastly API Gateway in this site's visual taxonomy.
Per-request vs bandwidth dominance
At small payloads (token-light JSON), per-request dominates the bill. At larger payloads (image, media, large API responses), bandwidth dominates. Model both lines together.
Edge-API fit
Fastly is a strong fit when low latency, high cache-hit ratio, and Compute@Edge programmability matter. It is a weak fit when the buyer wants a turnkey developer portal.
Recent change
Fastly continues to publish Compute@Edge per-million-request rates and bandwidth tiers; enterprise commits remain quote-only.
Editor's note
Fastly's API gateway story is Compute@Edge plus NGWAF + API Security. Per-request rate is competitive at the edge but the bill is driven by bandwidth at high volume.