OTA in a consumer IoT device that fails badly means an unhappy customer. OTA in a vehicle system touches functional safety, and that changes the update pipeline from top to bottom. Rivix builds automotive-grade firmware and the fleet-facing platform around it as one engagement.
Automotive-grade MCU integration for in-vehicle sensing and edge-compute modules.
Explore hardware →Signed, rollback-capable OTA pipelines and an ISO 26262-aware process, not a checklist bolted on afterward.
Explore firmware →Fleet-level event reporting and telematics data serving both real-time dispatch and long-horizon analysis.
Explore cloud →Dispatcher and fleet-manager interfaces built on top of the telematics platform.
Explore mobile & web →Edge computer-vision inference detecting defined safety events locally, without streaming continuous raw video.
Explore AI & Intelligence →The consumer OTA fundamentals — dual-bank (A/B) partitioning, signature verification, staged rollout — carry over, but rollback has to be provably safe and tied to the vehicle's own safety-relevant self-checks, not a generic health check. Automotive OTA manages update sets — coordinated bundles of firmware versions across multiple ECUs validated to work together — with rollback needing the same coordination in reverse. Any OTA to an ECU under functional-safety process can't ship until formal safety validation and sign-off completes, a slower gate than typical consumer OTA cadence.
ISO 26262 is the international functional safety standard for electrical and electronic systems in road vehicles. Components are classified ASIL A through D (plus QM) based on a severity/exposure/controllability hazard analysis, so a braking-related component carries different rigor than an infotainment feature. It requires forward traceability from requirement through design to test, maintained continuously through a structured V-model development process.
GPS gets fused with vehicle speed from the OBD-II bus or CAN, plus inertial data from an onboard accelerometer/gyroscope, with dead-reckoning to bridge GPS gaps in tunnels, urban canyons and parking structures. Position typically reports on a distance/time threshold rather than a fixed high-frequency interval, and derived events — harsh braking, idling, geofence entry/exit — get computed on-device and sent instead of a raw data stream.
Edge inference was chosen over cloud inference specifically to hit sub-200ms alerting latency and to avoid the bandwidth cost and privacy exposure of continuously streaming raw video from every vehicle in a fleet. Only classified events and short clips are transmitted, with local buffering carrying events through connectivity gaps.
Pulled from our case-study library — same AI/human split shown in full, industry context included.
An in-vehicle edge-AI system analyzes driving behavior locally and detects defined safety events in real time without requiring continuous transmission of raw sensor/video data.
A distributed monitoring module captures thermal conditions across an EV battery pack and identifies abnormal temperature behavior for battery-management and diagnostic systems.
OTA that touches functional safety changes the update pipeline from top to bottom, not just the risk tolerance.
Read the article →Serving a dispatcher who needs real-time location and an analyst who needs months of history, from the same data.
Read the article →ISO 26262 isn't a checklist bolted onto an existing process — it's a different process.
Read the article →Signed, rollback-capable OTA pipelines with staged rollout — the update path is designed alongside the firmware, not bolted on after v1 ships.
Teams moving into automotive quickly discover ISO 26262 isn't a checklist bolted onto an existing process — it's a different process, and we scope engagements with that gap in mind.
Yes — our edge-AI dash unit work detects defined safety events locally, sending only the event, not continuous raw video.
AI scaffolds drivers and protocol-stack boilerplate; a senior firmware engineer owns real-time timing guarantees and every power-critical code path.