ding113/claude-code-hub

一个现代化的 Claude Code & Codex API 代理服务,提供智能负载均衡、用户管理和使用统计功能。

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 21 minutes ago
Added to GitGenius on September 20th, 2026
Created on October 20th, 2025
Open Issues & Pull Requests: 42 (+0)
GitHub issues: Enabled
Number of forks: 392
Total Stargazers: 3,379 (+0)
Total Subscribers: 4 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 25
New in 7 days: 1
Closed in 7 days: 7
Avg open age: 40 days
Stale 30+ days: 3
Stale 90+ days: 2

Recent activity

Opened in 7 days: 1
Closed in 7 days: 7
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (254)
  • enhancement (171)
  • area:provider (128)
  • stale (126)
  • area:UI (66)
  • question (45)
  • oncall (39)
  • area:core (38)

Detailed Description

Claude Code Hub is an API proxy service that provides intelligent load balancing, user management, and usage statistics for Claude and OpenAI-compatible APIs.

The tool addresses the challenge of managing multiple AI service providers across teams by acting as a unified gateway. It routes requests to Claude and OpenAI-compatible endpoints while distributing load intelligently, tracking usage metrics, and enabling fine-grained operational control. Built on Next.js, Hono, PostgreSQL, and Redis, it centralizes access to multiple AI suppliers through a single integration point.

Teams managing multiple AI API accounts or needing to distribute requests across providers should consider this tool. It suits organizations that require observability into API usage, need to enforce rate limits or quotas per user, and want to abstract away the complexity of managing different API keys and endpoints. The project is particularly relevant for those already using Claude Code or Codex APIs at scale.

The project is undergoing active restructuring, with a rewritten version planned for future release under a different license. During this transition period, development progress on the current Node.js version may be delayed, and community support availability may be affected by the ongoing refactoring work.