Learn how LLM Gateway and Portkey AI Gateway differ in their key features, development activity, technology stack and community adoption, so you can decide which of these ai gateways is best for you.
Last 30 days
Last commit
Repository age
Version
License
Self-hosted
Repository

Last 30 days
Last commit
Repository age
Version
License
Repository

Both LLM Gateway and Portkey AI Gateway 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.
Portkey AI Gateway significantly outpaces LLM Gateway in community adoption with 12,766 stars compared to 1,556 stars on GitHub. This 8.2x difference suggests Portkey AI Gateway has a much larger and more active community. In terms of developer contributions, Portkey AI Gateway has 1,254 forks, indicating strong developer engagement.
LLM Gateway is growing faster, adding 128 stars in the last 30 days (+9%) against adding 282 stars for Portkey AI Gateway (+2.3%). LLM Gateway is the smaller project of the two, so it is closing the gap rather than extending a lead.
LLM Gateway shows more recent development activity with its last commit 8 hours ago, while Portkey AI Gateway was last updated 3 months ago. This suggests LLM Gateway is being more actively maintained.
Both tools share common technology foundations, being built with JavaScript, CSS, Typescript, JSX, Next.js. However, they differ in their additional technology choices: LLM Gateway uses Bash.
Portkey AI Gateway has been in development longer, starting 3 years ago, compared to LLM Gateway which began 1 year ago. This 1.7-year head start suggests Portkey AI Gateway may have more mature features and established processes.
Both projects use the MIT license, providing identical terms for usage and distribution.
Both tools serve similar use cases in AI Gateways.
LLM Gateway provides self-hosting options for complete data control and customization, while Portkey AI Gateway may be primarily cloud-based or require different deployment approaches.