Registry

The registry is what a gateway is allowed to reach: model providers, and MCP servers. Nothing routes anywhere until it exists here. An entry is two things — a destination and a credential. Everything else about it follows from the second.

​

The credential decides what upstream sees

The practical consequence: with a shared key, the destination’s audit log says TrustGate and every user inherits the same permissions. With per-user accounts it says who it actually was, and each person reaches exactly what their own account reaches — which is also why someone who has not connected an account yet gets nothing until they do.

​

Instances

One entry can hold several instances: the same provider configured more than once, each with its own credential and name. Two Azure OpenAI deployments, production and staging keys, one MCP server registered against two accounts. Instances are how you separate environments without separating gateways. Routing picks between them, and applications and policies refer to them individually. A server that is a single URL with a single sign-in holds exactly one instance, and a server people install themselves gets its instance created on first install.

​

Built-in and custom

Built-in entries come from the NeuralTrust catalog: the connection details are already known, so you supply a credential — or, for many MCP servers, nobody does, and each person connects their own account the first time they use it. Custom entries are the ones you register yourself: an OpenAI-compatible endpoint, a self-hosted model, an MCP server by URL, or an HTTP API described by an OpenAPI document that TrustGate turns into tools.

​

What the registry does not decide

Two things live elsewhere, and looking for them here is the most common wrong turn:

• Who may use an entry. People are governed by Access; machine callers by the application’s own list of entries.
• What may be done with it. Budgets, allowed models, allowed tools and guardrails are policies.

A registry entry makes something reachable. That is all it does.

​

Failure worth watching

An entry whose stored credentials stopped working keeps its place and keeps receiving traffic. The failure reaches your callers as provider errors rather than as anything that looks like a gateway problem, so a failed connection test is worth acting on when you notice it, not when someone reports it. Deleting an entry is permanent and stops all routing through it immediately.

​

Next