# Run It (/docs/tracks/operate)



Ductor is a single Go binary you run inside your own platform, backed by
Postgres and Redis. This track is everything between "it builds" and "it stays
up" — and it is a distinct audience from the other four, not a subset of them.

<Cards>
  <Card title="Deployment" href="/docs/deployment">
    Docker, Dokploy, or Helm/Kubernetes, plus the concerns common to all three.
  </Card>

  <Card title="Operations" href="/docs/operations">
    The operational model, migrations, observability, keys, and day-2 runbooks.
  </Card>

  <Card title="Production guarantees" href="/docs/deployment/production">
    Migrations, the enterprise security posture, resource sizing, and scaling the coordinator.
  </Card>

  <Card title="Hardening" href="/docs/auth/hardening">
    Allowed hosts, credential encryption, session-secret rules, and a locked-down checklist.
  </Card>
</Cards>

## Day-2 [#day-2]

<Cards>
  <Card title="Observability" href="/docs/operations/observability">
    OTel traces, Prometheus metrics, logs, and the Grafana stack.
  </Card>

  <Card title="Health checks & readiness" href="/docs/operations/health-checks">
    What /health and /ready actually verify — and what to alert on.
  </Card>

  <Card title="Queue operations" href="/docs/operations/queue-operations">
    Pause, resume, drain, admission control, and dead-letter replay.
  </Card>

  <Card title="Backup & restore" href="/docs/operations/backup-restore">
    What to back up, how, and how to restore Postgres and cache state.
  </Card>
</Cards>

## Configuration lives in Reference [#configuration-lives-in-reference]

Every `DUCTOR_*` environment variable and YAML key is in the
[configuration reference](/docs/reference/configuration), and every CLI
subcommand in the [CLI reference](/docs/reference/cli).