teslamate
TeslaMate is a self-hosted data logger for Tesla vehicles that records detailed trip, charge, and battery data into a PostgreSQL database and visualizes it via Grafana dashboards. It publishes vehicle telemetry to a local MQTT broker for integration with home automation systems, and runs on modest hardware like Raspberry Pi.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | teslamate-org/teslamate |
| Owner | teslamate-org |
| Primary language | Elixir |
| License | AGPL-3.0 — OSI-approved |
| Stars | 8.7k |
| Forks | 982 |
| Open issues | 68 |
| Latest release | v4.0.1 (2026-06-14) |
| Last updated | 2026-07-06 |
| Source | https://github.com/teslamate-org/teslamate |
What teslamate is
Built in Elixir with Phoenix LiveView, TeslaMate polls the Tesla API to capture high-precision drive metrics, charge cycles, and state changes while minimizing vampire drain. Data flows through PostgreSQL, with Grafana providing analysis dashboards and MQTT enabling downstream integrations (Home Assistant, Node-Red, Telegram).
Get the teslamate source
Clone the repository and explore it locally.
git clone https://github.com/teslamate-org/teslamate.gitcd teslamate# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires PostgreSQL database, Docker runtime (or bare-metal Elixir/Erlang setup), and Grafana for visualization; typical small-to-medium deployment ~5 min init once infrastructure is in place.
- Tesla API authentication uses OAuth; credentials are stored locally. No built-in encryption at rest for the database—rely on host-level security and network isolation.
- Data retention is unlimited by default; monitor PostgreSQL disk usage on long-running instances, especially if logging multiple vehicles over years.
- Contributor License Agreement (CLA) required for code contributions; enforced via cla-assistant to preserve AGPLv3 compliance.
- OpenSSF Best Practices badge and CI/CD coverage badges indicate quality gates, but review CI workflows and test coverage depth before critical deployments.
When to avoid it — and what to weigh
- Closed-source or commercial derivative products — AGPLv3 requires any modified version or network service built on TeslaMate to release source code under the same license. Closed-source wrappers or SaaS reselling are not permitted.
- Low-bandwidth or offline-first environments — Requires persistent internet to reach Tesla API, local PostgreSQL + Grafana infrastructure, and optional MQTT broker. Not suitable for offline-only or severely constrained networks.
- Minimal operational overhead desired — Self-hosted setup demands database administration, Docker/container knowledge, Grafana configuration, and ongoing security patching. Requires technical operator involvement.
- Dependency on Tesla API stability guarantees — Relies on undocumented Tesla API; changes or deprecation by Tesla could break data collection without notice. No contractual SLA or API compatibility guarantee.
License & commercial use
Licensed under GNU Affero General Public License v3.0 (AGPLv3). Copyleft license requiring derivative works, modifications, or network-service deployments to release source code under the same license. Trademark policy and Contributor License Agreement (CLA) in place to enforce long-term open-source commitment.
Commercial use for personal or internal fleet monitoring is permitted under AGPLv3. However, any commercial product or SaaS that modifies, wraps, or offers TeslaMate as a service must release its full source code under AGPLv3—no closed-source commercial derivatives allowed. Consult legal counsel before integrating into a revenue-generating offering.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
TeslaMate handles Tesla OAuth credentials and stores them locally in the database; no built-in encryption at rest. Credentials are never sent to third parties, but database security depends on host isolation, network ACLs, and PostgreSQL hardening. AGPLv3 copyleft encourages community code review and reduces risk of abandoned malware-prone forks. CAUTION: README warns of deceptive forks and unofficial apps using the TeslaMate name; use only official GitHub repository. No penetration testing or third-party security audit results published.
Alternatives to consider
TeslaFi
Commercial SaaS for Tesla data logging; proprietary, cloud-hosted, closed-source. No privacy control, but minimal operational overhead.
tesla-apiscraper (deprecated/community)
Lightweight alternative for basic Tesla API polling; smaller feature set, less active maintenance. TeslaMate offers richer dashboards and MQTT integration.
Tesla Owners App (official)
Native Tesla mobile app provides real-time vehicle status but no historical data logging, offline dashboards, or home automation integration. TeslaMate fills this gap for power users.
Build on teslamate with DEV.co software developers
If you require privacy-first, self-hosted vehicle telemetry with rich analytics and home automation integration, review TeslaMate's AGPLv3 license terms, operational requirements, and official documentation at docs.teslamate.org before deployment.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
teslamate FAQ
Can I use TeslaMate for a commercial SaaS or subscription service?
Does TeslaMate work offline or without Tesla API access?
What database backends are supported?
How do I ensure my Tesla credentials are secure?
Software development & web development with DEV.co
From first prototype to production, DEV.co delivers software development services around tools like teslamate. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source devops and beyond.
Evaluate TeslaMate for Your Tesla Fleet Monitoring Needs
If you require privacy-first, self-hosted vehicle telemetry with rich analytics and home automation integration, review TeslaMate's AGPLv3 license terms, operational requirements, and official documentation at docs.teslamate.org before deployment.