rEVolt FinderOverview
Charging by car make avg navs / user
Top charging hotspots
Live user map latest position per user · ● = active in last 5 min
Live locations by user latest search per user
Recent searches newest first
Users
Most active first — includes contact & home details for export.
Journeys per user · miles & navigations
Activity feed searches · navigations · sign-ups · reviews
Reviews star ratings drivers have left
Charging hotspots where people navigate to charge · 90d
Cars by make
Public-charging use by make total navs
Top models
Station directory junk hidden · by state
Caches
Clear a request cache to force fresh data on the next fetch. The station directory and NREL bulk table are left untouched.
Test data
Remove seeded test accounts and probe events (kept out of your real analytics).
OCM background sync
Users are served from the database; this worker refreshes areas from Open Charge Map off the request path, throttled to respect their fair-use policy. OCM being slow or down never affects the app.
What's Nearby (POI) warm-up pre-loads amenities so testers skip the slow first look-up
Overture POI import amenities cached from Overture Maps
Progress of loading amenity data into the database. Once loaded, "What's Nearby" serves instantly — no live look-up.
Verify the data
Pull a live sample straight from the database so you can confirm what actually loaded — and that it's only food / restaurants / bars / restrooms.
Outbound email (SMTP)
The server your app sends email through — verification codes now, sign-in later. Stored server-side; the password is write-only and never shown back.
Note: Railway blocks SMTP below the Pro plan, so production email sends via Resend (set RESEND_API_KEY in Railway). Send test uses Resend automatically when that key is present; otherwise it tries this SMTP server.