Skip to content
DevUtils Online

Self-Hosted

Trilium vs uptime-kuma

uptime-kuma leads by 9.8 · clear

A

Trilium

88.1

38,974 stars · AGPL-3.0

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

uptime-kuma has 94,538 GitHub stars to Trilium's 38,974, a gap of 55,564 (2.43×). Forks are 2,630 for Trilium and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 87 versus 100.

Push history: Trilium 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 574 for Trilium (0.015 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

Trilium 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 Trilium and 96 for uptime-kuma. This is a procurement signal, not legal advice.

In Self-Hosted, both Trilium (38,974 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: Trilium 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, self-hosting. The widest gap is license flexibility at 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).

uptime-kuma finishes ahead at 97.9 against Trilium at 88.1, a 9.8 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.

Trilium versus uptime-kuma metrics
Signal Trilium uptime-kuma
GitHub stars 38,974 94,538
Forks 2,630 8,860
Open issues 574 852
Adoption 92 100
Activity 100 100
Community 87 100
Issue health 84 84
License 52 96
Self-hosting 100 100
Composite 88.1 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 38,974 for Trilium. The gap is 55,564 stars.

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

Both were last pushed on 17 November 2026.

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

Yes. This catalog marks both Trilium 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, Trilium or uptime-kuma?

Trilium 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 Trilium vs uptime-kuma score?

uptime-kuma scores 97.9 and Trilium scores 88.1. This page calls that a clear lead for uptime-kuma.

Related comparisons