Define the allowed route
Planned routing settings for customer-owned provider accounts and models you are authorized to use. Supported providers and interfaces will be confirmed before launch.
Coming soonBYOK ONLY / IN DEVELOPMENT
An LLM gateway.
Your keys.
Your route.
A routing workspace for developers using their own provider accounts under the provider's permitted terms. We are building explicit route choices, bounded failure handling and request-level visibility.
No provider keys, model requests or payment today.
THE SCOPECustomer-owned provider accounts
THE DECISIONAllowed routes, reviewed outcomes
BEFORE ACCESSSupport, terms and price confirmed
EXPLICIT ROUTESBOUNDED FAILURE HANDLINGREQUEST CONTEXT
FIRST, DEFINE THE CONTRACT
A route needs
more than a URL.
Write the application need, approved provider boundary and failure cases before connecting anything. Our original worksheet is available as a plain-text download.
Get the BYOK review sheet ↗RequestInterface and allowed route
FailureStop condition and outcome
RecordProject, status and data boundary
Illustrative review fields. No real keys or requests.THE PLANNED ROUTING WORKSPACE
BYOK routing with an explicit scope
Review the failure path
Planned retry and fallback controls with explicit limits and visible outcomes. No promise of uninterrupted service or automatic resolution of application errors.
Coming soonKeep usage attributable
Planned project-level request records and usage estimates, with the distinction between estimates and provider billing kept visible.
Coming soonInspect the data boundary
Planned controls for what request information is retained and who can view it. Security, retention and provider-processing details will be reviewed before launch.
Coming soonBEFORE AN INTEGRATION
Before connecting an LLM provider
- Write down your contractDownload the BYOK review sheet and identify the interface, route, failure cases and data boundary you need to verify. Use placeholders only.
- Register developer interestJoin early access without submitting provider keys or connecting an account. No model request is sent by this registration.
- Review the supported scopeProvider support, pricing, usage limits and data-handling details will be published before access opens. The gateway is still in development.
PROPOSED PRICE, SEPARATE USAGE
Early access while the gateway takes shape
Proposed launch price for one developer workspace. Provider model usage is separate, paid through your authorized provider account. Included usage limits will be confirmed before sale. Saving this price records interest only; no charge or subscription starts today.
DEVELOPER QUESTIONS
Questions about the planned LLM gateway
Can I route model requests now?
No gateway endpoint or provider connection is live. The public resource is a planning sheet, and the visuals are concept illustrations.
Which keys would the product use?
The planned scope is customer-owned provider accounts and keys, with processing permitted by the provider. It excludes shared or donated key pools, credential resale and quota aggregation.
Does this include model usage?
No free paid-model usage is promised. Gateway access terms and provider usage charges must be reviewed separately before a future connection. No model calls or payments happen here today.
What is the launch price?
The proposed launch price is US$64 per month for one developer workspace with planned BYOK routing, fallback configuration and request visibility. Provider model usage is separate and paid through your authorized provider account. Included usage limits will be confirmed before launch. Early access and saving this price record interest only; no charge or paid subscription starts today.
Can I send you a key for testing?
Do not submit keys, access tokens, real prompts or private data through this early-access site. Its registration form is not a provider integration.
Is this a security or zero-retention guarantee?
No. The product is being developed, and no end-to-end security or retention guarantee is made. Review the actual processing chain and current provider terms before any future use.
Build a clearer route contract.
Follow the development of a BYOK-only gateway with explicit boundaries.