Skip to content
inetGeek

Amazon API Gateway vs Zuplo

SEPT 2026 audit

A comparison of Amazon API Gateway and Zuplo built from values read directly from each provider's own documentation, with the source recorded against every figure.

Updated 8 criteria comparedSources last checked

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 Zuplo if…

Getting an API behind a gateway without a procurement conversation: 100,000 requests a month free forever, no card, with the developer portal, AI gateway and MCP gateway included rather than sold as tiers.

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.
  • Zuplo: Volume is the point. Builder bills $100 per additional 100,000 requests — $1,000 per million against AWS at $1.00 and Apigee at $20 — so the pricing is built for low traffic and gets expensive quickly above it.

4 sourced criteria separate them — see where, with sources, below.

Visit Amazon API Gateway documentationVisit Zuplo documentation

No affiliate links, sponsored placements or paid rankings appear on this site. Ordering follows the sourced data and the stated criteria.

01.

At a glance.

CriterionAmazon API GatewayZuplo
Pricing
Free tierYesYes
Kind of free offerFree creditFree tier
Entry paid planNone. 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.$25 a month for Builder, which includes 100,000 requests and then charges $100 per additional 100,000. Enterprise starts at $1,000 a month on an annual contract.
Pricing modelPer 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 request, in blocks: Builder includes 100,000 a month and bills $100 per 100,000 beyond it, which works out far above the per-million rates AWS and Apigee quote and is aimed at low volume rather than scale. The MCP gateway, AI gateway and developer portal are included on every plan rather than sold separately.
Infrastructure
Uptime SLA
99.95% Monthly Uptime Percentage per region, backed by service credits.
99.5% as the baseline, rising to as much as 99.999% on Enterprise. The lowest published floor in this category and the highest published ceiling, both on the same page.

Only criteria both providers publish appear here; a tinted cell marks a real difference. Criteria only one of them documents are listed below, and an absence there means we found no source — not that the feature is missing. How we source this.

The small bar above a value is inetGeek's own lean toward that side — computed from the same facts shown, never a number the provider published. See the picker below "The short answer" to weigh only the criteria you care about.

02.

Where they differ.

Kind of free offer

Amazon API Gateway
Free credit
Zuplo
Free tier
Sources (2) →

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.
Zuplo
$25 a month for Builder, which includes 100,000 requests and then charges $100 per additional 100,000. Enterprise starts at $1,000 a month on an annual contract.
Sources (2) →

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.
Zuplo
Per request, in blocks: Builder includes 100,000 a month and bills $100 per 100,000 beyond it, which works out far above the per-million rates AWS and Apigee quote and is aimed at low volume rather than scale. The MCP gateway, AI gateway and developer portal are included on every plan rather than sold separately.
Sources (2) →

Uptime SLA

Amazon API Gateway

99.95% Monthly Uptime Percentage per region, backed by service credits.

Zuplo

99.5% as the baseline, rising to as much as 99.999% on Enterprise. The lowest published floor in this category and the highest published ceiling, both on the same page.

Sources (2) →

When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.

Confirm by email; unsubscribe from any issue. Your address goes to Kit and nowhere else — what we do with it.

03.

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.

What the free plan includesZuplo: 100,000 requests a month, one day of analytics, live logs and traces, up to two developer seats and GitOps from GitHub. No card, and no expiry — the only standing free tier in this category rather than a trial or a credit.
SAML single sign-onZuplo: Supported — Enterprise tier, with RBAC alongside it
Audit logsZuplo: A full management audit trail, listed as an Enterprise-tier feature.
04.

Questions this comparison answers.

Entry paid plan: Amazon API Gateway or Zuplo?

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.

Zuplo: $25 a month for Builder, which includes 100,000 requests and then charges $100 per additional 100,000. Enterprise starts at $1,000 a month on an annual contract.

Should I choose Amazon API Gateway or Zuplo?

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 Zuplo if Getting an API behind a gateway without a procurement conversation: 100,000 requests a month free forever, no card, with the developer portal, AI gateway and MCP gateway included rather than sold as tiers.

Provider pages

Amazon API GatewayAWS's managed API gateway, billed per request at two different rates depending on which API type you deploy.ZuploA programmable API gateway deployed to the edge, billed per request with a free tier that does not expire.

Related comparisons

Amazon API Gateway vs ApigeeAmazon API Gateway vs Kong KonnectKong Konnect vs ZuploZuplo vs ApigeeKong Konnect vs Apigee

Every page here is sourced and dated.