API management platforms
API management platforms sit in front of your APIs to handle authentication, rate limits, analytics, a developer portal, and increasingly AI and MCP traffic. This grid compares seven well-known options on what you can see before talking to sales: entry price, free access, how pricing works, where it can run, and which capabilities come built in.
Last updated
How to choose
Start with where your APIs run and who must operate the gateway. A fully managed service (Amazon API Gateway, Zuplo) means no servers to patch, while hybrid or self-hosted options (Kong, Tyk, Gravitee, Apigee hybrid, Azure's self-hosted gateway) keep traffic inside your own network for compliance or latency.
Check the pricing model first
- Per call (Amazon, Zuplo, Apigee pay-as-you-go) is cheap at low volume and grows with traffic.
- Per gateway, environment, or API (Gravitee, Azure tiers, Kong control planes, Tyk Core) is more predictable but has a higher floor.
- Sales-quoted only (Tyk) means you cannot compare cost before a call.
Then compare what you will actually use
- A built-in developer portal and monetization matter if outside developers or partners consume your APIs.
- AI and MCP gateway features matter if you route LLM or agent traffic through the same platform.
- GraphQL and Kafka or event stream support matter only if your APIs are not plain REST.
Pitfalls
- Entry prices rarely include analytics, SSO, audit logs, or SLAs; those are often add-ons or enterprise-only.
- Free tiers differ: some last 12 months, some 30 to 60 days, and one is free indefinitely at low volume.
- Run a small pilot with your real traffic before committing to an annual contract.
Answer
Browse the table. Filter to what matters.
Use the filters below, then sign in if you want to shortlist and decide with friends.
Sign in to vote, hide services and features, and reorder.
Verified: hover a cell and click its green dot for the source Estimate: no cited source Not stated: the company doesn't publish it
| Feature | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ |
|---|---|---|---|---|---|---|---|
|
⠿
Entry price
|
|||||||
|
⠿
Free trial or plan
|
|||||||
|
⠿
Pricing model
|
|||||||
|
⠿
Public list prices
|
|
||||||
|
⠿
Deployment options
|
Managed AWS service only
|
||||||
|
⠿
Open source gateway
|
|
|
|
|
|||
|
⠿
Developer portal
|
|||||||
|
⠿
API monetization
|
|
|
|
||||
|
⠿
AI and MCP gateway
|
|
||||||
|
⠿
GraphQL support
|
|
|
|
||||
|
⠿
Kafka and event streams
|
|
|
|
|
Why these features matter
-
Entry price ($/month)
Shows how much it costs to get started, but compare it with the pricing model: a low entry price can still grow quickly with traffic.
-
Free trial or plan
Lets you test against your own traffic before paying. Free tiers differ widely in length and limits.
-
Pricing model
Per-call pricing suits spiky or small workloads; per-gateway or per-environment pricing is more predictable at high volume.
-
Public list prices
Published prices let you estimate cost before talking to sales.
-
Deployment options
Data residency, latency and compliance rules can require the gateway to run inside your own network.
-
Open source gateway
An open-source gateway lowers lock-in and lets you start free, though management features may still be paid.
-
Developer portal
Needed if partners or outside developers use your APIs.
-
API monetization
Lets you charge for API use without building billing yourself.
-
AI and MCP gateway
Matters if AI model or agent calls should share the same security, limits and cost tracking as your APIs.
-
GraphQL support
Matters only if your APIs use GraphQL rather than plain REST.
-
Kafka and event streams
Matters if you want streaming and event APIs managed alongside request-response APIs.
About the services
-
Kong Konnect · Kong Inc.
Kong's cloud API, AI and event management platform built on the open-source Kong Gateway. The Plus plan starts at $25 per month plus usage; Enterprise is custom and adds SSO, RBAC and audit logs. Suits teams that want a flexible gateway with a self-serve entry point.
-
Amazon API Gateway · Amazon Web Services
AWS's managed gateway for REST, HTTP and WebSocket APIs. There are no minimums: you pay per call and for data out. Best for teams already on AWS and Lambda; less of a full lifecycle platform than the others.
-
Azure API Management · Microsoft
Microsoft's API management service in tiered units (Consumption, Developer, Basic, Standard, Premium, and newer v2 tiers). Fits Azure-centric organizations; the Premium tier adds multi-region and a self-hosted gateway for hybrid use.
-
Apigee · Google
Google Cloud's enterprise API management platform with pay-as-you-go and subscription pricing. A 60-day free evaluation is available; paid use starts with a Base environment at $365 per month per region.
-
Tyk · Tyk
API management with an open-source gateway and paid Core, Professional and Enterprise plans for cloud, hybrid or self-managed use. Prices are quoted by sales only; a 48-hour cloud trial and a 14-day self-managed trial are self-serve.
-
Gravitee · Gravitee
A platform covering APIs, event streams and AI agents. The Planet tier is $2,500 per month with unlimited users; Galaxy and Universe are custom. A good fit when you need both REST and Kafka-style event APIs governed together.
-
Zuplo · Zuplo
A managed, code-first API gateway run from GitHub with edge deployment. Free up to 100k requests per month; the $25 Builder plan is aimed at solo projects and teams needing SSO or an SLA need Enterprise.
Suggest a change
Related comparisons
-
Translation management softwareTranslation management systems (TMS) keep a team's UI strings, documents and translations in one place, with translation memory, glossaries, machine and human translation, and integrations with code and design tools. The decision is how you are charged (words, strings or keys), what a free plan covers, and how much automation and security you need.
-
Feature flag toolsFeature flag tools let engineers switch features on or off, roll them out to a slice of users, and roll them back without redeploying. This grid compares ten hosted and self-hosted tools, from open source servers to full experimentation platforms. The real trade-offs are how each one bills (per seat, per request, per user), whether you can run it yourself, and whether approvals, SSO, and A/B testing sit behind an enterprise plan.
-
Incident management softwareIncident management software wakes the right person when something breaks, gives the team one place to run the response, and records what happened so it doesn't happen again. This grid compares eight tools on what most buyers decide on: what the first paid plan really costs, whether on-call paging is included or sold separately, how well incidents run inside Slack or Teams, and how far AI goes.
-
Status page softwareStatus page software gives your customers one trusted place to see whether your service is up, read incident updates, and subscribe to alerts. Some tools are stand-alone status pages, while others bundle uptime monitoring, on-call paging, or full incident response. The trade-offs are price model (flat plan, per user, or per component), how many subscribers and team members each plan allows, and whether monitoring and paging come with it.
-
CI/CD platformsCI/CD platforms build, test, and ship your code automatically every time you push a change. The real decision is whether to use the pipeline built into the place where your code already lives, or an independent service, and how you want to pay: per user, per build minute, or with your own servers.
-
Low-code platformsLow-code platforms let teams build business apps, internal tools and workflows with visual builders and a little code instead of full software projects. The real decision is between developer-friendly tools you can self-host and enterprise platforms sold on custom quotes.