Learn how Gravitee 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.
Last 30 days
Last commit
20 hours agoRepository age
11 yearsLicense
Apache-2.0Repository
gravitee-api-management
Last 30 days
Last commit
6 days agoRepository age
9 yearsVersion
v3.0.3License
Apache-2.0Repository
krakend/krakend-ce
Both Gravitee and Krakend have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Krakend significantly outpaces Gravitee in community adoption with 2,702 stars compared to 469 stars on GitHub. This 5.8x difference suggests Krakend has a much larger and more active community. In terms of developer contributions, Krakend has 505 forks, indicating moderate developer engagement.
Gravitee is growing faster, adding 10 stars in the last 30 days (+2.2%) against adding 14 stars for Krakend (+0.5%). Gravitee is the smaller project of the two, so it is closing the gap rather than extending a lead.
Both projects show recent activity, with Gravitee last updated 20 hours ago and Krakend 6 days ago.
Both tools share common technology foundations, being built with Bash. However, they differ in their additional technology choices: Gravitee uses JavaScript, CSS, Typescript, Python, SCSS, Java, Lua, ASP.NET while Krakend leverages Golang.
Gravitee has been in development longer, starting 11 years ago, compared to Krakend which began 9 years ago. This 2.6-year head start suggests Gravitee may have more mature features and established processes.
Both projects use the Apache-2.0 license, providing identical terms for usage and distribution.
Both tools serve similar use cases in API Infrastructure. However, they also have distinct specializations: Krakend extends into API Integration.