Skip to main content
MKA1 brings model access, application APIs, and administration into a Kubernetes-based platform. Customers can operate a deployment for their own teams and downstream applications. The console and API expose the same platform capabilities. Developers integrate through SDKs and the CLI; administrators manage access, models, usage, and policies.

Understand the deployment

  • Architecture shows the gateway, services, control planes, and shared state.
  • Requirements describes the platform’s Kubernetes, storage, and capacity needs. Model-serving GPU capacity is sized separately.
  • GitOps and rollback documents deployment controls and their evidence. It is not a cluster installation runbook.

Explore what teams can build

Set up an organization

An organization is a tenant within a deployment. Accepting a cluster invite creates an organization; it does not install the platform.
  1. Follow Organization setup.
  2. Use the Console tour to locate the available tools.
  3. Manage Teams and members and Service accounts.
  4. Activate models in the Model registry.
  5. Give developers appropriately scoped API keys.

Operate and evaluate

Evidence pages describe the environments and methods they tested. Check those details when assessing a different deployment.