> ## 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.

# Init Command

> Initialize your 2501 deployment workspace

The `init` command creates your deployment workspace and auto-generates the required secrets.

<Note>
  You normally do not run `init` by hand. The installer chains a non-interactive `init` automatically, so a fresh install already leaves you with a ready workspace. Run `init` manually only when you want to recreate or relocate a workspace.
</Note>

## What gets created

`init` lays out a workspace containing the two environment files you edit before deploying:

* `env.engine` for the 2501 Engine
* `env.command-center` for the Command Center UI

It also generates and preserves the required secrets (credential keys, API key, auth secret). These are generated once and must never be regenerated after the initial deployment, as that would break existing credentials.

<Note>
  An optional `2501-infra.yml` overlay is written only when your deployment differs from the embedded defaults (for example a Kubernetes target, managed PostgreSQL, a stored registry key, or a pinned image tag). See [Configuration](/0.7/deployment/configuration).
</Note>

## Database mode

The default is an external database: you supply `DATABASE_URL` in `env.engine` and the CLI does not manage a database for you.

Pass `--postgres` to enable a managed PostgreSQL instance instead. Managed PostgreSQL is intended for experiments only, not production.

For all available options, run `2501 infra init -h`.