A
dokploy
84.2
38,560 stars · license n/a
DevOps
Grafana leads by 7.0 · clear
A
84.2
38,560 stars · license n/a
B · leads
91.2
77,962 stars · AGPL-3.0
dokploy versus Grafana is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 84.2 for dokploy and 91.2 for Grafana.
Grafana has 77,962 GitHub stars to dokploy's 38,560, a gap of 39,402 (2.02×). Forks are 3,180 for dokploy and 14,988 for Grafana. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 84 versus 100.
Push history: dokploy was last pushed on 17 November 2026 (0 days ago), and Grafana was last pushed on 17 November 2026 (0 days ago). Open issues stand at 833 for dokploy (0.022 per star) and 3,310 for Grafana (0.042 per star). Issue-health scores are 70 and 70; 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. Grafana is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 30 for dokploy and 52 for Grafana. This is a procurement signal, not legal advice.
In DevOps, both dokploy (38,560 stars) and Grafana (77,962 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, Grafana is freemium.
Grafana is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 22 points (30 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
Grafana finishes ahead at 91.2 against dokploy at 84.2, a 7.0 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 | dokploy | Grafana |
|---|---|---|
| GitHub stars | 38,560 | 77,962 |
| Forks | 3,180 | 14,988 |
| Open issues | 833 | 3,310 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 84 | 100 |
| Issue health | 70 | 70 |
| License | 30 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 84.2 | 91.2 |
Open Source Alternative to Vercel, Netlify and Heroku.
Grafana is the dashboard and visualization layer most teams pair with Prometheus and other metric stores. The open-source server can be self-hosted; Grafana Labs sells a cloud.
Grafana has more GitHub stars: 77,962 versus 38,560 for dokploy. The gap is 39,402 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dokploy and Grafana 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. Grafana is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Grafana scores 91.2 and dokploy scores 84.2. This page calls that a clear lead for Grafana.