Skip to content
DevUtils Online

Self-Hosted

deepwiki-open vs uptime-kuma

uptime-kuma leads by 7.1 · clear

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

uptime-kuma has 94,538 GitHub stars to deepwiki-open's 18,445, a gap of 76,093 (5.13×). Forks are 2,033 for deepwiki-open and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 84 versus 100.

Push history: deepwiki-open was last pushed on 15 November 2026 (2 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 287 for deepwiki-open (0.016 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

Both deepwiki-open 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 deepwiki-open (18,445 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: deepwiki-open 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, license flexibility, self-hosting. The widest gap is fork community at 16 points (84 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).

uptime-kuma finishes ahead at 97.9 against deepwiki-open at 90.8, a 7.1 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.

deepwiki-open versus uptime-kuma metrics
Signal deepwiki-open uptime-kuma
GitHub stars 18,445 94,538
Forks 2,033 8,860
Open issues 287 852
Adoption 86 100
Activity 100 100
Community 84 100
Issue health 84 84
License 96 96
Self-hosting 100 100
Composite 90.8 97.9

deepwiki-open

Open Source DeepWiki: AI-Powered Wiki Generator for GitHub/Gitlab/Bitbucket Repositories. Join the discord: https://discord.gg/gMwThUMeme

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, deepwiki-open or uptime-kuma?

uptime-kuma has more GitHub stars: 94,538 versus 18,445 for deepwiki-open. The gap is 76,093 stars.

Which was updated more recently, deepwiki-open or uptime-kuma?

uptime-kuma was pushed more recently: 17 November 2026 versus 15 November 2026 for deepwiki-open. That is 2 days apart.

Can I self-host both deepwiki-open and uptime-kuma?

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

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

uptime-kuma scores 97.9 and deepwiki-open scores 90.8. This page calls that a clear lead for uptime-kuma.

Related comparisons