Skip to content
DevUtils Online

Self-Hosted

siyuan vs uptime-kuma

uptime-kuma leads by 7.7 · clear

A

siyuan

90.2

47,269 stars · AGPL-3.0

siyuan 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. siyuan is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 90.2 for siyuan and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to siyuan's 47,269, a gap of 47,269 (2.00×). Forks are 3,122 for siyuan and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 88 versus 100.

Push history: siyuan 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 5 for siyuan (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.

siyuan is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for siyuan and 96 for uptime-kuma. This is a procurement signal, not legal advice.

In Self-Hosted, both siyuan (47,269 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: siyuan is open source, uptime-kuma is open source.

The lead is split. siyuan is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.

uptime-kuma finishes ahead at 97.9 against siyuan at 90.2, a 7.7 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

siyuan versus uptime-kuma metrics
Signal siyuan uptime-kuma
GitHub stars 47,269 94,538
Forks 3,122 8,860
Open issues 5 852
Adoption 94 100
Activity 100 100
Community 88 100
Issue health 96 84
License 52 96
Self-hosting 100 100
Composite 90.2 97.9

siyuan

An open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, siyuan or uptime-kuma?

uptime-kuma has more GitHub stars: 94,538 versus 47,269 for siyuan. The gap is 47,269 stars.

Which was updated more recently, siyuan or uptime-kuma?

Both were last pushed on 17 November 2026.

Can I self-host both siyuan and uptime-kuma?

Yes. This catalog marks both siyuan and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, siyuan or uptime-kuma?

siyuan is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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.

Who wins the siyuan vs uptime-kuma score?

uptime-kuma scores 97.9 and siyuan scores 90.2. This page calls that a clear lead for uptime-kuma.

Related comparisons