Amazon API Gateway vs Apigee
SEPT 2026 auditA comparison of Amazon API Gateway and Apigee built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
Choose Amazon API Gateway if…
APIs that already live in AWS, where the gateway can reach a Lambda or a private VPC service without leaving the account. Nothing is bought in advance: no minimum fee, no upfront commitment, and $1.00 per million HTTP API requests from the first one.
Editorial · Palash Bagchi · approved
Choose Apigee if…
API programmes that need policy depth and are already on Google Cloud, with 60 days of sandbox evaluation before any commitment and volume rates that fall to $13 per million calls above 500 million.
Editorial · Palash Bagchi · approved
Consider something else if…
- Amazon API Gateway: You would pick the wrong API type by accident. REST APIs cost $3.50 per million against HTTP APIs at $1.00 — the same traffic, three and a half times the bill — and the choice is made when you create the API, not when the invoice arrives.
- Apigee: Cost at the bottom end decides it. The floor is $365 a month per region for a Base environment before a single call is served, against $25 at Kong and Zuplo and nothing at all at AWS — and an Extensible proxy, the one that unlocks the full policy set, is $100 per million against a Standard proxy at $20.
4 sourced criteria separate them — see where, with sources, below.
Pick the criteria you care about. The chart counts how many of them lean toward each provider — the same read as scanning the bars below, just totalled for the ones you chose.
Amazon API Gateway 0
Apigee 0
At a glance.
| Criterion | Amazon API Gateway | Apigee |
|---|---|---|
| Pricing | ||
| Free tier | Yes | Yes |
| Kind of free offer | Free credit | Free trial |
| Entry paid plan | None. There are no minimum fees and no upfront commitments — you pay per request from the first one, at $1.00 per million for HTTP APIs and $3.50 per million for REST APIs in us-east-1. | $365 a month per region for a Base environment, plus $20 per million API calls on a Standard proxy. Pay-as-you-go means no contract, not no floor — calls are served by an environment and the cheapest environment carries that monthly charge whether traffic arrives or not. The most expensive entry in this category by an order of magnitude. |
| Pricing model | Per request, and the rate depends on which of two API types you deploy: $1.00 per million HTTP API requests falling to $0.90 above 300 million, against $3.50 per million REST API requests falling to $1.51 above 20 billion. WebSocket APIs are billed separately at $1.00 per million messages plus $0.25 per million connection-minutes. Data transfer out is charged on top, except on Private APIs. | Per million API calls, at a rate set by which of two proxy types serves them. A Standard proxy is $20 per million up to 50 million, $16 to 500 million and $13 above that; an Extensible proxy, which unlocks the full policy set, is $100, $80 and $64 across the same bands — five times the price for the same call volume. Choosing the proxy type is therefore a pricing decision as much as a capability one. |
| Infrastructure | ||
| Uptime SLA | 99.95% Monthly Uptime Percentage per region, backed by service credits. | 99.99% for Pay-as-you-go, Enterprise and Enterprise Plus subscriptions; 99% for Apigee Standard. The pricing page states it differently again, capping a Base environment at "up to 99%" — so a pay-as-you-go customer holds a 99.99% commitment while deploying into environments the price table rates at 99%, and neither page reconciles the two. |
Where they differ.
Kind of free offer
- Amazon API Gateway
- Free credit
- Apigee
- Free trial
Sources (2) →Sources ↓
- Amazon API Gateway Pricing ↗
“up to $200 in AWS Free Tier credits”
Read 2026-09-15 · official pricing
- Apigee pricing ↗
“in your own sandbox at no cost for 60 days”
Read 2026-09-15 · official pricing
Entry paid plan
- Amazon API Gateway
- None. There are no minimum fees and no upfront commitments — you pay per request from the first one, at $1.00 per million for HTTP APIs and $3.50 per million for REST APIs in us-east-1.
- Apigee
- $365 a month per region for a Base environment, plus $20 per million API calls on a Standard proxy. Pay-as-you-go means no contract, not no floor — calls are served by an environment and the cheapest environment carries that monthly charge whether traffic arrives or not. The most expensive entry in this category by an order of magnitude.
Sources (2) →Sources ↓
- Amazon API Gateway Pricing ↗
“There are no minimum fees or upfront commitments.”
Read 2026-09-15 · official pricing
- Apigee pricing ↗
“$365 per month per region Up to 50 QPS”
Read 2026-09-15 · official pricing
Pricing model
- Amazon API Gateway
- Per request, and the rate depends on which of two API types you deploy: $1.00 per million HTTP API requests falling to $0.90 above 300 million, against $3.50 per million REST API requests falling to $1.51 above 20 billion. WebSocket APIs are billed separately at $1.00 per million messages plus $0.25 per million connection-minutes. Data transfer out is charged on top, except on Private APIs.
- Apigee
- Per million API calls, at a rate set by which of two proxy types serves them. A Standard proxy is $20 per million up to 50 million, $16 to 500 million and $13 above that; an Extensible proxy, which unlocks the full policy set, is $100, $80 and $64 across the same bands — five times the price for the same call volume. Choosing the proxy type is therefore a pricing decision as much as a capability one.
Sources (2) →Sources ↓
- AWS Price List — AmazonApiGateway, us-east-1 ↗
“$1/million requests - API Gateway HTTP API (first 300 million)”
Read 2026-09-15 · official docs
- Apigee pricing ↗
“Costs provided are per 1M API calls.”
Read 2026-09-15 · official pricing
Uptime SLA
99.95% Monthly Uptime Percentage per region, backed by service credits.
99.99% for Pay-as-you-go, Enterprise and Enterprise Plus subscriptions; 99% for Apigee Standard. The pricing page states it differently again, capping a Base environment at "up to 99%" — so a pay-as-you-go customer holds a 99.99% commitment while deploying into environments the price table rates at 99%, and neither page reconciles the two.
Sources (2) →Sources ↓
- Amazon API Gateway Service Level Agreement ↗
“Monthly Uptime Percentage of at least 99.95% for each AWS region”
Read 2026-09-15 · official docs
- Apigee Service Level Agreement ↗
“Apigee Enterprise, Apigee Enterprise Plus, or Apigee Pay-as-you-go”
Read 2026-09-15 · official docs
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.
Documented by only one.
These criteria are published by one provider and not the other. An absence here means we have not found a source, not that the feature is missing.
Questions this comparison answers.
Entry paid plan: Amazon API Gateway or Apigee?
Amazon API Gateway: None. There are no minimum fees and no upfront commitments — you pay per request from the first one, at $1.00 per million for HTTP APIs and $3.50 per million for REST APIs in us-east-1.
Apigee: $365 a month per region for a Base environment, plus $20 per million API calls on a Standard proxy. Pay-as-you-go means no contract, not no floor — calls are served by an environment and the cheapest environment carries that monthly charge whether traffic arrives or not. The most expensive entry in this category by an order of magnitude.
Should I choose Amazon API Gateway or Apigee?
Pick Amazon API Gateway if APIs that already live in AWS, where the gateway can reach a Lambda or a private VPC service without leaving the account. Nothing is bought in advance: no minimum fee, no upfront commitment, and $1.00 per million HTTP API requests from the first one.
Pick Apigee if API programmes that need policy depth and are already on Google Cloud, with 60 days of sandbox evaluation before any commitment and volume rates that fall to $13 per million calls above 500 million.