Admin guide

Provider setup and BYOK

How administrators configure AI providers, bring their own keys, discover available models, and control which models customers can use.

Public draft for dev reviewLast verified 2026-05-21

Derived from the provider admin guide and current provider/model control plane.

Provider configuration

Administrators can configure platform-managed or organisation-scoped providers. Each provider records the provider type, endpoint, status, default role, routing priority, model count, and sync state. Credentials are never part of the public docs surface.

Model discovery

After a provider is configured, Kaidera can discover models, capture their capabilities, and keep the catalog current through scheduled refreshes. Discovery is the foundation for model choice, fallback, pricing governance, and model access groups.

  • Provider discovery finds available models.
  • Catalog enrichment fills capability, modality, pricing, and lifecycle metadata when available.
  • Admin-managed toggles decide which models are visible to customers.
  • Provider sync status shows when the catalog was last refreshed.

Bring your own key

BYOK lets an organisation connect its own provider account where supported. That can give a customer control over provider spend, account-level access, and model availability while still using Kaidera orchestration and governance.

Website context

Connect this guide back to the product story

The technology docs map links this page to the public technology narrative and helps buyers move from a capability overview into the right operating guide.

Open technology docs map →