pogiant
Member
- First Name
- Anton
- Joined
- Mar 22, 2023
- Threads
- 1
- Messages
- 11
- Reaction score
- 7
- Location
- Austin, TX
- Vehicles
- Rivian R1S
- Occupation
- Platform Engineer
- Thread starter
- #1
After too many road trips spent bouncing between the Rivian app, a charging map, ElectraFi, and ABRP, I built https://rivolt.dev - a single, clean dark-UI Rivian companion that consolidates the things I actually wanted in one place.
What it is
An open-source app that turns your truck's data into:
I'm looking for owners who'll actually plan trips, log charges, and tell me what's broken. Invite-only for now to keep the load sane while the trip-analysis pipeline burns through API tokens.
If you want in, comment below or DM me with:
Screenshots in the https://github.com/apohor/rivolt#readme . Happy to answer questions about the planner, the data model, or anything else.
What it is
An open-source app that turns your truck's data into:
- Per-drive analytics. Every drive becomes a page: road-snapped route map, speed / SoC / elevation / temperature / headwind charts, energy used, cost priced against your $/kWh rate. No more "wait, what did that drive cost me?" guessing.
- Per-charge ledger. Power curve over time, peak / avg kW, BMS thermal split when Rivian's API feed has it, auto Home/Public/DCFC bucketing. Sessions priced against your home rate, Rivian's reported cost or user-provided price.
- Trip planner with real numbers. Pick origin, destination, departure date/time. Rivian's planner picks stops; Rivolt layers a cost estimate on top - "$32 at chargers, ~$11 in stored energy" - plus categorized commentary on weather, drive mode, and vehicle config (tire pressures, additional weight, etc.). Numbers are computed in code; commentary is just framing.
- Live panel. Real-time SoC, range, GPS, charge state via Rivian's WebSocket feed (1–5s while driving).
- Push notifications for PWA (share web site to your home screen); multi-vehicle support; full JSON export.
- It's read-only. Rivolt can't unlock doors, start charging, or change anything on the truck. Pure telemetry.
- It's open-source and runs at https://rivolt.dev for the hosted version. There's also Docker compose file and Helm chart if you want to self-host it.
- It's in working order - I drive my truck with it every day - but it's a beta. Things might break, but data will persist.
- Your Rivian credentials are yours - AES-256 encrypted at rest, decrypted only in memory at request time, and never stored in plaintext. Rivolt is read-only against the Rivian API - it can't send commands to your truck. You can disconnect and export or delete all your data from Settings at any time. Code is open if you want to verify any of that: github.com/apohor/rivolt
I'm looking for owners who'll actually plan trips, log charges, and tell me what's broken. Invite-only for now to keep the load sane while the trip-analysis pipeline burns through API tokens.
If you want in, comment below or DM me with:
- Your Rivian model
- Roughly how often you take 200+ mi drives
- Whether you're willing to file a quick GitHub issue when something breaks
Screenshots in the https://github.com/apohor/rivolt#readme . Happy to answer questions about the planner, the data model, or anything else.
Sponsored