mnfst/llm-gateway

Connect Your Agents And Harnesses With Any Provider 🦚

View on GitHub ↗Jump to charts ↓Open shareable report →

Summary Information

Updated 20 minutes ago
Added to GitGenius on September 9th, 2026
Created on September 27th, 2022
Open Issues & Pull Requests: 108 (+0)
GitHub issues: Enabled
Number of forks: 508
Total Stargazers: 7,513 (+1)
Total Subscribers: 29 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.2 hours
Mean response time: 4.2 days
90th percentile: 8.7 days
Tracked items: 486

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 58% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Only 13% of issues opened in the past year have been closed. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 36
New in 7 days: 4
Closed in 7 days: 2
Avg open age: 87 days
Stale 30+ days: 28
Stale 90+ days: 13

Recent activity

Opened in 7 days: 4
Closed in 7 days: 2
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (86)
  • enhancement (27)
  • UX (18)
  • good first issue (17)
  • Priority: High (16)
  • severity: critical (14)
  • stale (13)
  • Need specifications (9)

Detailed Description

LLM Gateway is a gateway and routing layer that connects AI agents and applications with any language model provider.

The tool solves the problem of managing multiple LLM provider integrations and controlling how requests flow to different models. It acts as a centralized gateway that abstracts away provider-specific details, allowing agents and applications to send requests through a single interface regardless of which underlying provider handles them. The gateway handles routing logic, enabling developers to direct requests to different providers based on configurable rules.

Teams building AI agents should consider this tool if they need to work with multiple LLM providers, track token usage and costs across different models, or want to avoid vendor lock-in by maintaining flexibility in provider selection. It suits projects where observability into LLM usage is important and where the ability to switch or balance load across providers adds value. The tool supports bring-your-own-key deployments, meaning teams can use their own API credentials rather than relying on a managed service.

The project maintains active continuous integration with automated testing on code changes. Code coverage is tracked and monitored as part of the development process. The tool is available as a Docker image for containerized deployment and supports deployment across multiple cloud platforms through provided infrastructure templates.