HeroCtl vs
Dokploy
Modern UX, but tied to a runtime in maintenance mode.
Dokploy is the rising contender in modern self-hosted. Clean UI, multi-server out of the box, idle ~350 MB RAM (lighter than Coolify). But it is built on Docker Swarm — a runtime Docker Inc has not actively invested in since 2019. Every Swarm limitation becomes a Dokploy limitation, with no path to evolve. HeroCtl has its own control plane: freedom to ship features (native service-to-service encryption, built-in metrics) without waiting on a third party. Trade-off: Dokploy has a more polished UI today; HeroCtl has a more robust technical path.
Where Dokploy shines
- Modern, clean UI
- Multi-server via Docker Swarm out of the box
- Light idle (~350 MB RAM)
- Native Docker Compose support
- Growing community
Where it falls short
- Coupled to Docker Swarm (in maintenance mode since 2019)
- Swarm limitations become Dokploy limitations
- Plugin ecosystem still shallow
- Newer, less battle-tested
- Small Brazilian community
Side by side, no fluff
| Criterion | Dokploy | HeroCtl |
|---|---|---|
| Install time | 5 min | 5 min |
| Underlying runtime | Docker Swarm | Own control plane |
| Real high availability | Yes — via Swarm | Yes — replicated control plane |
| Idle RAM | ~350 MB | ~200–400 MB |
| Router + TLS | External integrated router | Built in |
| Service-to-service encryption | Optional encrypted overlay | Native |
| Plugin marketplace | Growing | Free job specs |
| Independent roadmap | Limited by Swarm | Own roadmap |
| Commercial model | OSS | Community free + Business/Enterprise |
| Ideal range | 1–30 servers | 1–500 servers |
Polished UX matters a lot, team is fine with Docker Swarm as a dependency, multi-server out of the box without configuration.
You want a control plane that evolves on its own decisions, native service-to-service encryption, scaling 100+ servers, detailed audit requirements.
Start with Community
Real HA cluster, free forever, no feature gates. Migrating from Dokploy typically takes a small team 4–6 weeks.