Realtime
Upstash Redis for realtime dispatch
Renaro's realtime architecture uses Redis patterns for pub/sub, fleet telemetry, GPS hot paths, and live updates that keep dispatchers close to current state.
- Realtime
- Pub/sub updates
- GPS
- Hot-path fleet state
- WebSocket
- Live fanout
- Resilience
- Degraded fallback posture
Dispatch state has to move quickly
Driver positions, booking state, assignment events, and fleet availability lose value when they are stale.
- Use realtime coordination for dispatch board updates.
- Keep GPS hot-path data close to live fleet views.
- Preserve graceful behavior when realtime infrastructure degrades.
Where this page fits
Realtime infrastructure pages help Renaro support technical searches and explain why the dispatch board can be live by default.
- Link Redis content to live dispatch, driver app, and fleet management.
- Keep technical copy tied to visible operator outcomes.
- Avoid implementation details that belong in private runbooks.
Related integration paths
Common questions
Are integrations implemented directly in the landing app?
No. The Astro landing app documents and routes SEO traffic to Renaro's product areas. Operational integrations are owned by the API, worker, and platform domains.
Why create integration landing pages?
Operators and technical buyers search for specific provider support. These pages state the current data and workflow boundary and link to capabilities that are available today; they do not imply that an unconfigured OAuth connector is live.
See Renaro with your own trips.
Bring a few of your real reservations. We'll show you how your office would handle them in Renaro, from the first phone call to the paid invoice.