A
teslamate
82.4
9,281 stars · AGPL-3.0
Self-Hosted
uptime-kuma leads by 15.5 · decisive
A
82.4
9,281 stars · AGPL-3.0
B · leads
97.9
94,538 stars · MIT
teslamate 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. teslamate is written mainly in Elixir; uptime-kuma is written mainly in JavaScript. The composite score is 82.4 for teslamate and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to teslamate's 9,281, a gap of 85,257 (10.19×). Forks are 1,041 for teslamate and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 76 versus 100.
Push history: teslamate 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 69 for teslamate (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.
teslamate 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 teslamate and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both teslamate (9,281 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: teslamate 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 teslamate at 82.4, a 15.5 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 | teslamate | uptime-kuma |
|---|---|---|
| GitHub stars | 9,281 | 94,538 |
| Forks | 1,041 | 8,860 |
| Open issues | 69 | 852 |
| Adoption | 80 | 100 |
| Activity | 100 | 100 |
| Community | 76 | 100 |
| Issue health | 84 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 82.4 | 97.9 |
A self-hosted data logger for your Tesla 🚘 [main maintainer=@JakobLichterfeld]
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 9,281 for teslamate. The gap is 85,257 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both teslamate and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
teslamate 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 teslamate scores 82.4. This page calls that a decisive lead for uptime-kuma.