Proposal: Integrate Sablier Traefik Plugin with Dokploy #5094

Context

I’d like to discuss the possibility of integrating the Sablier Traefik Plugin with Dokploy to enable automatic scaling of idle containers and improve resource efficiency for deployed applications.

Sablier can pause services when they are inactive and wake them when traffic arrives. Since Dokploy already uses Traefik for routing, the Traefik plugin looks like a natural fit.

Why this could be useful

• Reduce CPU and memory consumption for inactive applications.
• Make it practical to run more services on smaller servers.
• Automatically wake applications when a request comes in.
• Provide a simple way for Dokploy users to opt into scale-to-zero behavior.
• Leverage the existing Traefik infrastructure instead of introducing another proxy layer.

Possible integration

A potential implementation could expose Sablier configuration through Dokploy, allowing users to configure options such as:

• Which services should be managed by Sablier.
• Idle timeout before a service is stopped.
• Wake-up behavior when requests arrive.
• Default Sablier settings at the server/project/service level.

The Traefik middleware/plugin could then handle the request path while Sablier manages the container lifecycle.

Questions

1. Would the Dokploy maintainers be interested in supporting this integration?
2. Is there an existing architecture or extension point in Dokploy that would make this possible?
3. Would this be better implemented as a native Dokploy feature, a community integration, or a plugin?
4. Are there any concerns around Traefik configuration, service discovery, or container lifecycle management that should be considered?

I’d be interested in hearing whether this is something worth pursuing and, if so, discussing the best approach for implementing it.