A
grocy
85.8
9,689 stars · MIT
Self-Hosted
uptime-kuma leads by 12.1 · clear
A
85.8
9,689 stars · MIT
B · leads
97.9
94,538 stars · MIT
grocy 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. grocy is written mainly in Blade; uptime-kuma is written mainly in JavaScript. The composite score is 85.8 for grocy and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to grocy's 9,689, a gap of 84,849 (9.76×). Forks are 835 for grocy and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 74 versus 100.
Push history: grocy was last pushed on 13 November 2026 (4 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 142 for grocy (0.015 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 92 and 100.
Both grocy 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 grocy (9,689 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: grocy is open source, uptime-kuma is open source.
uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is fork community at 26 points (74 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against grocy at 85.8, a 12.1 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 | grocy | uptime-kuma |
|---|---|---|
| GitHub stars | 9,689 | 94,538 |
| Forks | 835 | 8,860 |
| Open issues | 142 | 852 |
| Adoption | 80 | 100 |
| Activity | 92 | 100 |
| Community | 74 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 85.8 | 97.9 |
ERP beyond your fridge - Grocy is a web-based self-hosted groceries & household management solution for your home
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 9,689 for grocy. The gap is 84,849 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 13 November 2026 for grocy. That is 4 days apart.
Yes. This catalog marks both grocy and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
grocy 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 grocy scores 85.8. This page calls that a clear lead for uptime-kuma.