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

# Overview

> Deploy 2501 on your infrastructure

Deploy and configure 2501 on your infrastructure using the `2501 infra` CLI.

## Install the CLI

Install the `2501 infra` CLI on the machine that will run the deployment. Your 2501 account team provides the installer. Installation is a single self-contained step: it places a checksum-verified static binary, sets up a sudo wrapper so `2501 infra deploy` runs privileged without you typing `sudo`, and runs a non-interactive setup so you finish with a ready-to-edit workspace. No Docker, AWS CLI, or registry login is required on the machine to install.

Common installer options: `--target kubernetes` (instead of the default Docker Swarm), `--user` (install under your home directory with no sudo), and `--version <tag>` (pin a specific version).

### Keeping the CLI current

There is no separate update command. The CLI stays in lockstep with the deployed platform version:

* **During deploy.** Interactive `2501 infra deploy` lists published releases newest-first. When you pick a version, the CLI self-updates its own binary to match (checksum-verified, then re-executed) before deploying.
* **CLI only.** To refresh just the binary, re-run the installer. It is idempotent and never touches an existing workspace.

## Quick start

After install, you typically only need to edit two environment files before deploying.

<Steps>
  <Step title="Edit the engine environment">
    Open `/etc/2501/env.engine` and set the human-required values, such as your LLM provider API keys and the external `DATABASE_URL`.
  </Step>

  <Step title="Edit the Command Center environment">
    Open `/etc/2501/env.command-center` and confirm its values.
  </Step>

  <Step title="Deploy">
    ```bash theme={null}
    2501 infra deploy
    ```

    `deploy` syncs your env files to the current version's spec, runs database migrations, and brings up the stack.
  </Step>
</Steps>

<Note>
  Most settings are defaulted for you. A plain Docker Swarm deployment with an external database needs no configuration file at all, just the two environment files above. See [Configuration](/0.7/deployment/configuration) for when an optional `2501-infra.yml` is written.
</Note>

## Getting help

The CLI includes built-in documentation for all commands:

```bash theme={null}
# List all commands
2501 infra -h

# Help for specific commands
2501 infra deploy -h
2501 infra config -h
2501 infra tenant -h
2501 infra org -h
2501 infra user -h
```

## Deployment workflow

1. **Install** the `2501 infra` CLI (setup runs automatically)
2. **Edit** `env.engine` and `env.command-center` with your human-required values
3. **Deploy** with `2501 infra deploy`
4. **Create entities** (the CLI prompts you interactively; skipped with `--yes`)
5. **Access** the Command Center UI

## What's Next

<CardGroup cols={2}>
  <Card title="Init Command" icon="terminal" href="/0.7/deployment/init-command">
    Initialize your deployment
  </Card>

  <Card title="Configuration" icon="gear" href="/0.7/deployment/configuration">
    Overview of configuration files
  </Card>

  <Card title="Docker Swarm" icon="server" href="/0.7/deployment/docker-swarm">
    Deploy to production
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/0.7/deployment/troubleshooting">
    Common issues and solutions
  </Card>
</CardGroup>