Feature Request: Atomic Deployment Groups with Health Checks and Automatic Rollback

[Achder]

Feature Request: Atomic Deployment Groups with Health Checks and Automatic Rollback

Problem

Coolify already supports deploying multiple resources at once using tags and Canvas. However, these deployments are independent.

If I deploy multiple applications together and one fails, the others may already have been updated successfully. This leaves the project in a partially deployed state, potentially with incompatible application versions.

Docker Compose provides dependency ordering and health checks, but doesn't guarantee atomic deployments either.

Proposed Solution

Introduce Deployment Groups that allow multiple Coolify resources to be deployed as a single logical unit, ideally building on the existing Tags or Canvas functionality.

A deployment group should support:

• Grouped deployments: Deploy all resources sharing a tag or belonging to a defined group with one action.
• Health checks: Consider a deployment successful only when all resources pass their health checks.
• Automatic rollback: If any resource fails to deploy or becomes unhealthy, roll back all resources in the group to their previous working versions.
• Deployment dependencies (optional): Allow resources to define startup/deployment order, e.g. database → backend → frontend.

Example

A project contains three independently managed Coolify resources:

• Frontend
• Backend API
• Worker

All three share the tag production-stack.

When deploying the tag:

1. Coolify deploys the new versions of all three resources.
2. Coolify waits for their health checks to pass.
3. If all succeed, the deployment is marked successful.
4. If any fails, Coolify automatically restores the previous versions of all three resources.

Ideally, the previous versions would continue serving traffic until the entire group is healthy, similar to a blue-green deployment.

Why This Would Be Useful

Many applications consist of multiple independently deployed services that need to remain compatible.

Currently, the choices are either:

• Manage resources independently and risk partially successful deployments.
• Combine everything into a single Docker Compose stack, sacrificing independent resource management without actually gaining atomic rollback.
• Build custom deployment orchestration outside Coolify.

Native deployment groups would make Coolify much more useful for multi-service applications while preserving the flexibility of managing resources individually.

Possible Integration with Canvas

Since Canvas already provides a visual representation of related resources and supports bulk deployments, it could become a natural interface for defining deployment groups, dependencies, and failure behavior.

Even a simpler first iteration supporting tag-based group deployments with health checks and coordinated rollback would be a valuable improvement.