Guides
Security and privacy
Where your provider key lives, what leaves the gateway, and the protections in the control plane.
#Your provider key
The gateway holds your real model-provider key, in an environment variable named by -upstream-key-env. Your agent never needs it. It sends the gateway's own bearer token, or nothing at all on a loopback address.
#The gateway's own access
The gateway refuses to listen on an address other than loopback unless you set -token-env. Bind to 127.0.0.1 for a gateway on the same machine as the agent, and use a token for anything else.
#What leaves the gateway
When you start a gateway with -api-url, it reports metadata for each call: tokens, cache hits, latency, retries, the agent's name and the notes each layer wrote. It does not report prompts or answers.
Two things are opt-in and off by default:
-report-memorysends users' remembered facts so the dashboard can draw the memory graph.-report-memory-quotesalso sends the user's own wording of each fact.
A local trace file (-trace) is yours and stays on your disk.
#The control plane
- Keys are shown once when created and can be revoked at any time. They have a role (admin, viewer, gateway), checked on every request.
- Organisations are separate. Every query is scoped to the organisation of the key that made it.
- Alert webhooks must be
httpsand cannot point at private or internal addresses. - Cross-origin access to the API is limited to the origins you list with
-allow-origin.
#Fail open
The layers are built so a failure in one does not take down the request. A judge that is down or slow never blocks a response, and a failed configuration poll keeps the last good configuration.
#Reporting a problem
If you find a vulnerability, email the founder at the address in the site footer. Please do not open a public issue for it.