SSubrupt
Skip to content

Best API Gateways of 2026

Updated · 7 picks · live pricing · affiliate disclosure

AWS-bundled pay-per-call gateway with REST/HTTP/WebSocket since 2015.

BEST OVERALL8.3/10

AWS API Gateway

AWS-bundled pay-per-call gateway with REST/HTTP/WebSocket since 2015.

Free 1M calls/mo for 12 months
Try AWS API GatewaySee full review

How it stacks up

  • Free 1M/mo 12mo

    vs Kong multi-cloud

  • HTTP $1/1M calls

    vs Apigee GCP

  • Launched 2015

    vs Zuplo edge

#2
KrakenD8.3/10

From $99/mo

View
#3
Kong7.2/10

From $250/mo

View

All picks at a glance

#PickBest forStartingScore
1AWS API GatewayBest AWS-bundled pay-per-call API gateway with REST plus HTTP plus WebSocketFree8.3/10
2KrakenDBest stateless aggregation Go-based gateway with single-binary deployment$99.00/mo8.3/10
3KongBest mainstream open-source enterprise API gateway with deepest plugin ecosystem$250.00/mo7.2/10
4Apollo Router (GraphOS)Best GraphQL Federation-anchored Rust-based router with GraphOS schema registry$250.00/mo6.3/10
5ZuploBest TypeScript programmable edge gateway with edge-deployed worldwide$250.00/mo6.2/10
6TykBest modern Go-based API gateway with GraphQL Federation built in$600.00/mo5.8/10
7Apigee (Google Cloud)Best Google Cloud-bundled API management platform since 2016 acquisition$500.00/mo5.7/10

Quick pick by use case

If you only have thirty seconds, find your situation below and skip to that pick.

If You are a platform engineering team wanting deepest plugin ecosystem with OSS-plus-cloud progressionKongKong ships 200+ plugin ecosystem with Apache 2 OSS plus Konnect cloud progression since 2015.If You are a Google Cloud-anchored enterprise running material API monetization plus developer portalsApigee (Google Cloud)Apigee ships broader API management platform (portal plus monetization plus analytics) with Google Cloud bundle.If You are an AWS-anchored serverless team running material Lambda workloads needing native integrationAWS API GatewayAWS API Gateway ships native AWS integration with REST/HTTP/WebSocket APIs since 2015.If You are a platform team wanting unified REST plus GraphQL gateway in one Go-runtime binaryTykTyk ships modern Go-based gateway with built-in GraphQL Federation and MPL 2 license since 2014.If You are running 10+ federated GraphQL subgraphs needing Federation 2 router plus schema registryApollo Router (GraphOS)Apollo Router ships GraphQL Federation-anchored Rust router plus GraphOS schema registry since 2022.If You are a TypeScript-anchored developer team wanting code-as-config gateway logic deployed to edge networksZuploZuplo ships TypeScript-based programmable gateway deployed to edge networks worldwide since 2022.

Compare all 7 picks

Top spec
#1AWS API Gateway8.3/10Free——Free 1M/mo 12mo
#2KrakenD8.3/10$99.00/mo$1,188.00/yrSave $1,812/yrOSS Apache 2
#3Kong7.2/10$250.00/mo$3,000.00/yr—Kong OSS Apache 2
#4Apollo Router (GraphOS)6.3/10$250.00/mo$3,000.00/yr—OSS Apache 2
#5Zuplo6.2/10$250.00/mo$3,000.00/yr—Free 1M/mo always
#6Tyk5.8/10$600.00/mo$7,200.00/yr$4,200/yr moreTyk OSS MPL 2
#7Apigee (Google Cloud)5.7/10$500.00/mo$6,000.00/yr$3,000/yr morePay-as-you-go $0.20/1M
#1

AWS API Gateway

8.3/10

Best AWS-bundled pay-per-call API gateway with REST plus HTTP plus WebSocket

Try AWS API GatewaySee AWS API Gateway alternatives

AWS-bundled pay-per-call gateway with REST/HTTP/WebSocket since 2015.

PlanMonthlyWhat you get
Free tierFree1M API calls/mo free for 12 months.
REST APIFree$3.50 per 1M calls with caching.
HTTP APIFree$1.00 per 1M calls with JWT auth.
WebSocket APIFree$1.00 per 1M messages plus connection time.

