Why this environment matters
For autonomous driving domain controllers, the system combines perception, localisation, route planning and actuator requests inside a safety-critical vehicle computer. The risk extends beyond a conventional endpoint: a compromised perception or planning component could feed unsafe commands into steering, braking or acceleration paths. A NØNOS deployment concept would treat every software component, data source and device interface as separately authorised rather than assuming that anything running on the host should be broadly trusted.
The security challenge
Connected vehicles combine public-facing radios, third-party content, diagnostics and hardware that can affect motion. Security therefore has to control both information flow and authority over physical functions. In autonomous driving domain controllers, the decisive risk is that a compromised perception or planning component could feed unsafe commands into steering, braking or acceleration paths. Even strong perimeter controls may not help once authorised software, a vendor tool or a valid user session has been compromised. Internal permission boundaries must remain enforceable after initial access.
How the capsule model could help
For this system, NØNOS could separate perception, planning, communications and maintenance workloads into signed capsules with narrowly scoped access to sensors and actuators. The design would combine verified boot and attestation, minimal persistent state, a memory-safe Rust core and signed capsule updates. The intended result would be a set of small trust boundaries instead of one large operating environment where every service inherits broad ambient access.
Deployment requirements
Any in-vehicle deployment would require OEM integration, hardware-specific drivers, deterministic timing analysis, functional-safety assessment and validation against the vehicle's existing safety architecture.
Current public-beta limitations, hardware support and application availability must be assessed before any pilot. Neither this use case nor an industry source establishes NONOS certification or a current customer deployment.
Who could buy or integrate it?
- Vehicle manufacturers specifying central autonomy computers
- Tier 1 controller suppliers integrating the execution platform
- Autonomy developers buying development and validation systems
Industry examples: Aptiv, Bosch. These are research prospects, not represented as NONOS customers, partners or endorsers.