tbphp/gpt-load

Self-hosted AI gateway for multi-channel, multi-credential setups — API keys and subscription accounts, scheduling, failover, request logs and usage. 自托管 AI...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 45 minutes ago
Added to GitGenius on September 10th, 2026
Created on June 6th, 2025
Open Issues & Pull Requests: 15 (+0)
GitHub issues: Enabled
Number of forks: 718
Total Stargazers: 6,681 (+0)
Total Subscribers: 18 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.3 hours
Mean response time: 3.1 days
90th percentile: 5.5 days
Tracked items: 305

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 17% of issues opened in the past year have been closed. Three people close 91% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 13
Closed in 7 days: 10
Avg open age: 3 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 13
Closed in 7 days: 10
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (134)
  • bug (83)
  • question (60)
  • triage (8)
  • documentation (2)
  • duplicate (1)

Detailed Description

gpt-load is a self-hosted AI gateway that routes requests across multiple LLM providers and credential types.

The tool addresses the complexity of managing multiple AI service providers and authentication methods in a single application. Rather than hardcoding API keys or switching between provider SDKs, developers deploy gpt-load as a central gateway that accepts requests and intelligently routes them to configured providers. It supports both API key and subscription account credentials, allowing teams to consolidate access to services like OpenAI, Anthropic, and Google Gemini through a unified interface. The gateway includes request scheduling, failover mechanisms to handle provider outages, and comprehensive logging and usage tracking to monitor consumption across channels.

gpt-load suits teams running self-hosted infrastructure who need to abstract away provider-specific details and manage multiple LLM services without embedding provider logic throughout their codebase. It works well for applications that require high availability across providers, need to track usage per channel or credential, or want to experiment with different LLM backends without code changes. Organizations already committed to self-hosting will find it a natural fit; those preferring managed solutions should evaluate whether the operational overhead justifies the control and cost visibility it provides.

The project shows active development with regular commits addressing bug fixes and feature additions. Pull requests receive timely review and feedback from maintainers. The codebase maintains consistent code quality standards with attention to testing and documentation. Issue discussions demonstrate engagement with user questions and feature requests, with maintainers providing detailed responses and guidance.