A
automatisch
65.6
14,025 stars · license n/a
Self-Hosted
uptime-kuma leads by 32.3 · decisive
A
65.6
14,025 stars · license n/a
B · leads
97.9
94,538 stars · MIT
automatisch 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. Both projects are written mainly in JavaScript. The composite score is 65.6 for automatisch and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to automatisch's 14,025, a gap of 80,513 (6.74×). Forks are 1,064 for automatisch and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 83 versus 100, and the fork community is 77 versus 100.
Push history: automatisch was last pushed on 11 February 2026 (278 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 293 for automatisch (0.021 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 70 and 84; activity scores are 36 and 100.
automatisch is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for automatisch and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both automatisch (14,025 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: automatisch is unpriced in this catalog, uptime-kuma is open source.
uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: self-hosting. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against automatisch at 65.6, a 32.3 point decisive 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 | automatisch | uptime-kuma |
|---|---|---|
| GitHub stars | 14,025 | 94,538 |
| Forks | 1,064 | 8,860 |
| Open issues | 293 | 852 |
| Adoption | 83 | 100 |
| Activity | 36 | 100 |
| Community | 77 | 100 |
| Issue health | 70 | 84 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 65.6 | 97.9 |
The open source Zapier alternative. Build workflow automation without spending time and money.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 14,025 for automatisch. The gap is 80,513 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 11 February 2026 for automatisch. That is 278 days apart.
Yes. This catalog marks both automatisch and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
automatisch is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 automatisch scores 65.6. This page calls that a decisive lead for uptime-kuma.