Torii is the gate your team walks through to reach your models. Seiki is the governance plane behind it — routing, budgets, audit. Both stand on Gateway, our Rust library for fallback chains and budget control.
The split execution plane is not a setting buried in preferences — it is written on the response, every time.
Local models, local context, nothing leaves the machine. Marked as such on every answer.
Routed, logged and budgeted through your own deployment — in the region you chose.
Torii is what your team opens in the morning. Seiki is where you go when you need to know why — and to change it.
The gate your team walks through.
Everything a member needs and nothing they don’t. Ask a model, keep a library, try things in the playground — and always see where the answer actually ran.
The sanctuary behind it.
The quiet room where the rules are kept. Every request, every provider, every fallback chain and every budget — set once, cascading down your org, without standing over anyone’s shoulder.
Order your models once — primary, then the next, then the local one. Gateway walks the chain when a provider stalls, and Seiki shows you how often it had to.
Bring your own keys for every provider and router. Strategos holds the credentials; your apps hold one address.
Register MCP servers — stdio on the desktop, http for shared ones — and allow-list tools per role and space.
Scoped keys turn the same gateway into an endpoint your own services can call, with usage attributed back to a team.
Org, department, team, person — your real structure. Permissions follow it, and so do spend caps, cascading downward.
Local models run on the machine in front of you. When the gateway is unreachable, work continues and syncs later.
Both clients run on your own infrastructure. There is no Sensei HQ account, no telemetry back to us, and no copy of your traffic anywhere we can read it. You hold the provider keys; you choose the region; you can export or delete the whole audit log whenever you like.
Gateway is our Rust library for talking to model providers: fallback chains, budget control, and one interface across every vendor you use. Torii and Seiki are what it looks like with a face on it — but the library stands alone, and you can build your own client on it.
Visit Gateway →Tell us how your organization works and we will tell you honestly whether the gate fits yet.
hi@sensei-hq.com