A · leads
act
98.4
72,721 stars · MIT
DevOps
act leads by 11.7 · clear
A · leads
98.4
72,721 stars · MIT
B
86.7
38,560 stars · license n/a
act versus dokploy is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. act is written mainly in Go; dokploy is written mainly in TypeScript. The composite score is 98.4 for act and 86.7 for dokploy.
act has 72,721 GitHub stars to dokploy's 38,560, a gap of 34,161 (1.89×). Forks are 2,126 for act and 3,180 for dokploy. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 95 versus 100.
Push history: act was last pushed on 16 November 2026 (1 day ago), and dokploy was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for act (0.004 per star) and 833 for dokploy (0.022 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
act 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. 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. License scores in this pair are 96 for act and 30 for dokploy. This is a procurement signal, not legal advice.
In DevOps, both act (72,721 stars) and dokploy (38,560 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: act is open source, dokploy is unpriced in this catalog.
The lead is split. act is furthest ahead on license flexibility (96 to 30), while dokploy is furthest ahead on fork community (100 to 95). Choose the dimension a rollout cannot compromise on.
act finishes ahead at 98.4 against dokploy at 86.7, a 11.7 point clear 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 | act | dokploy |
|---|---|---|
| GitHub stars | 72,721 | 38,560 |
| Forks | 2,126 | 3,180 |
| Open issues | 318 | 833 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 96 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 98.4 | 86.7 |
Run your GitHub Actions locally 🚀
Open Source Alternative to Vercel, Netlify and Heroku.
act has more GitHub stars: 72,721 versus 38,560 for dokploy. The gap is 34,161 stars.
dokploy was pushed more recently: 17 November 2026 versus 16 November 2026 for act. That is 1 days apart.
Yes. This catalog marks both act and dokploy as self-hostable. Confirm each project's deploy docs before you plan a migration.
act 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
act scores 98.4 and dokploy scores 86.7. This page calls that a clear lead for act.