Use cases
One bridge, many ways to use it.
redswitchboard patches one car's data into another car's apps. Pick a source on one side and a sink on the other: cross makes, or point a car at itself for your own logs and metrics.
Your Rivian in Tesla apps
Drive a Rivian, see it in TeslaMate, TeslaLogger, Home Assistant, and any Tesla Fleet API app: drives, charges, and history, on the dashboards built for Teslas.
Keep your Owner API app alive
Tesla is retiring the old unofficial Owner API (owner-api.teslamotors.com) for the OAuth-based Fleet API. Put redswitchboard in front: it speaks Fleet API to Tesla and serves the data back in the Owner API shape, so your existing Owner API app keeps working unchanged, no rewrite, even after Tesla turns the real Owner API off.
Note: Bridges vehicle data (logging and monitoring), not vehicle commands, which now require Tesla's Vehicle Command Protocol.
A buffer in front of your Tesla
Proxy your own Tesla through the bridge to smooth Fleet API rate limits, keep your own logs and metrics, and connect extra apps, all from one cached source.
Owner API into Fleet API apps
The reverse pairing: read your Tesla over the older Owner API (owner-api) and re-serve it as the current Tesla Fleet API, so Fleet-era apps work with an Owner-API source.
Run a Rivian into its own tooling
Point a Rivian at itself to capture logs, build analytics, and wire up other apps against a stable, cached copy of your data instead of hammering the vendor API.
A Tesla served as a Rivian
The reverse direction: serve Tesla data in the Rivian GraphQL shape for Rivian-native tools. Building it now via the tesla-fleet and rivian-graphql plugins.
Make-agnostic
The bridge is vendor-agnostic: pick any source make, serve it as any app's API. Tell us your make on the waitlist and you help set the order we build them in.
For apps and integrators
Migrating off the Tesla Owner API?
If you run a service or app built on the old Owner API, redswitchboard can sit in front of the Fleet API and serve the data back in the Owner API shape, so your integration keeps working without a rewrite. Self-host it, or talk to us about running it for you.
It bridges vehicle data (logging and monitoring), not vehicle commands, which now need Tesla's Vehicle Command Protocol.