StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. API Tools
  4. API Gateway
  5. Apigee vs Kong

Apigee vs Kong

OverviewDecisionsComparisonAlternatives

Overview

Kong
Kong
Stacks671
Followers1.5K
Votes139
GitHub Stars42.1K
Forks5.0K
Apigee
Apigee
Stacks240
Followers691
Votes30

Apigee vs Kong: What are the differences?

Key Differences between Apigee and Kong

Apigee and Kong are two popular API management platforms, but there are key differences between them that set them apart. Here are six specific differences between Apigee and Kong:

  1. Scalability: One of the key differences between Apigee and Kong is their scalability. Apigee is a cloud-based platform that offers high scalability, allowing businesses to easily handle large amounts of traffic and scale their APIs as needed. Kong, on the other hand, is a lightweight, open-source platform that can also handle high loads but may require additional configuration and optimization to achieve the same level of scalability as Apigee.

  2. Deployment Options: Another difference between Apigee and Kong is their deployment options. Apigee is a fully managed platform that runs in the cloud, making it easy to deploy and manage APIs without worrying about infrastructure. Kong, on the other hand, can be deployed in various environments, including on-premises, in the cloud, or in a hybrid environment, giving businesses more flexibility in terms of where they choose to run their APIs.

  3. Pricing Model: Apigee and Kong also differ in their pricing models. Apigee follows a consumption-based pricing model, where businesses pay based on the amount of API traffic processed. Kong, on the other hand, offers both open-source and enterprise versions, with the open-source version being free to use and the enterprise version offering additional features and support at a cost. This difference in pricing models allows businesses to choose the option that best fits their budget and requirements.

  4. Developer Experience: When it comes to developer experience, Apigee and Kong offer different approaches. Apigee provides a comprehensive and user-friendly developer portal, making it easy for developers to discover, test, and consume APIs. Kong, on the other hand, offers a more lightweight developer portal, focusing more on the API gateway capabilities and allowing developers to customize and extend it as needed. This difference in developer experience can be a determining factor for businesses depending on their specific developer needs.

  5. Integration Capabilities: Apigee and Kong also differ in their integration capabilities. Apigee provides a wide range of out-of-the-box integrations with other systems, making it easier for businesses to connect their APIs with existing infrastructure and services. Kong, on the other hand, offers a plugin architecture that allows businesses to extend its functionality and integrate with different systems, giving them more flexibility and control over the integration process.

  6. Support and Community: Finally, the support and community around Apigee and Kong vary. Apigee is a well-established platform with a large and active community, providing businesses with access to a wealth of resources, documentation, and community support. Kong, being an open-source platform, also has a strong community and offers support options through its enterprise version. However, the level of support and resources may differ compared to Apigee's offerings.

In summary, Apigee and Kong differ in terms of scalability, deployment options, pricing model, developer experience, integration capabilities, and support and community. These differences make each platform suitable for different use cases and business needs.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Kong, Apigee

Prateek
Prateek

Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic

Mar 14, 2020

Decided

Istio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn-keyIstio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn key solution with Rancher whereas Kong completely lacks here. Traffic distribution in Istio can be done via canary, a/b, shadowing, HTTP headers, ACL, whitelist whereas in Kong it's limited to canary, ACL, blue-green, proxy caching. Istio has amazing community support which is visible via Github stars or releases when comparing both.

322k views322k
Comments

Detailed Comparison

Kong
Kong
Apigee
Apigee

Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform.

API management, design, analytics, and security are at the heart of modern digital architecture. The Apigee intelligent API platform is a complete solution for moving business to the digital world.

Logging: Log requests and responses to your system over TCP, UDP or to disk; OAuth2.0: Add easily an OAuth2.0 authentication to your APIs; Monitoring: Live monitoring provides key load and performance server metrics; IP-restriction: Whitelist or blacklist IPs that can make requests; Authentication: Manage consumer credentials query string and header tokens; Rate-limiting: Block and throttle requests based on IP or authentication; Transformations: Add, remove or manipulate HTTP params and headers on-the-fly; CORS: Enable cross-origin requests to your APIs that would otherwise be blocked; Anything: Need custom functionality? Extend Kong with your own Lua plugins;
Design, secure, analyze, and scale your APIs with the Apigee Edge API management platform.; Predictive analytics to ensure intelligent and customized interactions.; Connect devices to the Internet, and enable partners and developers to access device functionality and data with APIs.; Protect your apps from cyber threats and bad bots with data-driven enterprise grade API security.
Statistics
GitHub Stars
42.1K
GitHub Stars
-
GitHub Forks
5.0K
GitHub Forks
-
Stacks
671
Stacks
240
Followers
1.5K
Followers
691
Votes
139
Votes
30
Pros & Cons
Pros
  • 37
    Easy to maintain
  • 32
    Easy to install
  • 26
    Flexible
  • 21
    Great performance
  • 7
    Api blueprint
Pros
  • 12
    Highly scalable and secure API Management Platform
  • 6
    Quick jumpstart
  • 6
    Good documentation
  • 3
    Easy to use
  • 3
    Fast and adjustable caching
Cons
  • 11
    Expensive
  • 1
    Doesn't support hybrid natively
Integrations
Cassandra
Cassandra
Docker
Docker
Prometheus
Prometheus
Kubernetes
Kubernetes
PostgreSQL
PostgreSQL
NGINX
NGINX
Vagrant
Vagrant
No integrations available

What are some alternatives to Kong, Apigee?

Postman

Postman

It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide.

Paw

Paw

Paw is a full-featured and beautifully designed Mac app that makes interaction with REST services delightful. Either you are an API maker or consumer, Paw helps you build HTTP requests, inspect the server's response and even generate client code.

Karate DSL

Karate DSL

Combines API test-automation, mocks and performance-testing into a single, unified framework. The BDD syntax popularized by Cucumber is language-neutral, and easy for even non-programmers. Besides powerful JSON & XML assertions, you can run tests in parallel for speed - which is critical for HTTP API testing.

Appwrite

Appwrite

Appwrite's open-source platform lets you add Auth, DBs, Functions and Storage to your product and build any application at any scale, own your data, and use your preferred coding languages and tools.

Runscope

Runscope

Keep tabs on all aspects of your API's performance with uptime monitoring, integration testing, logging and real-time monitoring.

Amazon API Gateway

Amazon API Gateway

Amazon API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, authorization and access control, monitoring, and API version management.

Insomnia REST Client

Insomnia REST Client

Insomnia is a powerful REST API Client with cookie management, environment variables, code generation, and authentication for Mac, Window, and Linux.

RAML

RAML

RESTful API Modeling Language (RAML) makes it easy to manage the whole API lifecycle from design to sharing. It's concise - you only write what you need to define - and reusable. It is machine readable API design that is actually human friendly.

Tyk Cloud

Tyk Cloud

Tyk is a leading Open Source API Gateway and Management Platform, featuring an API gateway, analytics, developer portal and dashboard. We power billions of transactions for thousands of innovative organisations.

Hoppscotch

Hoppscotch

It is a free, fast and beautiful API request builder. It helps you create requests faster, saving precious time on development

Related Comparisons

Postman
Swagger UI

Postman vs Swagger UI

Mapbox
Google Maps

Google Maps vs Mapbox

Mapbox
Leaflet

Leaflet vs Mapbox vs OpenLayers

Twilio SendGrid
Mailgun

Mailgun vs Mandrill vs SendGrid

Runscope
Postman

Paw vs Postman vs Runscope