Network Management and Security Concerns with Traefik/Dokploy

What problem will this feature address?

Currently, all applications in Dokploy, especially those with a domain exposed through Traefik, are automatically connected to the shared dokploy-network, regardless of their functional relationship. This leads to poor network isolation, making all containers accessible to each other. Such practice increases the risk of lateral movement if one container is compromised and restricts the ability to enforce the principle of least privilege in multi-application or multi-tenant deployments. There is no way to create, assign, or manage custom networks via the Dokploy interface, and all adjustments require manual docker-compose edits.

Describe the solution you'd like

• Introduce network management capabilities directly in the Dokploy interface:
  • Allow users to create custom Docker networks for different projects or purposes.
  • Enable explicit assignment of applications/services to specific networks from the interface, both at deployment and post-deployment.
• Traefik should be permitted to join all necessary application networks to enable routing.
• Applications should by default only connect to their designated networks rather than to dokploy-network, limiting unnecessary cross-container access.
• If an application is assigned a domain and needs to be exposed, only Traefik should bridge it to the required network—applications themselves should not be on the global network unless explicitly required.

Describe alternatives you've considered

• Being able to disconnect or disable the default dokploy-network and add only the networks you choose.
• Having full control over network creation, assignment, and management directly via the interface, rather than relying on manual docker-compose edits.

Additional context

It appears this behavior particularly affects all applications with a domain routed through Traefik, but further clarification from Dokploy maintainers would be helpful. Enhancing network management in Dokploy would align the platform with best practices for Docker container security and multi-tenancy.

Beyond a feature request, for me it's a security issue with the current setup. Applications should be isolated, and we should have as few single points of failure as possible.

Will you send a PR to implement it?

Trying

No files, tests, or entry points are named. Start by tracing the Dokploy interface and deployment paths that configure Docker networks and Traefik routing, including both deployment and post-deployment flows. Done means users can create and assign networks, applications are isolated by default, and Traefik can route without placing every application on the shared network.