# Amazon API Gateway vs Apigee

Canonical: https://inetgeek.com/compare/aws-api-gateway-vs-apigee/

Every value below is read from Amazon API Gateway's and Apigee's own documentation. See https://inetgeek.com/methodology/ for how.

## At a glance

| Criterion | Amazon API Gateway | Apigee |
| --- | --- | --- |
| 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. |
| 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 ([source](https://aws.amazon.com/api-gateway/pricing/))
- Apigee: Free trial ([source](https://cloud.google.com/apigee/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. ([source](https://aws.amazon.com/api-gateway/pricing/))
- 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. ([source](https://cloud.google.com/apigee/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. ([source](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonApiGateway/current/us-east-1/index.json))
- 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. ([source](https://cloud.google.com/apigee/pricing))

### Uptime SLA

- Amazon API Gateway: 99.95% Monthly Uptime Percentage per region, backed by service credits. ([source](https://aws.amazon.com/api-gateway/sla/))
- Apigee: 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. ([source](https://cloud.google.com/apigee/sla))

## Which should you choose?

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.

Consider something else: 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.

Consider something else: 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.

## Documented by only one

- Rate limits: Apigee: 50 queries per second on a Base environment. Throughput is a property of the environment type rather than a usage line you can raise, so more requests per second means a more expensive environment rather than a larger bill for the same one.

## 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.