Software · head to head
AWS API Gateway vs Kong

AWS API Gateway
Software
Fully managed API gateway service for creating and managing APIs at scale
- From
- Free
- Rated
- -

Kong
Software
Cloud-native API gateway and service connectivity platform
- From
- Free
- Rated
- -
The short version
- Each has a real cost: AWS API Gateway rEST APIs cost $3.50 per million calls against $1.00 for HTTP APIs, so the older and more featureful type is three and a half times dearer; Kong the Plus plan includes 1M API requests a month and charges $200 a month for each additional million
- They diverge on capability: AWS API Gateway covers REST APIs, Kong covers API Gateway.
Where they differ
Only the attributes on which AWS API Gateway and Kong actually diverge.
| Attribute | AWS API Gateway | Kong |
|---|---|---|
| Pricing model | usage-based | open-source |
| Platforms | AWS Cloud | Linux, Docker, Kubernetes |
| Founded | 2006 | 2010 |
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Unknown).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in AWS API Gateway
- REST APIs
- WebSocket APIs
- HTTP APIs
- Lambda
- EC2
- DynamoDB
- CloudWatch
- IAM
Only in Kong
- API Gateway
- Authentication & Authorization
- Rate Limiting
- Kubernetes
- Consul
- Eureka
- PostgreSQL
- Linux support
What people use each for
The jobs each tool is most often brought in to do.
AWS API Gateway
- Fronting Lambda functions with an HTTP endpointnot Kong
- REST and HTTP API management with throttling and keysnot Kong
- WebSocket APIs for real-time clientsnot Kong
- Private APIs reachable only inside a VPCnot Kong
- Publishing a developer portal for API consumersnot Kong
Kong
- Running an API gateway in front of internal and public servicesnot AWS API Gateway
- Publishing and governing APIs through a developer portalnot AWS API Gateway
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
AWS API Gateway
- REST APIs cost $3.50 per million calls against $1.00 for HTTP APIs, so the older and more featureful type is three and a half times dearer
- Data transfer out is charged at $0.09 per GB on top of request pricing
- WebSocket APIs bill connection minutes as well as messages, at $0.25 per million minutes
- Private APIs avoid data transfer charges but incur AWS PrivateLink costs instead
- The developer portal is $125 a month, with additional portal products at $12.50 each
- The free tier lasts 12 months rather than being ongoing
Kong
- The Plus plan includes 1M API requests a month and charges $200 a month for each additional million
- Plus is capped at 10M requests a month, so growth past that forces an Enterprise contract
- Plus limits published APIs to 20 and includes one Developer Portal, with a second at $200 a month
- SSO and audit logging are Enterprise only
- Enterprise pricing is custom and billed annually
Pricing, plan by plan
AWS API Gateway
Free- Free TierFree
- 1M requests per month
- Basic API management
- Pay-as-you-go$3.5/per 1M requests
- Unlimited requests
- HTTP APIs
- REST APIs
Kong
Free- CommunityFree
- Core API gateway
- Community support
- Enterprise$undefined/monthly
- Advanced features
- Priority support
- SLA
Which should you pick?
Choose AWS API Gateway if
- You need rest apis.
- You want to start without paying.
- You work on AWS Cloud.
- You also want websocket apis.
Choose Kong if
- You need api gateway.
- You want to start without paying.
- You work on Linux, Docker, Kubernetes.
- You also want authentication & authorization.
Questions people ask
- Is AWS API Gateway or Kong better?
- Neither clearly leads. AWS API Gateway starts at Free and Kong at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, AWS API Gateway or Kong?
- AWS API Gateway starts at Free and Kong at Free.
- Does AWS API Gateway or Kong run on more platforms?
- AWS API Gateway runs on AWS Cloud. Kong runs on Linux, Docker, Kubernetes.
- Can I use AWS API Gateway for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is AWS API Gateway best used for?
- AWS API Gateway is most often used for fronting lambda functions with an http endpoint, rest and http api management with throttling and keys, websocket apis for real-time clients, private apis reachable only inside a vpc. Of those, fronting lambda functions with an http endpoint and rest and http api management with throttling and keys are not what Kong is typically brought in for.
- What can AWS API Gateway do that Kong cannot?
- AWS API Gateway covers REST APIs, WebSocket APIs, HTTP APIs, Lambda. Kong covers API Gateway, Authentication & Authorization, Rate Limiting, Kubernetes.
Related pages
More on AWS API Gateway
Keep looking
Other head to heads
- AWS API Gateway vs Appwrite
- AWS API Gateway vs Hasura
- AWS API Gateway vs PocketBase
- AWS API Gateway vs Sanity
- AWS API Gateway vs Apigee
- AWS API Gateway vs Bruno
- AWS API Gateway vs KeystoneJS
- AWS API Gateway vs Parse Server
- AWS API Gateway vs Stoplight
- AWS API Gateway vs Strapi
- AWS API Gateway vs Swagger/OpenAPI
- AWS API Gateway vs Thunder Client
- AWS API Gateway vs WSO2 API Manager
- AWS API Gateway vs 3scale
- AWS API Gateway vs Akana
- AWS API Gateway vs Asyncapi
- AWS API Gateway vs Microsoft Azure API Management
- AWS API Gateway vs Backendless
- Kong vs Appwrite
- Kong vs Hasura
- Kong vs PocketBase
- Kong vs Sanity
- Kong vs Apigee
- Kong vs Bruno
- Kong vs KeystoneJS
- Kong vs Parse Server
- Kong vs Stoplight
- Kong vs Strapi
- Kong vs Swagger/OpenAPI
- Kong vs Thunder Client
- Kong vs WSO2 API Manager
- Kong vs 3scale
- Kong vs Akana
- Kong vs Asyncapi
- Kong vs Microsoft Azure API Management
- Kong vs Backendless
