What happens to each call
- Who is calling. The key on the call identifies the caller: a person’s API key, an agent’s run, or an organization API key. An unknown, revoked or expired key is refused.
- What they may use. The model is checked against the models your organization turned on and the person’s groups. A model name can be an alias your admins defined.
- Who pays. A person’s own Claude plan (where xpander has enabled it), a provider key your organization stored, or xpander’s key billed in credits (Licenses and who pays). Callers never hold a provider key.
- Budgets. The budgets of the organization, the group, the person, the agent and the key are checked before the call leaves (Budgets).
- Fallbacks. When the provider is overloaded or fails, the call is retried, then tried on the alias’s next model.
- The record. One record per call: who, what started it, which client, model and provider, tokens, cost and timings (Usage and logs).
Cloud, Hybrid and Air-Gapped
On Hybrid and Air-Gapped installs, the gateway is part of the chart. Self-hosted explains how to turn it on.
Where each setting lives
All of them are under Platform > AI governance, except the last two, which are in Settings in Xpander Chat. On a self-hosted install, use your own Platform and Xpander Chat addresses.
Get started
- Connect a provider. In Models, choose Add provider and add a key. On xpander cloud you can also start on the models included with xpander.
- Turn on models. Tick the models people may use, and choose Who may use it… to limit them to groups.
- Add an alias (optional), such as
default-codingwith a fallback. - Set budgets and policies in Budgets and Policies.
- Connect a coding tool. In AI models & keys, pick a client under Connect a client and choose Copy setup command (Connect your tools).
- Check it. Your first request shows at the top of Logs.

