A
documenso
85.9
15,803 stars · AGPL-3.0
Self-Hosted
uptime-kuma leads by 12.0 · clear
A
85.9
15,803 stars · AGPL-3.0
B · leads
97.9
94,538 stars · MIT
documenso 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. documenso is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 85.9 for documenso and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to documenso's 15,803, a gap of 78,735 (5.98×). Forks are 3,493 for documenso and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 90 versus 100.
Push history: documenso 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 276 for documenso (0.017 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
documenso 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 documenso and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both documenso (15,803 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: documenso 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 documenso at 85.9, a 12.0 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | documenso | uptime-kuma |
|---|---|---|
| GitHub stars | 15,803 | 94,538 |
| Forks | 3,493 | 8,860 |
| Open issues | 276 | 852 |
| Adoption | 84 | 100 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 84 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 85.9 | 97.9 |
The Open Source DocuSign Alternative.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 15,803 for documenso. The gap is 78,735 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both documenso and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
documenso 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.
uptime-kuma scores 97.9 and documenso scores 85.9. This page calls that a clear lead for uptime-kuma.