How Talaiz works
One outbound tunnel, one control point, and a tamper-evident record of every call.
The connector dials out — nothing listens
Inside your network you run a single small binary called the connector. It opens an outbound-only WebSocket to the Talaiz gateway and supervises your local MCP servers. There is no inbound listener, no open port, and no firewall change — so there is no new attack surface.
Deny by default
The connector advertises the servers and tools it can reach. The gateway starts from a blank policy: nothing is allowed. You add rules per agent and per tool — allow, require approval, cap the rate — and the same policy engine runs on both the gateway and the connector, so one mistake cannot open a path.
The decision pipeline
Every call an agent makes flows through the same checks, in order:
- Authenticate the agent with its API key.
- Authorize the specific tool against policy.
- Rate-limit and enforce the plan quota.
- Approval — block until a human approves, when the rule demands it.
- Redact sensitive fields before the result reaches the agent or the log.
Every call on the record
Each executed call writes exactly one audit event — who, what, when, with which arguments, and what came back. Events are sealed into a SHA-256 hash chain, so the log is tamper-evident: truncating or editing it breaks verification, and a failed write fails the call closed rather than let an unaudited action succeed.
One binary
The gateway ships as a single Go binary with a server-rendered UI — no Node, no build step, no client framework. Self-host it in minutes, or use the managed cloud.