A
feishin
82.0
10,433 stars · GPL-3.0
Self-Hosted
uptime-kuma leads by 15.9 · decisive
A
82.0
10,433 stars · GPL-3.0
B · leads
97.9
94,538 stars · MIT
feishin 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. feishin is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 82.0 for feishin and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to feishin's 10,433, a gap of 84,105 (9.06×). Forks are 609 for feishin and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 71 versus 100.
Push history: feishin was last pushed on 16 November 2026 (1 day ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 329 for feishin (0.032 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
feishin is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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. License scores in this pair are 64 for feishin and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both feishin (10,433 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: feishin is open source, uptime-kuma is open source.
uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 32 points (64 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against feishin at 82.0, a 15.9 point decisive 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 | feishin | uptime-kuma |
|---|---|---|
| GitHub stars | 10,433 | 94,538 |
| Forks | 609 | 8,860 |
| Open issues | 329 | 852 |
| Adoption | 81 | 100 |
| Activity | 100 | 100 |
| Community | 71 | 100 |
| Issue health | 70 | 84 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 82.0 | 97.9 |
A modern self-hosted music player.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 10,433 for feishin. The gap is 84,105 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 16 November 2026 for feishin. That is 1 days apart.
Yes. This catalog marks both feishin and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
feishin is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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 feishin scores 82.0. This page calls that a decisive lead for uptime-kuma.