AWS API Gateway is the AWS-bundled pay-per-call API gateway for AWS-anchored organizations whose evaluation centers on native AWS ecosystem fit plus pay-per-call pricing. Launched 2015 with AWS Lambda, AWS API Gateway built around the thesis that AWS customers should not run a separate gateway vendor; the gateway should be a managed AWS primitive.

Four shapes. Free tier covers 1M API calls/mo free for 12 months with REST plus HTTP plus WebSocket APIs. REST API covers $3.50 per 1M calls plus optional caching at $0.02-3.80/hr per cache size. HTTP API covers $1.00 per 1M calls (lighter weight than REST) with JWT auth built in. WebSocket API covers $1.00 per 1M messages plus $0.25 per 1M connection minutes for long-lived connections.

The load-bearing wedge is the native AWS ecosystem fit. AWS customers running Lambda functions plus IAM authentication plus CloudWatch logs get an API gateway that integrates natively without separate vendor procurement; for serverless-anchored teams, AWS API Gateway is the procurement-natural pick. The catch is the AWS-only architecture; multi-cloud teams get less value, and pay-per-call pricing compounds at material scale.

Pros

  • Native AWS ecosystem fit (Lambda, IAM, CloudWatch)
  • HTTP API at $1/1M calls cheaper than REST
  • WebSocket API for long-lived connections
  • 1M calls/mo free for 12 months on Free tier
  • Strong fit for serverless-anchored AWS customers

Cons

  • AWS-only architecture; multi-cloud teams get less value
  • Pay-per-call pricing compounds at material scale
Free 1M/mo 12moHTTP $1/1M callsLaunched 2015Free 1M calls/mo for 12 months

Best for: AWS-anchored serverless teams running material Lambda workloads wanting native API gateway integration without separate vendor procurement.

Data residency plus on-prem posture
9
Routing latency plus throughput
10
Operator onboarding curve
9
Value
9
Support
9
Try AWS API Gateway
#2

KrakenD

8.3/10Save $1,812/yr

Best stateless aggregation Go-based gateway with single-binary deployment

Try KrakenDSee KrakenD alternatives

Stateless aggregation Go-based gateway with single-binary deployment since 2017.

PlanMonthlyAnnualWhat you get
OSS CommunityFree—Apache 2 Go-based stateless gateway.
Enterprise (self-hosted)CustomCustomPremium plugins with SSO and audit.
Cloud$99.00/mo$1,188.00/yr$0.10 per 1K requests plus $99/mo base.
Enterprise PlusCustomCustomCustom integrations with dedicated CSM.

KrakenD is the stateless aggregation Go-based API gateway for platform engineering teams whose evaluation centers on aggregating multiple backend APIs into single client-facing endpoints with a stateless Go binary. Founded 2017 in Spain and Apache 2 licensed, KrakenD built around the thesis that BFF patterns need a stateless aggregation gateway separate from generic gateways, with Go single-binary operational simplicity.

Four tiers. OSS Community covers Apache 2 Go-based stateless aggregation gateway with single-binary deployment. Enterprise (self-hosted) covers ~$36K+/yr with premium plugins plus analytics plus SAML SSO. Cloud covers $0.10 per 1K requests plus base $99/mo with pay-as-you-go scaling. Enterprise Plus covers custom integrations plus SLA at custom-quoted economics.

The load-bearing wedge is the stateless aggregation specialization. Frontend teams building BFF endpoints that aggregate 5-10 backend microservice calls into single client-facing endpoints get KrakenD's purpose-built aggregation engine without writing custom code; competing generic gateways treat aggregation as a plugin pattern rather than a first-class primitive. The catch is the narrower scope; KrakenD lacks the broader API management features (developer portals, monetization, deep auth) of Kong or Apigee, and teams that need full API management plus aggregation must run KrakenD alongside another gateway.

Pros

  • Stateless aggregation gateway as load-bearing primitive
  • Single Go binary operational simplicity
  • Apache 2 OSS without copyleft concerns
  • Cloud $99/mo plus per-call as cheapest published
  • Strong fit for frontend teams building BFF aggregation endpoints

Cons

  • Narrower scope; lacks API management depth of Kong/Apigee
  • Teams needing full API management plus aggregation must run two gateways
OSS Apache 2Cloud $99/moFounded 2017OSS Community Apache 2 free

Best for: Frontend teams building backend-for-frontend (BFF) aggregation endpoints needing stateless multi-service aggregation as the primary gateway primitive.

Data residency plus on-prem posture
9
Routing latency plus throughput
10
Operator onboarding curve
9
Value
10
Support
8
Try KrakenD
#3

