A · leads
DevOps-Roadmap
92.3
20,992 stars · Apache-2.0
DevOps
DevOps-Roadmap leads by 3.9 · narrow
A · leads
92.3
20,992 stars · Apache-2.0
B
88.4
38,560 stars · license n/a
DevOps-Roadmap versus dokploy is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. DevOps-Roadmap is written mainly in an unspecified language; dokploy is written mainly in TypeScript. The composite score is 92.3 for DevOps-Roadmap and 88.4 for dokploy.
dokploy has 38,560 GitHub stars to DevOps-Roadmap's 20,992, a gap of 17,568 (1.84×). Forks are 3,563 for DevOps-Roadmap and 3,180 for dokploy. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 100 versus 99.
Push history: DevOps-Roadmap was last pushed on 02 November 2026 (15 days ago), and dokploy was last pushed on 17 November 2026 (0 days ago). Open issues stand at 11 for DevOps-Roadmap (0.001 per star) and 833 for dokploy (0.022 per star). Issue-health scores are 96 and 70; activity scores are 78 and 100.
DevOps-Roadmap is listed as Apache-2.0, 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 DevOps-Roadmap and 30 for dokploy. This is a procurement signal, not legal advice.
In DevOps, both DevOps-Roadmap (20,992 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: DevOps-Roadmap is open source, dokploy is unpriced in this catalog.
The lead is split. DevOps-Roadmap is furthest ahead on license flexibility (96 to 30), while dokploy is furthest ahead on recent activity (100 to 78). Choose the dimension a rollout cannot compromise on.
DevOps-Roadmap finishes ahead at 92.3 against dokploy at 88.4, a 3.9 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 | DevOps-Roadmap | dokploy |
|---|---|---|
| GitHub stars | 20,992 | 38,560 |
| Forks | 3,563 | 3,180 |
| Open issues | 11 | 833 |
| Adoption | 94 | 100 |
| Activity | 78 | 100 |
| Community | 100 | 99 |
| Issue health | 96 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 92.3 | 88.4 |
DevOps Roadmap for 2026. with learning resources
Open Source Alternative to Vercel, Netlify and Heroku.
dokploy has more GitHub stars: 38,560 versus 20,992 for DevOps-Roadmap. The gap is 17,568 stars.
dokploy was pushed more recently: 17 November 2026 versus 02 November 2026 for DevOps-Roadmap. That is 15 days apart.
Yes. This catalog marks both DevOps-Roadmap and dokploy as self-hostable. Confirm each project's deploy docs before you plan a migration.
DevOps-Roadmap is listed as Apache-2.0, 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.
DevOps-Roadmap scores 92.3 and dokploy scores 88.4. This page calls that a narrow lead for DevOps-Roadmap.