A
meetily
93.4
32,765 stars · MIT
Self-Hosted
uptime-kuma leads by 4.5 · narrow
A
93.4
32,765 stars · MIT
B · leads
97.9
94,538 stars · MIT
meetily 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. meetily is written mainly in Rust; uptime-kuma is written mainly in JavaScript. The composite score is 93.4 for meetily and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to meetily's 32,765, a gap of 61,773 (2.89×). Forks are 3,640 for meetily and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 90 versus 100.
Push history: meetily was last pushed on 14 November 2026 (3 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 412 for meetily (0.013 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both meetily 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 meetily (32,765 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: meetily is open source, uptime-kuma is open source.
uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 10 points (90 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against meetily at 93.4, a 4.5 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 | meetily | uptime-kuma |
|---|---|---|
| GitHub stars | 32,765 | 94,538 |
| Forks | 3,640 | 8,860 |
| Open issues | 412 | 852 |
| Adoption | 91 | 100 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.4 | 97.9 |
Privacy-first AI meeting note taker for Windows, macOS and Linux. Free, open source (MIT). On-device Whisper/Parakeet transcription and speaker diarization, no meeting bot. Open-source alternative to Granola, Otter and Fireflies. https://meetily.ai
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 32,765 for meetily. The gap is 61,773 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 14 November 2026 for meetily. That is 3 days apart.
Yes. This catalog marks both meetily and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
meetily 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 meetily scores 93.4. This page calls that a narrow lead for uptime-kuma.