A single Coolify panel can manage several servers. CBM handles this natively.
- One agent per server. Run the (same) install command on each Docker host. The enrollment token is per instance, shared across its servers.
- Server captured per resource. On sync, CBM records which Coolify server each resource is deployed on (from the Coolify API).
- Auto-detected agent → server. Each agent reports the resources it can see on its local Docker host; CBM matches them to the known servers and assigns the agent automatically. No manual mapping needed in the common case.
- Routing. Every backup/restore is sent to the agent on the resource's server. If no agent is online there, you get a clear error rather than a backup of the wrong host.
If auto-detection can't decide yet (a brand-new, empty host with nothing recognizable), set the
agent's server by hand on the Agents page (a dropdown), or pass AGENT_SERVER_UUID when
installing the agent.
When an instance spans several servers, the instance page shows one block per server: the agent status there, the install reminder, and that server's own schedule (cron + destination
- retention). Schedule precedence is resource override > server > instance > global.
"Back up Coolify" (the control plane) stays a single action, routed to the main server.
A "local folder" destination is realised on each agent's host. So the same local destination used by two servers is two physical folders, one per host. The destination detail page shows the size broken down per server, and reconciliation / retention / restore for a local backup run on the agent that produced it. For a single shared location, use SSH/SFTP or S3.