01Directory in, permission out
One gateway.Full control.
A gateway for models and MCP tools, on infrastructure you own.
Contact via email ›
learn moreA gateway for models and MCP tools, on infrastructure you own.
Cursor, Claude Code, and your own apps call one URL. Keys, audit, and PII stay with you.
Configure the agent. Govern the call. See what it did.
Zentrix is the gateway. ZenSwitch points every coding agent at it in one click, and ZenFuse shows what those agents actually did.
- 01Desktop · Configure
ZenSwitch
One click to point every agent at the gateway.
Sign in once. ZenSwitch writes the base URL, key, model, and MCP servers into each local client, and can put it all back.
- Claude Code, Claude Desktop, Codex, OpenCode, WorkBuddy, Grok
- Preview, apply, roll back — every original file is backed up
- Session hooks for Trae, Qoder, WorkBuddy, CodeBuddy feed ZenFuse
- 02Gateway · Govern
Zentrix
One governed hop for models and MCP tools.
Permission from your org chart, quota down the department tree, tool calls reviewed before the agent runs them.
- OpenAI, Anthropic, and Gemini protocols on one URL
- Vendor keys and MCP credentials never reach the laptop
- Offline pack, runs without public outbound access
- 03Observability · SeePreview
ZenFuse
Every agent session, turn by turn.
Sessions, turns, tool calls, retries, and cost per session — from Claude Code telemetry, IDE hooks, or any OTLP SDK.
- Replay a session and its tool-call chain
- Cost and context pressure per session
- Members see their own sessions; admins see the tenant
From the client to the thing it called.
One URL. A Gateway Key in the client. Upstream credentials, permission, and the audit trail stay on the hop.
Zentrix
One governed hop
Clients
Backends
Business apps
Internal services
Coding agents
Autonomous agents
Model providers
Self-hosted models
MCP servers
Your APIs
Edge
Models
Tools
Control plane
Observability
ZStack RouterModels
Agent GatewayTools
Admin console
Permissions
Traces · metrics
Usage · audit
A request leaves the app
A business app calls /v1/chat/completions with its Gateway Key. Same OpenAI-compatible SDK. Only the base URL changes.
Governed by your org chart, not a list of keys.
Most gateways stop at teams and consumers. Zentrix carries the department and the person on every call — and reads what their agent is about to run.
Where Zentrix is different.
Every gateway here fronts models and MCP tools. The difference is what it knows about your company, and what it does before a call leaves.
- Who can call what
- Zentrix: Org tree synced from DingTalk, Feishu, WeCom, LDAP
- LiteLLM: Orgs · teams · users
- Budgets
- Zentrix: Cascades down departments, checked before the call
- LiteLLM: Per key · user · team · org
- Agent tool calls
- Zentrix: Rebuilt from the stream, reviewed in 11 risk categories, blocked before the agent runs it
- LiteLLM: Prompt and response guardrails
- Admin duties
- Zentrix: System, security, and audit admins exclude each other
- LiteLLM: RBAC
- Audit trail
- Zentrix: Hash-chained, with integrity alerts
- LiteLLM: Audit logs (Enterprise)
- Delivery
- Zentrix: One offline pack, no public outbound
- LiteLLM: Docker · Helm
- Client setup
- Zentrix: ZenSwitch writes each agent's config
- LiteLLM: Manual per client
Compiled from each project's public documentation, September–October 2026. Some capabilities sit in paid tiers. Spot something out of date? Tell us. [email protected]
Running in one command.
The gateway goes on a Linux host. ZenSwitch goes on every laptop that runs an agent.
Server · Linux
Zentrix Gateway
On the download site, choose the Zentrix Gateway edition and the host architecture, then download the installer and the offline package.
Architecture
Put both files in one directory on the host, then run
tar xzf zenova-*-linux-amd64.tar.gz && sudo ./zenova install ./zenova-zentrix_gateway-*-linux-amd64-*.zpkgThe host needs no internet access. The download site also shows this command with the exact file names.
- Linux amd64 (x86-64-v2) or arm64
- 4 cores · 8 GB RAM, 16 GB recommended
Desktop
ZenSwitch
Switch Claude Code, Codex, OpenCode, and more to your Zentrix endpoint, and install the ZenFuse session hooks.
System
Download for macOSzenswitch-macos-arm64.dmg · macOS · Apple silicon
Or in Terminal
curl -fL -o /tmp/zenswitch-macos-arm64.dmg https://cdn.zstack.io/product_downloads/Cloud_suite/AI/zenswitch/latest/zenswitch-macos-arm64.dmg && open /tmp/zenswitch-macos-arm64.dmgZenFuse ships inside Zentrix. Connect agents from the console once the gateway is up.
MCP Services
Open a full-size preview
Ready to see it for yourself
Frequentlyasked questions
Quick answers on keys, MCP, and what stays on your network.
Point Cursor, Claude Code, Codex, WorkBuddy, or an internal service at one gateway URL. From there they can call the models your company has published, and attach MCP tools — DingTalk, GitHub, Confluence, databases, or your own APIs — without putting vendor keys in the client. The gateway is the hop that holds the upstream credentials, checks permission, and writes the record.
Yes. Clients hold a Gateway Key. Model-provider keys and MCP credentials stay pooled on the gateway and are injected only on the way out. Rotate or revoke a key and it takes effect on the next call. The laptop never had the upstream secret, so there is nothing to chase down when someone leaves.
Admins publish tools into the MCP plaza. A user opens a tool, copies the connection JSON, and pastes it into Cursor, Claude Code, Codex, or WorkBuddy. They can run a tool test on the gateway before the client ever sees it. If a tool’s definition changes in a way that affects safety, it can require a new approval instead of updating silently.
It does not have to. Zentrix installs from an offline package. Bring your own models — vLLM, SGLang, Ollama, or any OpenAI-compatible endpoint — and the platform does not need public outbound access. PII detection runs locally, with allow, audit, redact, or block. Unknown matches fail closed.
A raw endpoint has no company permission model, no quota, no PII fence, and no audit of the person who actually made the call. Zentrix sits in front: one base URL, routing and failover, visibility by department, and a log that names the caller. If a client bypasses the gateway, that traffic will not show up in the admin console. That is the point.
Visibility and invocation are separate. A model or tool a user is not allowed to use is not callable. Authorization is checked on every call, down to the individual tool, against the real user — not only the application account. Admins can see who called what, from where, and at what cost. Permission changes take effect without restarting the gateway.