Skip to main content
Version: 3.6.0

What are models and model aliases?

What is a model?​

A model is what generates text, embeddings or other output when a client calls the Model Gateway. It reaches the platform in one of two ways:

  • Deployed on your infrastructure. A platform administrator deploys an open-weight model on your own GPUs.
  • Connected from an external provider. The platform forwards requests to OpenAI, Azure OpenAI, Anthropic or any other OpenAI-compatible server. The platform stores the provider's credentials.

What you can do with models depends on your role in the tenant. Everyone can use the models shared with them, and Editors and Owners can also connect external models for the tenant. Platform administrators deploy models, decide which tenants may use each one, and see usage across tenants.

A model connected in a tenant is available in that tenant only.

Each model has a type that decides where it can be used: chat, embedding, rerank, transcription, ocr or guardrail. RAG endpoints use embedding, rerank and ocr models, and can use a chat model while indexing. Chat uses chat and transcription models, and a preset agent's output guardrails use guardrail models. See Model capabilities.

What is a model alias?​

A model alias is a stable public name that points at a model. Clients send the alias as the model name in their requests. Later you can point the alias at another model, and those clients keep working without a change.

client ──► "company-chat" (alias) ──► model A
└╌╌► model B (after a repoint)

When a better model arrives, a platform administrator repoints the alias. Clients keep sending the same name and reach the new model, with no code change and no new API keys:

  • Grants follow the alias. An API key granted on an alias keeps working after a repoint, as long as the new model is shared with the key's tenant. A key granted on a model stays with that one model.
  • Sharing is set on the alias, and the model must be shared too. A tenant can call an alias only when both the alias and the model it points at are shared with that tenant. Before repointing, share the new model with the alias's tenants.
  • The ID never changes. An alias's public ID is fixed when it is created.

Aliases belong to the platform and point only at platform-owned models. An alias can also be unlisted: it still works for everyone with access, but it is left out of the model list and the model pickers. You can still grant an API key access to it.

More resources​