Feature · Custody
Shipped · self-hostedYour credentials never reach the agent.
Most governance products ask you to route your API keys through their cloud. SynOI's gateway resolves the credential at call time and hands it to the provider, never to the agent. Self-hosted, it never touches SynOI infrastructure at all.
What it does
Keys are forwarded, never persisted.
Your provider key (Anthropic, OpenAI, or any other) is read from the request, forwarded to the provider, and dropped. It is not written to a SynOI database at any point in that path.
That is an architectural fact you can inspect in the code and in your own network traffic, not a policy promise you have to take on faith.
How it works
Self-hosted is the default, not an add-on.
The gateway runs on your infrastructure: your machine, your Docker host, your VPC. Governance decisions and receipt signing happen locally. Nothing about custody depends on SynOI's continued uptime or business decisions.
A competitor asking you to route keys through their console is asking you to trust their custody. SynOI is built so you never have to. That is one half of custody. The other half is below, and it is the half that does the enforcing.
The other half
The agent does not hold the action credential. Your gateway does.
Model keys are forwarded and dropped, as above. Credentials that take actions in other systems, a payment provider, a CRM, a database, work the opposite way, and deliberately so. You store one in a Profile, and the gateway resolves it inside the call itself and never hands it to the agent.
That is what makes the gate hard to route around. A guard the agent can decline to call is a request. An action the agent cannot perform without a key it does not have is a boundary. Conformance tests pin the property: the credential is absent from the action result, from the signed receipt, and from the adapter.
Both halves of this page are true at once because the gateway is yours. Running self-hosted, that credential sits on your infrastructure, not on ours. SynOI the company holds nothing either way.
Be honest about the boundary
Where this does not apply.
This holds for brokered capabilities, where the gateway holds a credential the agent genuinely lacks. It does not hold for a wrapper around something the agent can already do on its own, such as running a local shell command. And it stops holding the moment an integrator also hands the agent the raw provider key.
Storing a credential in a Profile is opt-in. Nothing is collected by default.
Status
Shipped, self-hosted. Hosted mode is not the production default.
The self-hosted, edge-run path is what is live in production today. A hosted convenience mode exists as a direction, not as the shipped norm, and copy on this site should never imply otherwise.
Folded in from the former catalog
- Gateway custody
- BYO keys
- KMS/VPC self-host path
Keep your keys where they already are.
One environment variable points your traffic at a gateway you run. Your keys stay on your box the whole time.