tidoly vs Dokploy
Summary. Dokploy runs your Compose files on Docker Swarm. tidoly installs catalog apps with their database, sign-in and domain configured.
Dokploy
An open-source PaaS on Docker Swarm with Traefik. Its strength is Docker Compose: if your stack is already described in a compose file, Dokploy runs it close to as-is, on one node or several. The UI is modern and the footprint is small.
tidoly
A commercial platform on Kubernetes (k3s). Catalog entries declare what they need — database, sign-in, domain, other services — as typed bindings the platform fulfils.
The difference
Not Swarm versus Kubernetes. The question is who owns the connections.
With Dokploy, your compose file owns them. You wrote the environment variables and you maintain them. With tidoly, the catalog entry declares a dependency and the platform fulfils it: credentials are issued and injected, callback URLs are set, dependents are updated on change.
Both are valid. The first gives you full control of a description you already have. The second means nobody has to hold that description in their head.
Choose Dokploy if
- You already have compose files and want them to keep working
- You need open source and a small footprint
- You deploy your own applications more often than off-the-shelf ones
Choose tidoly if
- Most of what you run is off-the-shelf software your team signs into
- You want single sign-on without configuring each app
- You want Kubernetes underneath without learning it now