A
dokploy
88.6
38,560 stars · license n/a
DevOps
opensre leads by 6.1 · narrow
A
88.6
38,560 stars · license n/a
B · leads
94.7
12,838 stars · Apache-2.0
dokploy versus opensre 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; opensre is written mainly in Python. The composite score is 88.6 for dokploy and 94.7 for opensre.
dokploy has 38,560 GitHub stars to opensre's 12,838, a gap of 25,722 (3.00×). Forks are 3,180 for dokploy and 1,884 for opensre. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 94.
Push history: dokploy was last pushed on 17 November 2026 (0 days ago), and opensre was last pushed on 17 November 2026 (0 days ago). Open issues stand at 833 for dokploy (0.022 per star) and 11 for opensre (0.001 per star). Issue-health scores are 70 and 96; 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. opensre 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. License scores in this pair are 30 for dokploy and 96 for opensre. This is a procurement signal, not legal advice.
In DevOps, both dokploy (38,560 stars) and opensre (12,838 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, opensre is open source.
The lead is split. dokploy is furthest ahead on adoption (100 to 90), while opensre is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
opensre finishes ahead at 94.7 against dokploy at 88.6, a 6.1 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 | opensre |
|---|---|---|
| GitHub stars | 38,560 | 12,838 |
| Forks | 3,180 | 1,884 |
| Open issues | 833 | 11 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 94 |
| Issue health | 70 | 96 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 94.7 |
Open Source Alternative to Vercel, Netlify and Heroku.
The open-source agent for CI/CD reliability.
dokploy has more GitHub stars: 38,560 versus 12,838 for opensre. The gap is 25,722 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dokploy and opensre 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. opensre 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
opensre scores 94.7 and dokploy scores 88.6. This page calls that a narrow lead for opensre.