Apache APISIX vs Krakend
Learn how Apache APISIX and Krakend differ in their key features, development activity, technology
stack and community adoption, so you can decide which of these api infrastructure tools is best for you.
Learn how Apache APISIX and Krakend differ in their key features, development activity, technology stack and community adoption, so you can decide which of these api infrastructure tools is best for you.
Apache APISIX
Last 30 days
Last commit
19 hours agoRepository age
7 yearsVersion
3.18.0License
Apache-2.0Self-hosted
YesRepository
apache/apisix
Krakend
Last 30 days
Last commit
14 hours agoRepository age
9 yearsVersion
v2.13.10License
Apache-2.0Repository
krakend/krakend-ce
Detailed Comparison
Both Apache APISIX and Krakend have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, maturity, licensing and features when making your decision.
Both Apache APISIX and Krakend have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, maturity, licensing and features when making your decision.
Community & Popularity
Apache APISIX significantly outpaces Krakend in community adoption with 17,037 stars compared to 2,668 stars on GitHub. This 6.4x difference suggests Apache APISIX has a much larger and more active community. In terms of developer contributions, Apache APISIX has 2,924 forks, indicating strong developer engagement.
Growth Momentum
Apache APISIX and Krakend are moving at much the same rate, adding 57 stars and adding 7 stars respectively over the last 30 days (+0.3% vs +0.3%). Neither is pulling away from the other on momentum alone.
Development Activity
Both projects show recent activity, with Apache APISIX last updated 19 hours ago and Krakend 14 hours ago.
Project Maturity
Krakend has been in development longer, starting 9 years ago, compared to Apache APISIX which began 7 years ago. This 1.4-year head start suggests Krakend may have more mature features and established processes.
Licensing
Both projects use the Apache-2.0 license, providing identical terms for usage and distribution.
Use Cases & Features
Both tools serve similar use cases in API Infrastructure. However, they also have distinct specializations: Krakend extends into API Integration.
Hosting & Deployment
Apache APISIX provides self-hosting options for complete data control and customization, while Krakend may be primarily cloud-based or require different deployment approaches.
Stellar Hosted – Managed Open Source software hosting in the EU: secure, compliant, fast.