Your own lanes.Your own rules.
A dedicated RouterLane deployment for your organization: all four tiers including Smart+, a console that shows every agent session, filters that enforce your policy on the way in and out, and the retention you choose.
| Included | |
|---|---|
| Deployment | Dedicated, with its own console |
| Tiers | Fast, Normal, Smart and Smart+ |
| Limits | Set to your traffic |
| Console | Transcripts, ask the data, summaries, analytics |
| Policy | Content filters that log or block |
| Retention | Yours to set, transcripts on or off |
| Budgets | Plans, keys and caps per team |
A dedicated deployment
Your own instance of the router and its console. Your traffic, transcripts and settings stay in it.
Smart+
Whole jobs on a copy of the repository: setup, explore, build, tests and an independent QA review, then one patch. A spend ceiling on every job.
Content filters
Yes or no rules over prompts, replies, reasoning, tool calls and tool results. Regex rules judge locally in microseconds; classifier rules ask a small model.
Retention you set
Transcripts on or off, raw parameters on or off, and how long bodies are kept. After the window, bodies are deleted; tokens, timing, model and decision stay.
Plans and budgets per team
Each team gets a client with its own plan and keys: tiers, requests per minute, concurrency, monthly token and spend caps, and per-tier prices.
Answers about your traffic
Ask the data across chosen users and sessions and get answers that cite turns. Session summaries keep a running account of every session.
Data handling.Written down.
What is stored, for how long, and who can reach it, in one place.
- Keys are stored as SHA-256 hashes. The raw key is shown once.
- Credentials are stripped from every logged header.
- Transcripts follow your retention window; request metadata stays for billing.
- Identical requests are answered from a 10-minute cache held in memory, never written to disk.
- Smart+ jobs run as a separate account that cannot read the service's code, database or credentials. Workspaces are deleted after 48 hours.
- A blocked input is never forwarded to a model.
How it starts.In three steps.
Tell us the shape
Which agents and SDKs your teams run, roughly how much traffic, and what your policy needs filters for.
We set the lanes
Plans per team, limits, prices, filters and retention, set in your deployment's console.
Your teams switch
Two environment variables per client. The tier names in their configs never change.
Your own lanes.Your own console.
Keys are issued on request. Tell us what you are building and which clients you use, and we will send a key by email.