Kong

Microservice API Gateway and Platform.

Steady · 61
61/100
Steady

Maintained, but at a slower pace than the leaders in its category.

Maintenance 5/40
Releases 25/25
Community 19/20
Momentum 12/15

Commit activity more than 13% of tracked projects; popularity more than 96%. How this is calculated.

Commits, last 11 months

2025-12: 0 commits 2026-01: 3 commits 2026-02: 2 commits 2026-03: 0 commits 2026-04: 0 commits 2026-05: 4 commits 2026-06: 6 commits 2026-07: 3 commits 2026-08: 1 commits 2026-09: 7 commits 2026-10: 6 commits
2025-12 32 total 2026-10
Stars44k
Latest release3.9.5 · 19 Nov 2026
Repo updated19 Nov 2026
LicenceApache-2.0
Built withLua, Docker, K8S, deb

Is Kong actively maintained?

Kong is under active development: 32 commits landed over the last 11 months, averaging roughly 5 commits a month in the most recent quarter.

The most recent tagged release, 3.9.5, shipped within the last month — a current, installable version exists today.

Kong ranks #9 of 15 in Software Development - API Management, placing it mid-table for maintenance activity.

What Kong actually does

Kong is an API gateway and platform designed to route, manage, and govern traffic between microservices. It typically sits between clients and your backend services to handle cross-cutting concerns like request routing and traffic control.

Best fit: It suits distributed architectures and teams managing multiple microservices that require centralised traffic routing and API governance.

Worth knowing: Managing a distributed API gateway can introduce significant operational complexity and latency overhead, especially when scaling across multiple nodes.

Deployment notes

You can deploy it using Docker, Kubernetes, or native deb packages, and it typically requires a persistent database backend such as PostgreSQL to store configuration.


Kong as a replacement for


Alternatives to Kong

Projects in the same categories, ordered by health score.