SplitWave compared with Coolify, Dokploy, CapRover and Dokku

Checked against the public documentation of each project on 8 October 2026. These tools change quickly; if something here is out of date or wrong, write to support@split-wave.com and we will correct it.

All five let you deploy applications from Git to your own server. They differ in what they run on, how they handle people and audit, and how they are licensed.

SplitWave Coolify Dokploy CapRover Dokku
Runs on Kubernetes (k3s or your cluster), Helm chart Docker Docker Docker Swarm Docker on one host; optional k3s scheduler
Core licence Elastic License 2.0 (source-available) Open source Open core: SSO, audit logs and custom roles need a paid licence Apache 2.0, paid Pro add-on MIT
Roles for people Admin, devops, developer, viewer, per project (Teams module; the free core has one admin) Teams with owner, admin and member roles Owner, admin, member; custom roles are paid No per-user roles found SSH keys on the server
Two-factor sign-in TOTP, required to buy and for admins Optional Not verified Pro only Not applicable
Audit log Hash-chained, tamper-evident, in the free core Team audit log (since v4.4.0) Paid licence Not found Server logs
Deploy approvals (second person, emergency override) Yes Not found in public docs Not found in public docs Not found in public docs Not found in public docs
Licence check Offline signed key, no calls home Not applicable Validated daily against the vendor servers Not verified Not applicable

Where the others are stronger

  • Coolify and Dokploy have large communities, Docker Compose support, one-click databases and services, and built-in backups. SplitWave today deploys one service per project and has no built-in databases.
  • CapRover has a long track record and a catalogue of one-click apps.
  • Dokku is the simplest and most mature, MIT-licensed, and works well on a single small server with Heroku-style buildpacks.
  • All four are older and more widely used than SplitWave, which released version 0.1.0 in October 2026.

When SplitWave is the better fit

  • You already run Kubernetes (or want k3s) and prefer a platform that works with namespaces and standard permissions rather than the Docker socket.
  • A small team needs a second person to approve production deploys, a tamper-evident audit trail and roles per project.
  • You cannot let a licence server be called from the installation (closed networks): the key is verified offline.
  • You want the interface in Russian or Kazakh as well as English.

If none of these applies, one of the other tools may serve you better, and that is fine.

Sources