Teslatlas

Teslatlas.
TeslaMate analytics, kept local.

Teslatlas syncs your TeslaMate data locally via direct PostgreSQL or MyTeslaMate API, powering 3D route replay, battery health predictions, charge diagnostics, parked drain insights, and offline-first analysis after sync.

Download on the App Store

Capabilities

More from your TeslaMate history.

Battery health predictions, charge diagnostics, 3D route replay, parked drain insights where enough local history exists, and prepared maps from local data that never leaves the device.

3D route replay

Interactive maps with flyover views, multiple rendering modes, and full journey analysis across your drive history.

Battery health predictions

Machine learning estimates for battery degradation powered by your local driving and charging history.

Charge diagnostics

Charge doctor findings, cost tracking, efficiency trends, and parked drain detection across your full session history.

PostgreSQL or API

Connect directly to TeslaMate PostgreSQL, or use the MyTeslaMate API with bearer, basic, or Cloudflare Access auth.

Long-range maps

Rust builds local route and raster artifacts so six-month and one-year views open without asking TeslaMate again.

Offline-first analysis

Core analytics and prepared maps work from the local mirror after sync. Export backups, support bundles, or public share files with VIN, time, and location redaction.

Privacy

Read-only access to your TeslaMate stack.

TeslaMate PostgreSQL or MyTeslaMate API stays the source of truth. Sync Health shows source, freshness, row counts, and confidence labels while Teslatlas mirrors into local SQLite without writing back.

We do not collect, store, or share personal data from the app.

Teslatlas connects directly from your device to your own TeslaMate database or to a MyTeslaMate API endpoint that you configure. Vehicle data does not pass through MAGRATHEAN UK LTD. Cached data, computed predictions, preferences, and credentials stay local on your device.

Read-only Access path
Local ML Predictions on device
Offline After sync

Architecture

SwiftUI outside. Rust data work underneath.

SwiftUI renders overview, drives, battery, and trip views across Apple platforms. Rust handles sync, SQLite, route optimisation, and generated map artifacts. TeslaMate PostgreSQL stays the source system.

Swift

iOS and macOS shell

SwiftUI owns onboarding, connection setup, settings, and the analytics screens across iPhone, iPad, and Mac Catalyst.

Rust

Data core

Rust handles PostgreSQL sync, local SQLite writes, route-heavy transforms, and the slower map preparation tasks that do not belong on the UI thread.

SQLite

Local mirror

The local mirror keeps everyday browsing, filters, and offline views responsive once the first sync is done.

PostgreSQL

TeslaMate source

Your TeslaMate PostgreSQL database stays authoritative, with Teslatlas validating connectivity and then reading into a faster local working set.