Kong

7.2/10

Best mainstream open-source enterprise API gateway with deepest plugin ecosystem

Try KongSee Kong alternatives

Mainstream open-source enterprise API gateway with the deepest plugin ecosystem since 2015.

PlanMonthlyAnnualWhat you get
Kong OSSFree—Apache 2 self-hosted with NGINX/OpenResty.
Konnect Plus$250.00/mo$3,000.00/yrHosted control plane with multi-region.
Konnect EnterpriseCustomCustomAdvanced security plus OIDC and audit.
Kong MeshFree$0.00/yrService mesh on Kuma with mTLS.

Kong is the mainstream open-source enterprise API gateway for platform engineering teams whose evaluation centers on the deepest plugin ecosystem plus the broader Konnect API platform. Founded 2015 and reaching $1.4B valuation in 2021, Kong built around the thesis that API gateways need an extensible plugin architecture for auth, rate-limiting, transformation, and custom logic.

Four tiers. Kong OSS covers Apache 2 self-hosted with NGINX/OpenResty base and 200+ plugins. Konnect Plus covers $250+/mo entry tier with hosted control plane plus multi-region data planes. Konnect Enterprise covers ~$50K+/yr with advanced security plugins plus OIDC plus RBAC plus audit. Kong Mesh covers service mesh on Kuma with mTLS at custom-quoted economics.

The load-bearing wedge is the 200+ plugin ecosystem plus the OSS-plus-cloud progression. Platform teams running Kong OSS get production-grade routing for free; teams that outgrow self-hosting graduate to Konnect Plus without re-architecting; enterprises with material security plus compliance plus mesh requirements consolidate on Konnect Enterprise plus Kong Mesh. The catch is the OpenResty/NGINX-based architecture; some modern teams prefer Go-based gateways (Tyk, KrakenD) for memory profile and language ecosystem fit, and the plugin architecture means careful plugin selection to avoid performance regressions.

Pros

  • 200+ plugin ecosystem (deepest on the lineup)
  • Apache 2 OSS with self-hosted free path
  • Konnect Plus $250+/mo as cloud-managed step
  • Kong Mesh service mesh on Kuma
  • Strong fit for platform teams wanting OSS-plus-enterprise progression

Cons

  • OpenResty/NGINX-based architecture preferred against by some Go-anchored teams
  • Plugin ecosystem requires careful selection to avoid performance regressions
Kong OSS Apache 2Konnect Plus $250+Founded 2015Kong OSS free Apache 2

Best for: Platform engineering teams wanting the deepest plugin ecosystem with OSS self-host plus optional Konnect cloud progression at scale.

Data residency plus on-prem posture
9
Routing latency plus throughput
10
Operator onboarding curve
8
Value
9
Support
9
Try Kong
#4

Apollo Router (GraphOS)

6.3/10

Best GraphQL Federation-anchored Rust-based router with GraphOS schema registry

Try Apollo Router (GraphOS)See Apollo Router (GraphOS) alternatives

GraphQL Federation-anchored Rust router plus GraphOS since 2022.

PlanMonthlyAnnualWhat you get
Apollo Router OSSFree—Apache 2 Rust-based GraphQL router.
GraphOS ServerlessFree—Free up to 10M ops with schema registry.
GraphOS Cloud Pro$250.00/mo$3,000.00/yr$250/mo with custom domain and SLA.
GraphOS EnterpriseCustomCustomSelf-hosted runtime with SAML SSO.

Apollo Router (GraphOS) is the GraphQL Federation-anchored Rust-based router for teams running material federation workloads whose evaluation centers on Federation 2 support plus the GraphOS schema registry. Launched 2022 as the Rust replacement for Apollo Server's gateway, Apollo Router built around the thesis that GraphQL Federation needs a purpose-built router with Rust runtime performance.

Four tiers. Apollo Router OSS covers Apache 2 Rust-based router with self-hosted free plus Federation 2 support. GraphOS Serverless covers free up to 10M ops/mo with schema registry plus analytics. GraphOS Cloud Pro covers $250/mo plus $0.50 per 1M ops above with custom domain plus higher SLA. GraphOS Enterprise covers self-hosted runtime plus SAML SSO plus audit at custom-quoted economics.

