Skip to content
DevUtils Online

Self-Hosted

docuseal vs uptime-kuma

uptime-kuma leads by 12.3 · clear

A

docuseal

85.6

19,074 stars · AGPL-3.0

docuseal 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. docuseal is written mainly in Ruby; uptime-kuma is written mainly in JavaScript. The composite score is 85.6 for docuseal and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to docuseal's 19,074, a gap of 75,464 (4.96×). Forks are 1,960 for docuseal and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 83 versus 100.

Push history: docuseal was last pushed on 16 November 2026 (1 day ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 133 for docuseal (0.007 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

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

In Self-Hosted, both docuseal (19,074 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: docuseal 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 docuseal at 85.6, a 12.3 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.

docuseal versus uptime-kuma metrics
Signal docuseal uptime-kuma
GitHub stars 19,074 94,538
Forks 1,960 8,860
Open issues 133 852
Adoption 86 100
Activity 100 100
Community 83 100
Issue health 84 84
License 52 96
Self-hosting 100 100
Composite 85.6 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 19,074 for docuseal. The gap is 75,464 stars.

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

uptime-kuma was pushed more recently: 17 November 2026 versus 16 November 2026 for docuseal. That is 1 days apart.

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

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

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

uptime-kuma scores 97.9 and docuseal scores 85.6. This page calls that a clear lead for uptime-kuma.

Related comparisons