Teslatlas.
TeslaMate analytics, kept local.
Teslatlas mirrors drives, charges, battery history, and route data from your TeslaMate PostgreSQL database into on-device storage, so trip replay, long-range maps, and everyday browsing stay fast even offline.
Capabilities
TeslaMate history, shaped for the phone.
The app is built around the data you actually come back to: recent activity, battery trends, charging context, and route history that still works once the phone drops off the network.
Overview that stays useful
Recent drives, charges, vehicle status, and all-time context load from the local mirror instead of sending you back to a web dashboard.
Drive history, filtered
Browse by time range and drive length, then drill into individual trips with exact route lines when the source data is present.
Battery and charge history
Track battery snapshots, usable capacity, charging sessions, and energy trends in one place.
Incremental refresh
Daily sync pulls only the missing recent data since the last local update, so routine refresh stays quick.
Long-range maps
Rust builds local route and raster artifacts so six-month and one-year views can open without asking TeslaMate for everything again.
Read-only sync path
Teslatlas reads from TeslaMate and mirrors what it needs locally. There is no write-back path to the source system.
Privacy
Read-only access to your TeslaMate stack.
TeslaMate PostgreSQL stays the source of truth. Teslatlas mirrors the data it needs into local SQLite, keeps browsing fast on device, and does not write back to the source system.
Read-only
TeslaMate access path
Local
SQLite mirror
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 that sit on top of the mirrored data set.
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.