// the find
Wei-Shaw/sub2api
Sub2API is an open-source relay platform that unifies Claude, OpenAI, Gemini, and Antigravity subscriptions into a single endpoint. It supports account sharing and cost-sharing, with seamless native tool compatibility.
Sub2API is a self-hosted API gateway that pools AI provider subscriptions (Claude, OpenAI/Codex, Gemini, Antigravity) and re-exposes them as a single OpenAI-compatible endpoint. It handles multi-tenant billing, account rotation, sticky sessions, and rate limiting — essentially letting you resell or cost-share subscription quota. The README discloses twice that this likely violates Anthropic's and OpenAI's ToS; that's not a footnote, it's the central risk.
1. Solid Go stack: Ent ORM with code generation gives type-safe queries and schema migrations, Wire handles compile-time DI — both are good choices for something this operationally complex. 2. Sticky session routing is correctly implemented — LLM conversations need to stay on the same upstream account or context breaks, and most quick-and-dirty proxies get this wrong. 3. Security configuration is thoughtful: URL allowlist, response header filtering, circuit breaker on billing errors, and explicit warnings about HTTP in config with clear documentation of the risks. 4. Deployment story is genuinely good — auto-generated secrets, local directory mounts for easy server migration, one-click upgrade from the admin UI.
1. The ToS risk is existential, not advisory: all your pooled upstream accounts can be banned simultaneously the moment a provider detects the pattern. The README's two-paragraph disclaimer doesn't change that your entire user base goes dark at once. 2. Antigravity and native Claude cannot be mixed in the same conversation, and the fix is 'configure groups manually' — that's a leaky abstraction the operator has to manage forever, not a solved problem. 3. Sora integration is listed in config keys but marked 'temporarily unavailable' with no timeline — signals that upstream integrations are fragile when providers change their APIs. 4. Three-service self-hosting requirement (app + Postgres + Redis) with token-level billing sync means your quota accounting breaks silently whenever an upstream provider changes rate limit behavior or pricing structures.