Skip to content
DevUtils Online

Self-Hosted

serviette vs uptime-kuma

uptime-kuma leads by 4.7 · narrow

serviette 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. serviette is written mainly in Python; uptime-kuma is written mainly in JavaScript. The composite score is 93.2 for serviette and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to serviette's 58,707, a gap of 35,831 (1.61×). Forks are 1,551 for serviette and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 81 versus 100.

Push history: serviette was last pushed on 10 November 2026 (7 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 6 for serviette (0.000 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.

Both serviette 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 serviette (58,707 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: serviette is open source, uptime-kuma is open source.

The lead is split. serviette 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 serviette at 93.2, a 4.7 point narrow 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.

serviette versus uptime-kuma metrics
Signal serviette uptime-kuma
GitHub stars 58,707 94,538
Forks 1,551 8,860
Open issues 6 852
Adoption 96 100
Activity 92 100
Community 81 100
Issue health 96 84
License 96 96
Self-hosting 100 100
Composite 93.2 97.9

serviette

A no-code RAG server that keeps answers in sync with your documents. Works with 8 vector databases. Built on Pathway.

Project site · GitHub · Full profile

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 58,707 for serviette. The gap is 35,831 stars.

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

uptime-kuma was pushed more recently: 17 November 2026 versus 10 November 2026 for serviette. That is 7 days apart.

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

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

serviette 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.

Who wins the serviette vs uptime-kuma score?

uptime-kuma scores 97.9 and serviette scores 93.2. This page calls that a narrow lead for uptime-kuma.

Related comparisons