gateway

Portkey-AI/gateway

A blazing fast AI Gateway with integrated guardrails. Route to 1,600+ LLMs, 50+ AI Guardrails with 1 fast & friendly API.

Ship status

Gone silent

No push in over 120 days. A quiet repo may also be a finished one.

Last push
May 25, 2026
139 days ago
Ship score
20/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 13,060 → 13,126 (Sep 22 – Oct 6, 2026)
History starts 2026-09-22, the first weekly sample after this repo joined the directory.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
13.2K
Forks
1.3K
Open issues
293
Watchers
64
Primary language
TypeScript
Created
Aug 23, 2023
Owner
Portkey-AI · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 213 startups in the directory ship primarily in TypeScript.

Topics

#ai-gateway#gateway#generative-ai#hacktoberfest#langchain#llm#llm-gateway#llmops#llms#mcp#mcp-client#mcp-gateway#mcp-servers#model-router#openai

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 94%, self-hostable 25%, hosted offering 81%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 2026-09-22, found by the weekly discovery job at confidence 0.91. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: silent — last push 2026-05-25This is the badge for Portkey-AI/gateway, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/Portkey-AI/gateway.svg)](https://ossean.com/Portkey-AI/gateway)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.