RevDash
In the browser
Cloud & replay
An account exists so trips can leave the phone and be replayed on a map. The app itself does not need one.
Create an account
In the app: Settings → Cloud. Email, and a password of at least 10 characters. Create account or Sign in. The same account is what you use at revdash.me/app.
Passwords are stored as a slow one-way hash. Sessions are opaque tokens stored hashed, not JWTs, and last 90 days. There is no password-reset mail yet, if you lose the password, you cannot recover that account from the app.
A hidden Server field is there for people running their own deployment. Leave it alone unless you are one of them.
Upload
Signed in, tap Upload now. Pending trips go up; the summary line says how many are waiting. Upload also runs when a trip ends and when the app starts, in-process. It does not yet wait for unmetered Wi-Fi or survive the process being killed. If an upload did not happen, open Cloud and tap the button.
What goes up is the trip: OBD columns, and GPS columns if you recorded them. Telemetry is written straight to object storage against a short-lived URL. The API never reads the samples; it only hands out the keys.
Nothing uploads on its own. There is no background sync, and declining to create an account is a complete product. Hitting the free cap stops uploads for that month, not recording.
Replay
In the app, Replay trips in a browser opens the dashboard. Or go to revdash.me/app and sign in. Tap a trip.
The route opens on a photorealistic 3D globe (Google Maps) when the server has a Maps API key, and can be switched to a greyscale 2D basemap served from this origin. Colour the route by any recorded parameter, with a legend of its real range. Two charts sit under the map, locked to it: scrub, and the marker follows; brush a range, and both charts zoom together. 3D playback follows the car using the recorded bearing.
Playback is 1×, 4×, 16× or 60×. Download the full-resolution CSV at any time, on the free tier as well as Pro. If there is no basemap installed on the server, or the trip has no GPS, the page still opens, the charts still draw, and it says why.
Plans
| Free | Pro | |
|---|---|---|
| The Android app | Entirely | Entirely |
| Uploads | 20 a month | Unlimited |
| Kept | 30 days from the end of the drive | Until you delete them or close the account |
| CSV download | Yes | Yes |
| Share a drive by link | Yes, expiring | Yes, expiring |
Pro pricing is announced at launch. Buying happens in the Android app so the subscription attaches to the right account. Google Play handles the payment and the server never sees the card number.
Share links
On every tier. A link is a 256-bit token; RevDash stores only a hash of it. Anyone holding the URL can view that one trip without signing in, that is the point, and it does not name the vehicle. Default lifetime is 30 days. A wrong token looks like a missing one, so the URL is not an existence oracle for other people’s drives.
Treat a share link like a key. Anyone you send it to can pass it on. Revoke it when you are done.
Deleting a trip
From the trip list, delete. That is a soft delete: access stops now, objects are swept shortly after. Closing the whole account is under Account & backup.