The load-bearing wedge is the GraphQL Federation specialization plus the schema registry. Teams running 10+ federated subgraphs get Apollo Router's purpose-built Federation 2 router plus GraphOS schema registry tracking subgraph evolution and preventing breaking changes; competing generic gateways treat GraphQL as one routing pattern. The catch is the GraphQL-only scope; teams needing REST routing must run Apollo Router plus a separate REST gateway, and GraphOS Cloud Pro at $250/mo crosses Kong Konnect Plus for teams needing both.

Pros

  • Federation 2 specialization unmatched by generic gateways
  • GraphOS schema registry tracks subgraph evolution
  • Rust runtime performance beats Node.js plus NGINX alternatives
  • OSS Apache 2 self-hosted plus GraphOS Serverless free
  • Strong fit for teams running 10+ federated subgraphs

Cons

  • GraphQL-only scope; REST teams need separate gateway
  • GraphOS Cloud Pro $250/mo crosses Kong Konnect Plus
OSS Apache 2GraphOS Serverless freeLaunched 2022Apollo Router OSS plus GraphOS Serverless free

Best for: Platform engineering teams running 10+ federated GraphQL subgraphs needing Federation 2 router plus schema registry plus subgraph analytics.

Data residency plus on-prem posture
9
Routing latency plus throughput
10
Operator onboarding curve
9
Value
9
Support
9
Try Apollo Router (GraphOS)
#5

Zuplo

6.2/10

Best TypeScript programmable edge gateway with edge-deployed worldwide

Try ZuploSee Zuplo alternatives

TypeScript programmable edge gateway with edge-deployed runtime worldwide since 2022.

PlanMonthlyAnnualWhat you get
FreeFree—1M API calls/mo free with TypeScript.
Pro$250.00/mo$3,000.00/yr$250/mo plus per-call beyond included.
Business$1,000.00/mo$12,000.00/yrSAML SSO with multi-region infra.
EnterpriseCustomCustomSelf-hosted with custom integrations.

Zuplo is the TypeScript programmable edge gateway for developer teams whose evaluation centers on writing API gateway logic in TypeScript plus running it on edge networks worldwide. Founded 2022 in Seattle, Zuplo built around the thesis that API gateway configuration should be code (TypeScript) deployed to edge networks (like Cloudflare Workers) rather than YAML configuration on centralized infrastructure.

Four tiers. Free covers 1M API calls/mo free always with TypeScript-based programmable gateway plus edge-deployed worldwide. Pro covers $250/mo plus $0.50 per 1K calls above included with custom domain plus analytics. Business covers ~$1K+/mo with SAML SSO plus advanced auth plus multi-region dedicated infra. Enterprise covers self-hosted option plus custom integrations at custom-quoted economics.

The load-bearing wedge is the TypeScript-as-code primitive plus edge deployment. Developer teams writing API auth logic plus rate-limiting plus transformation in TypeScript get version-controlled gateway configuration in Git alongside application code; the edge deployment delivers low-latency routing globally without dedicated regional infrastructure. The catch is the TypeScript lock-in; teams not anchored to TypeScript find Zuplo's programming model incongruent, and the post-1M-calls/mo pricing at $0.50 per 1K calls compounds quickly at scale (10M calls/mo runs ~$4.5K/mo plus base).

Pros

  • TypeScript-as-code gateway configuration in Git
  • Edge-deployed worldwide for low-latency routing
  • Free 1M calls/mo always (not 12-month limit like AWS)
  • Custom domain plus analytics on Pro
  • Strong fit for TypeScript-anchored teams wanting code-as-config gateway

Cons

  • TypeScript lock-in incongruent for non-TS teams
  • Per-1K-call pricing compounds quickly above 1M/mo free
Free 1M/mo alwaysPro $250/moFounded 2022Free 1M API calls/mo always

Best for: TypeScript-anchored developer teams wanting code-as-config gateway logic deployed to edge networks worldwide for low-latency routing.

Data residency plus on-prem posture
9
Routing latency plus throughput
10
Operator onboarding curve
10
Value
9
Support
8
Try Zuplo
#6

Tyk

5.8/10$4,200/yr more

Best modern Go-based API gateway with GraphQL Federation built in

Try TykSee Tyk alternatives

Modern Go-based gateway with built-in GraphQL Federation since 2014.

PlanMonthlyAnnualWhat you get
Tyk OSSFree—MPL 2 Go-based with GraphQL Federation.
Cloud Edge$600.00/mo$7,200.00/yrHosted gateway with up to 5M requests.
Cloud ProFree$0.00/yrMulti-region with developer portal.
On-prem (Self-Managed)Free$0.00/yrFull self-hosted enterprise with SSO.

