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.
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.
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.