Run It

Deploy, migrate, monitor, secure, and recover a Ductor instance — the day-2 track.

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.

Deployment

Docker, Dokploy, or Helm/Kubernetes, plus the concerns common to all three.

Operations

The operational model, migrations, observability, keys, and day-2 runbooks.

Production guarantees

Migrations, the enterprise security posture, resource sizing, and scaling the coordinator.

Hardening

Allowed hosts, credential encryption, session-secret rules, and a locked-down checklist.

Day-2

Observability

OTel traces, Prometheus metrics, logs, and the Grafana stack.

Health checks & readiness

What /health and /ready actually verify — and what to alert on.

Queue operations

Pause, resume, drain, admission control, and dead-letter replay.

Backup & restore

What to back up, how, and how to restore Postgres and cache state.

Configuration lives in Reference

Every DUCTOR_* environment variable and YAML key is in the configuration reference, and every CLI subcommand in the CLI reference.