Skip to main content
1

Install the 2501 CLI

Your 2501 account team provides the installer. It places a checksum-verified static binary, sets up the sudo wrapper, and runs a non-interactive init so you finish with a ready-to-edit workspace.No Docker, AWS CLI, or registry login needed on the machine.
2

Edit the two env files

If you use your own PostgreSQL instance, set DATABASE_URL in both files and DIRECT_URL in env.engine for migrations. Confirm the public Command Center URL in both files. The CLI generates and defaults the shared secrets.
3

Prepare the initial tenant and administrator

Before the first deployment, review /etc/2501/tenant.yaml, /etc/2501/organization.yaml, and /etc/2501/admin-user.yaml, created by the installer. Set the initial tenant and organization names and the administrator email. You can set a password or leave it blank for the engine to generate one at boot.Users & Organizations
4

Deploy

The CLI lists published releases newest-first, self-updates to match the version you pick, syncs env files, runs migrations, and brings up the stack.For Kubernetes, add --target kubernetes - it generates a manifest tree you apply with kubectl.
5

Open Command Center

Sign in at your Command Center URL with the admin account. If you left its password blank, read the generated credentials from the engine logs with 2501 infra logs engine.Configure your LLM providers and models, including their credentials and the tenant defaults. Then register your first host, attach an agent, and send a task.

Configuration approaches

Command Center, CSV/JSON import, or the public API - pick the approach that fits your changes.

Deploy

Docker Swarm, Kubernetes, LLM providers, troubleshooting.