A
ProxmoxVE
94.0
30,139 stars · MIT
Self-Hosted
uptime-kuma leads by 3.9 · narrow
A
94.0
30,139 stars · MIT
B · leads
97.9
94,538 stars · MIT
ProxmoxVE versus uptime-kuma is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. ProxmoxVE is written mainly in Shell; uptime-kuma is written mainly in JavaScript. The composite score is 94.0 for ProxmoxVE and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to ProxmoxVE's 30,139, a gap of 64,399 (3.14×). Forks are 2,948 for ProxmoxVE and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 90 versus 100, and the fork community is 88 versus 100.
Push history: ProxmoxVE was last pushed on 17 November 2026 (0 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 11 for ProxmoxVE (0.000 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both ProxmoxVE and uptime-kuma are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Self-Hosted, both ProxmoxVE (30,139 stars) and uptime-kuma (94,538 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: ProxmoxVE is open source, uptime-kuma is open source.
The lead is split. ProxmoxVE is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on fork community (100 to 88). Choose the dimension a rollout cannot compromise on.
uptime-kuma finishes ahead at 97.9 against ProxmoxVE at 94.0, 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 | ProxmoxVE | uptime-kuma |
|---|---|---|
| GitHub stars | 30,139 | 94,538 |
| Forks | 2,948 | 8,860 |
| Open issues | 11 | 852 |
| Adoption | 90 | 100 |
| Activity | 100 | 100 |
| Community | 88 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.0 | 97.9 |
Proxmox VE Helper-Scripts (Community Edition)
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 30,139 for ProxmoxVE. The gap is 64,399 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both ProxmoxVE and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
ProxmoxVE 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. uptime-kuma 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.
uptime-kuma scores 97.9 and ProxmoxVE scores 94.0. This page calls that a narrow lead for uptime-kuma.