> ## Documentation Index
> Fetch the complete documentation index at: https://agno-v2-codex-homepage-20260719-015142.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# AgentOS Templates

> Choose an AgentOS starter or application template to run in your cloud.

Start from an **AgentOS Starter** when you have your own agent use case. Start from an **Application Template** when you want a working agent product to fork and adapt.

Both give you an AgentOS codebase that runs locally and can deploy to infrastructure you control.

## Application Templates

Application Templates are complete agent products with agents, tools, storage, interfaces, evals, and deployment scripts already connected.

<CardGroup cols={2}>
  <Card title="Dash: Data Agent" icon="chart-mixed" href="/deploy/templates/dash/overview">
    For data teams that need SQL answers grounded in schemas, business definitions, validated queries, and prior corrections.
  </Card>

  <Card title="Coda: Code Agent" icon="code-branch" href="/deploy/templates/coda/overview">
    For engineering teams that want code search, PR review, issue triage, and implementation support inside Slack.
  </Card>

  <Card title="Scout: Knowledge Agent" icon="radar" href="/deploy/templates/scout/overview">
    For teams that need an agent to navigate live company context across Slack, Drive, wikis, the web, and MCP sources.
  </Card>

  <Card title="Context: Multiplayer Agent" icon="address-book" href="/deploy/templates/context/overview">
    For founders and operators who want a private CRM and knowledge base that their AI tools can share over MCP.
  </Card>
</CardGroup>

## AgentOS Starters

Starters provide the same AgentOS foundation with deployment scripts for different infrastructure.

| Starter                                      | Best for                                                                             | Deployment shape                                                           |
| -------------------------------------------- | ------------------------------------------------------------------------------------ | -------------------------------------------------------------------------- |
| [Railway](/deploy/templates/railway/deploy)  | Teams that want a managed application and database with minimal infrastructure setup | Railway service and managed PostgreSQL                                     |
| [Docker](/deploy/templates/docker/deploy)    | Teams that want to run AgentOS on infrastructure they control                        | Docker Compose on your host                                                |
| [AWS](/deploy/templates/aws/deploy)          | Teams that already operate in AWS                                                    | ECS Express Mode and RDS PostgreSQL                                        |
| [Fly.io](/deploy/templates/fly/deploy)       | Teams that want a single always-on Fly Machine                                       | Fly Machine and Fly Postgres                                               |
| [Google Cloud](/deploy/templates/gcp/deploy) | Teams that already operate in GCP                                                    | Cloud Run and Cloud SQL                                                    |
| [Kubernetes](/deploy/templates/helm/deploy)  | Platform teams that already run Kubernetes                                           | Helm chart with in-cluster or external PostgreSQL                          |
| [Azure](/deploy/templates/azure/deploy)      | Teams that already operate in Azure                                                  | Container Apps and Flexible Server for PostgreSQL                          |
| [Render](/deploy/templates/render/deploy)    | Teams that want a Blueprint-driven deployment                                        | Render web service and managed PostgreSQL                                  |
| [Modal](/deploy/templates/modal/deploy)      | Python teams that already use Modal                                                  | Always-warm Modal container with Neon or external PostgreSQL with pgvector |

## What's inside every Starter

| Component                   | What it does                                                                                                     |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **AgentOS API**             | Serves agents, teams, and workflows to products, the AgentOS UI, coding agents, and MCP clients.                 |
| **Two platform agents**     | **Agent Builder** creates agents, teams, and workflows. **Platform Manager** inspects and explains the platform. |
| **Two workflows**           | **Deployment Check** reports platform health. **Run Evals** runs the eval suite.                                 |
| **Six coding-agent skills** | Sets up the Starter, creates and extends agents, improves behavior, runs evals, and reviews project drift.       |
| **Eval suite**              | Runs AgentAsJudge and Reliability evals and records results in PostgreSQL.                                       |
| **PostgreSQL**              | Stores sessions, memory, knowledge, traces, and eval results.                                                    |

## Build with your Starter

Every deploy guide includes a prompt for setting up the Starter locally with Claude Code, Codex, or Cursor. The coding agent starts AgentOS, verifies the MCP endpoint, and builds your first agent. The same guide then covers production deployment for that provider.

After AgentOS is running, connect it to the coding agents on your machine:

```bash theme={null}
uvx agno connect
```

See [Build with Coding Agents](/deploy/templates/improve-agents) for the complete development loop.