Managed model gateway
Proliferate's managed gateway route — central keys, per-user virtual keys, and how budgets apply.
A gateway is the path an agent's model calls take to a provider. This page is about Proliferate's managed gateway, which members enable per agent.
Running your own is a self-hosted deployment task, not an admin setting. See Bring your own gateway.
| Who | Members enable the managed gateway per agent; admins configure org budgets and caps |
| Applies to | Every agent session |
| Requires | Gateway access on the org plan for the managed gateway; a self-hosted add-on for your own gateway |
| Affects | A user (their gateway usage) and the organization (budgets you configure) |
Proliferate's managed gateway
Turn the gateway on for an agent and it reaches current models with no key to paste or rotate.
- Proliferate holds central provider keys, so no one on the team needs their own.
- Each account gets a per-user virtual key, so usage is attributable to the person who spent it inside a shared organization.
- Provider secrets are not sent to a machine or a runtime; only the scoped virtual key is.
- Eligible accounts may receive a free signup credit to try it, depending on configuration and a linked GitHub identity.
Info:
Budgets and LLM caps apply to managed-gateway usage; see Usage & limits.
They are controls to configure, not an airtight org-wide cutoff. A personal enrollment can route around the organization's selection, and enforcement of that case is not yet verified.
Bring your own gateway
See Model gateway.