A
SurfSense
91.4
16,893 stars · Apache-2.0
Self-Hosted
uptime-kuma leads by 6.5 · narrow
A
91.4
16,893 stars · Apache-2.0
B · leads
97.9
94,538 stars · MIT
SurfSense 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. SurfSense is written mainly in Python; uptime-kuma is written mainly in JavaScript. The composite score is 91.4 for SurfSense and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to SurfSense's 16,893, a gap of 77,645 (5.60×). Forks are 1,613 for SurfSense and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 85 versus 100, and the fork community is 81 versus 100.
Push history: SurfSense 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 64 for SurfSense (0.004 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
SurfSense is listed as Apache-2.0, 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. License scores in this pair are 96 for SurfSense and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both SurfSense (16,893 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: SurfSense is open source, uptime-kuma is open source.
The lead is split. SurfSense is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on fork community (100 to 81). Choose the dimension a rollout cannot compromise on.
uptime-kuma finishes ahead at 97.9 against SurfSense at 91.4, a 6.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 | SurfSense | uptime-kuma |
|---|---|---|
| GitHub stars | 16,893 | 94,538 |
| Forks | 1,613 | 8,860 |
| Open issues | 64 | 852 |
| Adoption | 85 | 100 |
| Activity | 100 | 100 |
| Community | 81 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.4 | 97.9 |
Air-gapped, privacy-focused, open-source NotebookLM alternative. AI agent that researches, transforms, and edits your documents. Join our Discord: https://discord.gg/ejRNvftDp9
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 16,893 for SurfSense. The gap is 77,645 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 14 November 2026 for SurfSense. That is 3 days apart.
Yes. This catalog marks both SurfSense and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
SurfSense is listed as Apache-2.0, 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 SurfSense scores 91.4. This page calls that a narrow lead for uptime-kuma.