Tyk is the modern Go-based API gateway for platform engineering teams whose evaluation centers on the Go runtime profile plus built-in GraphQL Federation without separate Apollo Router deployment. Founded 2014 in London and MPL 2 licensed, Tyk built around the thesis that API gateways should be Go-native for memory efficiency plus that GraphQL Federation should ship as a first-class gateway feature.

Four tiers. Tyk OSS covers MPL 2 self-hosted Go-based gateway with GraphQL Federation built in. Cloud Edge covers $600/mo per region with hosted gateway plus dashboard plus up to 5M requests/mo. Cloud Pro covers multi-region plus portal at custom-quoted economics. On-prem (Self-Managed) covers full self-hosted enterprise with SAML SSO plus audit.

The load-bearing wedge is the Go-runtime plus built-in GraphQL Federation combination. Platform teams that want unified REST plus GraphQL gateway without running Apollo Router alongside Kong get Tyk OSS as one binary handling both; the Go runtime profile beats Kong's NGINX/Lua memory footprint at high VU counts. The catch is the smaller mainstream procurement footprint versus Kong; Tyk's reference base is meaningful but smaller, and the Cloud Edge $600/mo per-region pricing crosses Kong Konnect Plus on absolute cost for single-region deployments.

Pros

  • Go-runtime memory efficiency at high VU counts
  • Built-in GraphQL Federation without separate router
  • MPL 2 OSS without copyleft concerns
  • On-prem self-managed enterprise option
  • Strong fit for teams wanting unified REST plus GraphQL gateway

Cons

  • Smaller mainstream procurement footprint versus Kong
  • Cloud Edge $600/mo per-region above Kong Konnect Plus single-region
Tyk OSS MPL 2Cloud Edge $600Founded 2014Tyk OSS free MPL 2

Best for: Platform engineering teams wanting unified REST plus GraphQL gateway in one Go-runtime binary without running Apollo Router alongside Kong.

Data residency plus on-prem posture
9
Routing latency plus throughput
10
Operator onboarding curve
8
Value
8
Support
8
Try Tyk
#7

Apigee (Google Cloud)

5.7/10$3,000/yr more

Best Google Cloud-bundled API management platform since 2016 acquisition

Try Apigee (Google Cloud)See Apigee (Google Cloud) alternatives

Google Cloud-bundled API management platform since the 2016 acquisition.

PlanMonthlyAnnualWhat you get
Apigee EvalFree—60-day trial with 6M API calls.
Pay-as-you-goFree$0.20/yr$0.20 per 1M calls hosted on GCP.
Subscription Standard$500.00/mo$6,000.00/yrAnnual commit with higher limits.
EnterpriseCustomCustomApigee Hybrid with on-prem option.

Apigee is the Google Cloud-bundled API management platform for enterprises whose evaluation centers on Google Cloud ecosystem fit plus the broader Apigee Edge runtime with developer portals, monetization, and analytics. Founded 2004 and acquired by Google in 2016 for $625M, Apigee built around the thesis that API management is more than gateway routing; enterprises need portals, monetization, and analytics in the same product.

Four tiers. Apigee Eval covers 60-day free trial with up to 6M API calls plus full feature set. Pay-as-you-go covers $0.20 per 1M API calls hosted on Google Cloud with Apigee Edge runtime. Subscription Standard covers ~$500+/mo entry with annual commit pricing plus higher rate limits. Enterprise covers ~$50K+/yr with Apigee Hybrid (on-prem option) plus premium support plus dedicated CSM.

The load-bearing wedge is the broader API management platform plus Google Cloud ecosystem fit. Enterprises running material API monetization (developer portal subscriptions, partner billing, multi-tier API products) get Apigee's portal, monetization, and analytics natively; for organizations on Google Cloud, the Apigee bundle is the procurement-natural pick. The catch is the price; Apigee Subscription Standard starts at $500+/mo and Enterprise crosses $50K+/yr, plus the post-2016 Google ownership shifts roadmap priorities toward GCP integration over standalone Apigee features.

Pros

  • Broader API management platform (portal plus monetization plus analytics)
  • Google Cloud ecosystem fit since 2016 acquisition
  • Pay-as-you-go $0.20 per 1M calls
  • Apigee Hybrid on-prem option on Enterprise
  • Strong fit for enterprises with API monetization plus GCP commitment

