Feature · Custody
Shipped · self-hostedYour credentials never leave your machine.
Most governance products ask you to route your API keys through their cloud. SynOI runs where you run it, self-hosted, with your keys held in your custody the whole time.
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.
This is the moat: 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.
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.