> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mka1.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Platform overview

> Understand what MKA1 deploys and how to evaluate and administer the platform.

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](/docs/architecture/overview) shows the gateway, services, control planes, and shared state.
* [Requirements](/docs/architecture/requirements) describes the platform’s Kubernetes, storage, and capacity needs. Model-serving GPU capacity is sized separately.
* [GitOps and rollback](/docs/gitops-atomic-rollback) documents deployment controls and their evidence. It is not a cluster installation runbook.

## Explore what teams can build

| Capability                                | Start here                                                         |
| ----------------------------------------- | ------------------------------------------------------------------ |
| Text, conversations, and streaming        | [Text generation](/docs/generate-a-response)                       |
| Documents, images, and audio              | [Multimodal input](/docs/multimodal-input), [Speech](/docs/speech) |
| Retrieval over customer documents         | [Files and retrieval](/docs/files-and-vector-stores)               |
| Reusable agents, memory, and integrations | [Agents](/docs/managing-agents)                                    |
| Model-quality measurement                 | [Evals](/docs/evals)                                               |
| Training and model hosting                | [Compute](/docs/compute)                                           |

## 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](/docs/organization-setup).
2. Use the [Console tour](/docs/console-tour) to locate the available tools.
3. Manage [Teams and members](/docs/teams-and-members) and [Service accounts](/docs/service-accounts).
4. Activate models in the [Model registry](/docs/model-registry).
5. Give developers appropriately scoped [API keys](/docs/authentication).

## Operate and evaluate

* Configure [Auto routing](/docs/auto-routing), [Budgets](/docs/budgets), and [Rate limits](/docs/rate-limiting).
* Inspect [Usage and auditing](/docs/usage-auditing).
* Review [Resource permissions](/docs/authorization) and [Tenant isolation](/docs/authentication-deep-dive).
* Review [Data encryption](/docs/data-encryption), [HSM-backed keys and TLS 1.3](/docs/hsm-tls-validation), and [Signed artifacts](/docs/signed-artifacts).
* Evaluate the published [latency](/docs/streaming-output-latency), [retrieval](/docs/evaluating-text-stores), and [GraphRAG](/docs/graphrag) results against your own workload.

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