Cons

  • Subscription Standard starts at $500+/mo entry pricing
  • Post-2016 Google ownership shifts priorities toward GCP integration
Pay-as-you-go $0.20/1MSubscription $500+Google-acquired 201660-day Apigee Eval free trial

Best for: Enterprises running material API monetization workflows with developer portals plus partner billing, especially organizations on Google Cloud.

Data residency plus on-prem posture
9
Routing latency plus throughput
9
Operator onboarding curve
8
Value
7
Support
9
Try Apigee (Google Cloud)

How we picked

Each pick gets a transparent composite score from price, features, free-tier availability, and editor fit. Pricing flows from our live database, so when a vendor changes prices the score updates here too.

Price 40, features 30, free tier 15, fit 15. KrakenD wins composite at 5.44 with $99/mo Cloud but pinned picks[6] for stateless-aggregation positioning. Kong pinned picks[0] for head-term mainstream brand recognition with deepest plugin ecosystem (200+) since 2015 and the broader Konnect platform with $1.4B valuation despite Konnect Plus $250+/mo typical.

We don't claim "30,000 hours of testing." Our methodology is the formula above plus the editor's published verdict for each pick. Verifiable, auditable, and updated when the underlying data changes.

Why trust Subrupt

We're a subscription tracker first, a buying guide second. Every claim on this page is something you can check.

By use case

Best mainstream open-source enterprise API gateway

Kong

Read the full review →

Try Kong

Best Google Cloud-bundled API management platform

Apigee (Google Cloud)

Read the full review →

Try Apigee (Google Cloud)

Best AWS-bundled pay-per-call API gateway

AWS API Gateway

Read the full review →

Try AWS API Gateway

Best modern Go-based gateway with GraphQL Federation

Tyk

Read the full review →

Try Tyk

Best GraphQL Federation-anchored Rust-based router

Apollo Router (GraphOS)

Read the full review →

Try Apollo Router (GraphOS)

Didn't make the list

Apigee (Google Cloud)

Already in picks (second). Worth flagging the broader API management platform; enterprises running API monetization get portal plus monetization plus analytics native.

AWS API Gateway

Already in picks (third). Worth flagging the HTTP API tier; AWS customers running HTTP APIs get $1/1M instead of $3.50/1M REST, producing meaningful savings at scale.

Apollo Router (GraphOS)

Already in picks (fifth). Worth flagging the GraphOS schema registry; teams running 10+ federated subgraphs get schema-evolution tracking that prevents breaking changes.

KrakenD

Already in picks (seventh). Worth flagging stateless aggregation; frontend teams building BFF endpoints get purpose-built aggregation rather than plugin-based.

How to choose your API Gateways

Seven product shapes compete for one head term

The 'best API gateways' search covers seven distinct shapes. Mainstream OSS enterprise (Kong) targets platform teams wanting deepest plugin ecosystem. Google Cloud-bundled (Apigee) targets enterprises with API monetization plus GCP commitment. AWS-bundled (AWS API Gateway) targets serverless-anchored AWS teams. Modern Go with GraphQL Federation (Tyk) targets teams wanting unified REST plus GraphQL. GraphQL Federation-anchored (Apollo Router) targets teams running 10+ federated subgraphs. TypeScript programmable edge (Zuplo) targets TypeScript teams wanting code-as-config. Stateless aggregation Go (KrakenD) targets BFF aggregation patterns. The honest framework: identify your API call volume, GraphQL vs REST mix, and adjacent-vendor commitments before evaluating.

OSS-self-host vs cloud-hosted vs hyperscaler-bundled is the core decision

The category splits into three procurement shapes. OSS-self-host (Kong OSS, Tyk OSS, Apollo Router OSS, KrakenD OSS) ships free open-source core that platform teams operate on internal infrastructure. Cloud-hosted (Kong Konnect, Tyk Cloud Edge, Apollo GraphOS, Zuplo) ships managed gateway in vendor cloud at $99-$600/mo entry. Hyperscaler-bundled (AWS API Gateway, Apigee on Google Cloud) ships gateway as a native cloud primitive integrated with the rest of the cloud stack. The honest framework: organizations with platform engineering capacity to operate gateways pick OSS-self-host for cost. Organizations without ops capacity pick cloud-hosted for managed convenience. AWS or GCP-anchored organizations pick hyperscaler-bundled for ecosystem fit.

GraphQL Federation reshapes 2026 evaluations for federated subgraph teams

