A · leads
serviette
97.4
58,707 stars · MIT
Self-Hosted
serviette leads by 11.2 · clear
A · leads
97.4
58,707 stars · MIT
B
86.2
9,281 stars · AGPL-3.0
serviette versus teslamate is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. serviette is written mainly in Python; teslamate is written mainly in Elixir. The composite score is 97.4 for serviette and 86.2 for teslamate.
serviette has 58,707 GitHub stars to teslamate's 9,281, a gap of 49,426 (6.33×). Forks are 1,551 for serviette and 1,041 for teslamate. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 95.
Push history: serviette was last pushed on 10 November 2026 (7 days ago), and teslamate was last pushed on 17 November 2026 (0 days ago). Open issues stand at 6 for serviette (0.000 per star) and 69 for teslamate (0.007 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.
serviette 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. 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. License scores in this pair are 96 for serviette and 52 for teslamate. This is a procurement signal, not legal advice.
In Self-Hosted, both serviette (58,707 stars) and teslamate (9,281 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: serviette is open source, teslamate is open source.
The lead is split. serviette is furthest ahead on license flexibility (96 to 52), while teslamate is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
serviette finishes ahead at 97.4 against teslamate at 86.2, a 11.2 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 | serviette | teslamate |
|---|---|---|
| GitHub stars | 58,707 | 9,281 |
| Forks | 1,551 | 1,041 |
| Open issues | 6 | 69 |
| Adoption | 100 | 83 |
| Activity | 92 | 100 |
| Community | 100 | 95 |
| Issue health | 96 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 86.2 |
A no-code RAG server that keeps answers in sync with your documents. Works with 8 vector databases. Built on Pathway.
A self-hosted data logger for your Tesla 🚘 [main maintainer=@JakobLichterfeld]
serviette has more GitHub stars: 58,707 versus 9,281 for teslamate. The gap is 49,426 stars.
teslamate was pushed more recently: 17 November 2026 versus 10 November 2026 for serviette. That is 7 days apart.
Yes. This catalog marks both serviette and teslamate as self-hostable. Confirm each project's deploy docs before you plan a migration.
serviette 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
serviette scores 97.4 and teslamate scores 86.2. This page calls that a clear lead for serviette.