An intelligent Claude API proxy with load balancing across multiple accounts, real-time analytics, and multi-provider support.
better-ccflare is an advanced proxy server for the Claude API that intelligently distributes requests across multiple accounts to avoid rate limits. It provides full visibility into every request, response, and rate limit status, making it essential for developers and teams who rely heavily on Claude's API.
Developers and teams who heavily use Claude's API and need to manage multiple accounts, avoid rate limits, and gain operational visibility. This includes those using Claude Pro/Team subscriptions, API keys, or multiple AI providers like AWS Bedrock, Vertex AI, or OpenRouter.
Developers choose better-ccflare for its intelligent load balancing that prevents rate limit errors, its extensive multi-provider support, and its comprehensive real-time analytics dashboard. It offers production-ready features like automatic failover, OAuth token health monitoring, and minimal performance overhead (<10ms).
The ultimate CC proxy
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically distributes requests across multiple Claude accounts with session-based tracking and auto-fallback to prevent rate limit errors, as detailed in the load balancing features.
Supports Claude OAuth, AWS Bedrock, Vertex AI, OpenRouter, and other providers with universal API format conversion, enabling seamless integration across AI services.
Provides a web dashboard with token usage, latency, and cost tracking per request, including batch processing and advanced filtering for operational visibility.
Includes automatic failover, configurable retry logic, SQLite/PostgreSQL persistence, and security hardening for reliable deployments in high-throughput environments.
Claims <10ms overhead with lazy loading and request deduplication, ensuring low latency for API proxying without significant impact.
Setting up HTTPS requires manual certificate management or a reverse proxy like Traefik, with self-signed certificates needing system-level trust adjustments, which can be error-prone.
Windows installation has known npm bugs causing path errors, and macOS binaries are not notarized, requiring manual commands to bypass Gatekeeper.
Users must handle SQLite or PostgreSQL databases, with potential integrity issues that require manual repair using CLI tools, adding maintenance complexity.
Managing multiple accounts, providers, and environment variables (e.g., for OAuth vs API key auth) can be overwhelming for users with simpler needs.