Apollo Router launched 2022 as the Rust-based replacement for Apollo Server's gateway, and by 2026 became the de-facto GraphQL Federation runtime for teams running 10+ federated subgraphs. The implications are material; teams that previously ran Apollo Server Gateway alongside Kong or Tyk for REST routing now run Apollo Router for GraphQL Federation specifically while keeping Kong or Tyk for REST. The honest framework: teams running material GraphQL Federation should evaluate Apollo Router for the federation runtime regardless of REST gateway choice. Teams without GraphQL Federation can ignore Apollo Router. Teams with light GraphQL plus material REST often prefer Tyk or Kong's GraphQL Federation features without running a separate router.

When to skip API gateways and use Cloudflare plus serverless functions

API gateways are not always the right answer. For organizations under 1M API calls/mo with simple HTTP-only APIs hosted on serverless platforms (Cloudflare Workers, Vercel Functions), the platform's built-in routing plus auth plus rate-limiting often suffices; the dedicated API gateway value proposition only materializes when multi-service aggregation, advanced auth, monetization, or developer portals become operational requirements. The honest framework: API gateways fit when monthly call volume exceeds 10M, multi-service aggregation becomes load-bearing, or API monetization plus developer portals become operational. Outside that envelope, serverless platform routing is often the right answer.

Plugin ecosystem depth drives Kong selection at upper-mid scale

Kong's 200+ plugin ecosystem is unmatched in the category and load-bearing for upper-mid market evaluations. Plugins cover authentication (OAuth2, OIDC, JWT, API key, mTLS), rate-limiting (per-consumer, per-route, sliding-window), traffic management (canary, blue-green, request-transformer), observability (Datadog, Prometheus, OpenTelemetry), and security (IP restriction, bot detection, anomaly detection). Competing gateways ship 20-50 plugins or require custom code for similar functionality. The honest framework: organizations with material plugin requirements (5+ plugins active in production) get more value from Kong's ecosystem. Organizations with simple gateway requirements (auth plus rate-limiting only) can use any gateway and the plugin depth is not load-bearing.

Adjacent-vendor consolidation drives 3 of the 7 picks

Three of the seven picks bundle into adjacent vendors or platforms. Apigee bundles into Google Cloud (GCP plus Apigee Edge plus Apigee Hybrid) since the 2016 acquisition. AWS API Gateway bundles into AWS (Lambda, IAM, CloudWatch, all of AWS) natively. Apollo Router bundles into Apollo GraphOS plus the broader Apollo GraphQL ecosystem (Apollo Studio plus Apollo Connectors). The honest framework: pick by adjacent-vendor relationship. GCP customers default to Apigee. AWS customers default to AWS API Gateway. Apollo GraphQL ecosystem customers pick Apollo Router. For organizations without adjacent commitments, Kong plus Tyk plus KrakenD win on standalone fit by language preference and use case.

Frequently asked questions

Are these prices guaranteed not to change?

No. Pricing in this category mostly published-tier (Kong Konnect Plus $250+/mo, Tyk Cloud Edge $600/mo, KrakenD Cloud $99/mo, Zuplo Pro $250/mo, Apollo GraphOS Cloud Pro $250/mo) with pay-per-call (Apigee at $0.20/1M, AWS at $1-$3.50/1M) and custom-quoted enterprise tiers. OSS cores (Kong, Tyk, Apollo Router, KrakenD) free forever. Mid-points cited reflect public sticker pricing as of May 2026.

Does Subrupt earn a commission from any of these picks?

We track which picks have approved affiliate programs in our database, and the FTC disclosure block at the top of every guide names which ones currently have a click-tracking partnership. Affiliate revenue does not change ranking. The composite math runs against the same weights for every pick regardless of partnership; if a higher-paying vendor scores worse, it ranks worse. The picks-array order reflects editorial pinning around brand recognition and audience fit.

Why is Kong ranked first when KrakenD wins composite?

Mainstream recognition for API gateways in 2026 is Kong due to the deepest plugin ecosystem (200+) since 2015 plus the broader Konnect platform. Kong uniquely matches the mainstream-opensource-enterprise tile. KrakenD wins composite math thanks to $99/mo Cloud, but its narrower stateless-aggregation scope makes it a narrower fit for general API gateway needs. If you need BFF aggregation, KrakenD fits better. For GraphQL Federation, Apollo Router fits better.

Should I pick Kong or Apigee for enterprise API management?

