Operate
Running Flux in production — server, workers, scheduling, security, observability, multi-tenancy, and maintenance.
Operate is the section for the people who have to keep Flux running in production.
Server covers running and configuring the Flux server, choosing a storage backend, and wiring health checks. Start with Running the server.
Workers covers running workers in production: bootstrap tokens, the SSE-push dispatch model, label-based routing, and observability. Start with Running workers.
Scheduling covers managing scheduled workflows. The scheduler runs as a fleet-wide singleton — on PostgreSQL, multiple server replicas coordinate via advisory locks so schedules never dispatch twice. Start with Schedule management.
Security is the largest sub-group: authentication, OIDC, API keys, RBAC, principals, encryption at rest, and secrets. Start with Authentication overview.
Observability covers events, metrics, tracing, and logs. Start with Events and audit logs.
Multi-tenancy covers namespaces and namespace-scoped permissions for shared deployments. Start with Namespaces.
Maintenance covers backups, upgrades and Alembic-managed schema migrations, execution-history retention, capacity planning, and disaster recovery. Start with Backups and restore.