# temporal vs teslamateapi

> Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

| | temporal | teslamateapi |
|---|---|---|
| Score | 82/100 ✓ | 46/100 |
| Rank in category | #1 of 1 in Workflow | #3 of 5 in Vehicle Management |
| GitHub stars | 24 057 ✓ | 257 |
| Stars, last 30 days | +779 ✓ | +0 |
| Stable releases, 12 months | 11 ✓ | 6 |
| Latest release | v1.30.8 · 12 Oct 2026 ✓ | v1.25.0 · 7 Jul 2026 |
| Setup | Advanced | Moderate ✓ |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Go | Go |

## Which one should you pick?

temporal scores 82/100 against 46/100 for teslamateapi, so it is the safer default.

temporal ships more often: 11 stable releases in the past year, against 6 for teslamateapi.

If you want the quickest setup, teslamateapi is easier to run; temporal needs more configuration.

temporal is growing faster right now (+779 stars in 30 days).

## Details

- [temporal](https://selfhost.directory/project/temporal) (markdown: https://selfhost.directory/project/temporal.md)
- [teslamateapi](https://selfhost.directory/project/teslamateapi) (markdown: https://selfhost.directory/project/teslamateapi.md)

---
Source: https://selfhost.directory/compare/temporal-vs-teslamateapi