Pick by GCP commitment plus monetization needs. Kong wins for organizations wanting open-source plus deepest plugin ecosystem plus self-hosting without GCP commitment. Apigee wins for Google Cloud organizations with material API monetization (developer portals, partner billing) where the broader management platform is load-bearing. Different procurement; Kong optimizes for OSS plus plugin depth, Apigee for GCP plus monetization.

When does AWS API Gateway beat Kong for AWS-anchored teams?

When you are deeply integrated with AWS Lambda plus IAM plus CloudWatch. AWS API Gateway provides native integration with Lambda functions (no separate auth glue), IAM authentication (no separate OAuth setup), and CloudWatch logs (no separate observability glue); standalone Kong requires building these integrations. For AWS-anchored serverless teams, AWS API Gateway is the procurement-natural pick. Kong wins for multi-cloud teams or organizations needing the broader plugin ecosystem.

Should I pick Apollo Router or Tyk for GraphQL Federation?

Pick by federation depth and REST coexistence. Apollo Router wins for teams running 10+ federated subgraphs needing the deepest Federation 2 specialization plus GraphOS schema registry. Tyk wins for teams running unified REST plus GraphQL where running a single Go binary handling both is operationally simpler than Apollo Router plus Kong. Different procurement decisions; Apollo Router optimizes for federation depth, Tyk optimizes for unified gateway operational simplicity.

How do I model the full year-1 API gateway bill?

Year 1 bill includes platform fees plus implementation plus integration. Kong Konnect Plus runs ~$3K/yr platform plus $30K-$100K implementation. Apigee Subscription Standard runs ~$6K/yr plus $50K-$200K implementation. AWS API Gateway at 100M calls/mo (HTTP) runs ~$1.2K/yr platform. Tyk Cloud Edge runs ~$7.2K/yr per region. Apollo GraphOS Cloud Pro runs ~$3K/yr platform. Year-1 budget ranges $0 (OSS self-hosted) to $500K+ (Apigee Enterprise plus implementation).

Why aren't Mulesoft, Azure API Management, or Gravitee in the picks?

Mulesoft is a Salesforce-anchored integration platform overlapping Apigee with Salesforce CRM ecosystem fit. Azure API Management is an Azure-bundled gateway overlapping AWS API Gateway. Gravitee is an OSS API management overlapping Kong with smaller reference base. We focus on platform-shaped picks with broadest coverage; for Salesforce shops, Mulesoft belongs on shortlist; Azure deployments evaluate Azure API Management.

Why aren't WSO2, Gloo Gateway, or Traefik in the picks?

WSO2 is an open-source full API platform overlapping Kong with stronger SOAP plus integration heritage. Gloo Gateway is a Solo.io Envoy-based API gateway overlapping Kong with stronger service mesh integration. Traefik is a Kubernetes ingress controller overlapping Kong with stronger Kubernetes-only focus. These options round out the wedge; for Kubernetes ingress RFPs, Traefik belongs on the shortlist; for Envoy-anchored shops, Gloo belongs alongside Kong.

When does this guide get updated?

We aim to refresh /best/ guides quarterly when there are no major shifts, and immediately when there are. Major triggers: Kong Konnect plus Kong Mesh expansion, Apigee post-Google integration changes, AWS API Gateway pricing shifts, Tyk GraphQL Federation expansion, Apollo Router post-2022 maturity, Zuplo edge expansion, KrakenD Cloud growth, and AI-API-routing launches that materially shift the category.

Subrupt Editorial

The team behind subrupt.com. We track subscriptions, surface cheaper alternatives, and publish buying guides where the score formula is on the page so you can recompute it yourself. We do not claim 30,000 hours of testing. What we claim is live pricing from our database, a transparent composite score, and honest savings math against a category baseline.

Last reviewed

Citations

Affiliate disclosure: Subrupt earns a commission when you switch to a service through our recommendation links. This never changes the price you pay. We only recommend services where there's a real cost or feature advantage for you, and our picks are based on the data on this page, not on which programs pay the most.

Related buying guides

Buying guide

Best Threat Intelligence Platforms of 2026

Read guide

Buying guide

Best VPNs of 2026

Read guide

Buying guide

Best Free VPNs of 2026

Read guide

Track your subscriptions on Subrupt

Add the API Gateways you pay for and see how much you'd save by switching.

Open dashboard

More buying guides

Independent rankings for the subscriptions worth paying for.

See all guides