Powered by Tessie·Secure by default·Private beta

Secure data,
predictive
charging.

teslaconnectivity is a white-label API layer for Tesla vehicle telemetry — pulled through the Tessie API, restricted by an encrypted OpenVPN tunnel, stored in Microsoft Cloud EU, and exposed to systems you build yourself.

Behavioural modelling and trend analysis turn raw driving and charging data into predictions: when to charge, how much to add, and which tariff window is likely to be cheapest. Access is currently limited while the service remains in private beta.

256-bit
AES-GCM encryption
Tessie
Tesla API integration
14–30d
Learning window
100 max
Private beta cap
01 — CAPABILITIES

A quiet system that learns how you use your car.

0006121824MONTUEWEDTHUFRISATSUNlearned weekday windowweekly rhythm · 7d
01 · Behaviour

Behaviour analysis

Continuous modelling of driving patterns, departure times, daily mileage and charging habits. Your car's rhythm, learned from weeks of real data — not assumptions.

1401006020nowanomalypeak forecastspot price · øre/kWh
02 · Trend

Trend detection

Electricity spot price forecasts correlated with vehicle state, weather, and historic load. Anomalies surface early; seasonal drift is captured before it costs you.

optimal · 02:00–06:00departure07:30charge model · next 24hspot priceSoC target00020612
03 · Predict

Charge prediction

The system recommends the optimal charging window by combining local spot prices, predicted departure, and target state of charge — automatically.

02 — INTEGRATION

From your car to your dashboard, privately.

Vehicle data flows from your Tesla through the Tessie API, into the encrypted OpenVPN tunnel, and into the teslaconnectivity API layer. This is a white-label connectivity solution: we provide the secure API, data pipeline, and model-ready telemetry — the end-user dashboard, branding, and customer-facing experience are created and controlled by you.

Source
Tessie
Authenticated Tesla API access, one integration per vehicle.
Transport
OpenVPN
AES-256-GCM tunnel. Dashboard access stays behind VPN.
Destination
API layer
Model-ready telemetry for dashboards you build and brand yourself.
How it works

Connect for 14–30 days.
Get real insights.

Meaningful behavioural models need meaningful data. After a two- to four-week connection window, the system has enough history to produce charge recommendations, spot-price forecasts, and usage reports tuned to how you actually drive.

01
Connect
Authorise Tessie for your vehicle and activate the OpenVPN profile. The pipeline starts collecting data immediately.
02
Observe
For 14–30 days, the system builds a model of your driving rhythm, charging habits, and local tariff patterns.
03
Predict
Personalised charge windows, cost forecasts, and anomaly signals — exposed through the teslaconnectivity API for your own dashboard or customer-facing app.
03 — Security

Wrapped in an encrypted tunnel.

Your data runs behind OpenVPN.

Live Tesla telemetry needs a secure channel. teslaconnectivity provides the secure API and connectivity layer. Your team builds the dashboard or customer portal on top of it. Access to the private API is only available after your device has joined the VPN network.

An invitation-only flow avoids a public web-login surface. There is no public account portal to phish, brute-force, or accidentally index.

Client requiredOpenVPN Community Edition 2.5+ or OpenVPN Connect, with a .ovpn profile issued to your account.
ProtocolOpenVPN / UDP 1194
CipherAES-256-GCM
AuthSHA-256 + TLS-crypt
Endpointvpn.teslaconnectivity.com
CredentialPersonal certificate
04 — Questions

Things people ask before they sign up.

Is my Tessie API token safe with you?

Tokens are provided during secure onboarding, not through this public form. They are stored encrypted at rest in Microsoft Cloud EU, scoped per vehicle, never written to logs, and revocable from your Tessie dashboard at any time.

What data do you collect?

State of charge, location, power draw, cabin climate, drive and charge events, and odometer. No Tesla account credentials, no media, no phone contents, and nothing about who is driving.

Where is the data stored?

Telemetry and configuration data are stored encrypted in Microsoft Cloud EU. The service is designed for European data residency, with operational access limited to the teslaconnectivity team for provisioning, support, and service operation.

Is this affiliated with Tesla or Tessie?

No. teslaconnectivity is an independent project that uses the Tessie API as a third-party integration. Tessie is a separate paid service you subscribe to directly.

What happens if I cancel?

Email the team. Your Tessie token is wiped, your VPN certificate is revoked, and stored telemetry is deleted within 7 days. You can request a final export before deletion.

GDPR — am I covered?

Yes. The service is designed to operate under EU GDPR, with data hosted in Microsoft Cloud EU. You have rights of access, rectification, portability, and erasure.

Returning user

Access the API.

Already issued a profile? Connect your OpenVPN client and access the private API endpoint. Your own dashboard or app can then consume the telemetry and prediction outputs through the secure channel.

VPN connection required
No connection yet? Request your VPN config to get started.
🔒 api.teslaconnectivity.com
🔐
PROTECTED BY VPN
05 — Access

Request your VPN config.

teslaconnectivity.ovpn
VPN config · personal client certificate

Each request is validated automatically. Credentials arrive by email shortly after submission.

01
Submit your request
The request goes straight to the team. Sensitive credentials are never requested through this public form.
02
Automated, secure provisioning
Each request is validated and a per-device VPN config is generated automatically. Credentials arrive by email shortly after submission.
03
Import & connect
Open the file in OpenVPN Connect or Tunnelblick. The private API becomes reachable as soon as the tunnel is up; your own dashboard can connect from there.
06 — Pipeline

How a data point travels.

01

Vehicle

Your Tesla emits telemetry: state of charge, location, power draw, climate and odometer.

02 · Tessie

Tessie API

Authenticated per vehicle. Tessie brokers the data from Tesla's API.

03 · OpenVPN

Encrypted tunnel

Private API access is protected by OpenVPN and certificate-based provisioning.

04

Private node

Request terminates on private infrastructure. Telemetry processing stays local.

05

Your dashboard

teslaconnectivity provides the API; your own dashboard, brand, and user experience sit on top.

07 — Team

A small team. One mailbox. No support queue.

Built small on purpose.

teslaconnectivity is built and operated by a small engineering team working with users across Europe. The project started in March 2024 as an internal tool to model charging behaviour across our own vehicles on variable-tariff contracts — and grew from there.

We are not a venture-backed startup and not on a hiring spree. We are a handful of people with the skills the pipeline needs: VPN operations, energy-market analytics, API tooling, and secure provisioning.

Every VPN profile is issued by hand. Every email is read by one of us. There is no support team layered on top — we are the support team.

What we do between us.

  • Run the OpenVPN infrastructure and the Microsoft Cloud EU environment behind the API.
  • Train and tune the behaviour models and the spot-price forecaster.
  • Design the API, provisioning flow, and reference dashboard components for white-label use.
  • Handle onboarding, support, and GDPR requests.
08 — Privacy · Summary

What we hold, what we don't, and how to leave.

Data controller
teslaconnectivity · operator@teslaconnectivity.com
What is collected
Tesla telemetry brokered via the Tessie API: state of charge, location, power, climate, drive and charge events, and odometer.
What is not collected
Tesla account credentials, driver identity, media, contacts, phone data, or anything outside the vehicle telemetry stream.
Where it lives
Encrypted at rest in Microsoft Cloud EU, with restricted operational access.
Who can see it
You through your VPN/API access, and the team only where needed to run, support, and secure the service.
Retention
Telemetry is retained only for as long as needed for the service and can be deleted on request.
Your rights
Access, correction, export, and deletion are available on request.
Third parties
Microsoft Cloud EU is used for hosting and storage. Tessie is a separate service you subscribe to directly.