Roadmap and scope
What SubLane supports today and what remains a possible future direction.
Product direction
SubLane focuses on lightweight, self-hosted sharing of subscription accounts within an internal team. The priority is to make account setup, permissions and usage understandable and operable. This roadmap does not promise release dates.
Available today
- Official OpenAI and Chat Completions-compatible API channels with API keys, base URLs, key rotation and existing resource groups.
- One Go process with an embedded web interface, SQLite storage, English and Chinese UI, and theme switching.
- Workspaces with separate subscriptions, resource groups, members, direct pool grants, personal API keys and usage records.
- Subscription import and authorization, encrypted credentials, model discovery and exact model allowlists.
- Account concurrency, durable cooldowns, conversation affinity and Codex subscription quota awareness.
- Resource allowances by share of an internal USD or token budget, or by direct USD and token limits.
- Request diagnostics, member request limits, daily and hourly usage summaries, and management audit records.
- Password changes and recovery, online backups, verification and isolated-directory restore.
- One-use invitation links for member registration in a selected workspace.
- Tagged-release workflow, Linux amd64/arm64 archives and container validation.
Codex, Claude and Antigravity subscription integrations support authorization, imports, model discovery, quota reporting and pool routing. Fresh main quota windows gate Codex and Claude accounts, while Antigravity quota admission and explicit model cooldowns affect only the requested model. Grok quota does not inform admission. Pool/key model dialogs provide local admission diagnostics, with optional model-unavailable and low-quota alerts. Synthetic protocol tests do not replace acceptance with real subscriptions and desktop clients. See native client protocols for Messages and Gemini version boundaries. Deployment resource baselines still need measurement.
Possible later additions
OIDC integration, richer quota reporting, advanced routing and additional native API providers are candidates, not current features. The existing scope needs validation with an internal team before expansion.
Outside the initial scope
Direct LDAP integration, billing and resale workflows, mandatory external databases, PostgreSQL storage and multiple application replicas are not part of this release. See workspaces for the current deployment boundary.