A
dokploy
88.6
38,560 stars · license n/a
DevOps
semaphore leads by 1.5 · narrow
A
88.6
38,560 stars · license n/a
B · leads
90.1
14,420 stars · MIT
dokploy versus semaphore is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dokploy is written mainly in TypeScript; semaphore is written mainly in Go. The composite score is 88.6 for dokploy and 90.1 for semaphore.
dokploy has 38,560 GitHub stars to semaphore's 14,420, a gap of 24,140 (2.67×). Forks are 3,180 for dokploy and 1,353 for semaphore. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 89.
Push history: dokploy was last pushed on 17 November 2026 (0 days ago), and semaphore was last pushed on 17 November 2026 (0 days ago). Open issues stand at 833 for dokploy (0.022 per star) and 1,075 for semaphore (0.075 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.
dokploy is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. semaphore is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 30 for dokploy and 96 for semaphore. This is a procurement signal, not legal advice.
In DevOps, both dokploy (38,560 stars) and semaphore (14,420 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: dokploy is unpriced in this catalog, semaphore is open source.
The lead is split. dokploy is furthest ahead on issue health (70 to 52), while semaphore is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
semaphore finishes ahead at 90.1 against dokploy at 88.6, a 1.5 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | dokploy | semaphore |
|---|---|---|
| GitHub stars | 38,560 | 14,420 |
| Forks | 3,180 | 1,353 |
| Open issues | 833 | 1,075 |
| Adoption | 100 | 91 |
| Activity | 100 | 100 |
| Community | 100 | 89 |
| Issue health | 70 | 52 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 90.1 |
Open Source Alternative to Vercel, Netlify and Heroku.
Modern UI and powerful API for Ansible, Terraform/OpenTofu/Terragrunt, PowerShell and other DevOps tools.
dokploy has more GitHub stars: 38,560 versus 14,420 for semaphore. The gap is 24,140 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dokploy and semaphore as self-hostable. Confirm each project's deploy docs before you plan a migration.
dokploy is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. semaphore is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
semaphore scores 90.1 and dokploy scores 88.6. This page calls that a narrow lead for semaphore.