Use Cases

Developing for heterogeneous ECUs requires a separate porting effort for each target platform. Hardware changes mean integration overhead, regression risk, and slower development cycles.

The WebAssembly-based architecture creates a unified execution environment: the same binary runs deterministically on high-performance computers and microcontrollers alike — across all development and test stages through to the vehicle fleet.

Monolithic systems make every change risky: new features, supplier integration, or updates require full regression of the entire system and block parallel teams.

Modular building blocks with standardised interfaces allow independent updates, flexible recombination, and direct reuse — from microcontrollers to high-performance computers, without starting system integration from scratch.

Heterogeneous target platforms each require their own runtime optimisations. Traditional container solutions are too heavy and too slow for resource-constrained embedded systems.

The LightWeave runtime delivers near-native speed at minimal footprint — up to 90 % lower runtime overhead compared to traditional containers, deterministic and reproducible on every platform.

Increasing connectivity and third-party software dramatically enlarge the vehicle attack surface. Traditional execution environments offer no module isolation — one compromised module can endanger the entire system.

WebAssembly sandboxing creates "Freedom from Interference": each component receives only explicitly granted interfaces. Compliance with ISO 26262 and ISO/SAE 21434 is actively supported — enabling safe execution even of third-party code.

Insufficient test coverage is hard to measure and impossible to find reliably by hand. Security risks from undiscovered test gaps often remain hidden until late in the development process.

The RapidTest framework uncovers weaknesses early through targeted code mutation. Reproducible test results across all stages (MIL → HIL → vehicle fleet) provide high transparency over the true effectiveness of tests for critical functions.

In C/C++, entire bug classes — buffer overflows, use-after-free, data races — are inherent to the language and surface at runtime. These errors are hard to reproduce and cause critical security vulnerabilities.

Rust eliminates these bug classes at compile time through memory safety without garbage collection. Combined with WebAssembly sandboxes, a second protective layer reliably isolates even faulty third-party code.

Gateway implementations between CAN and Ethernet are traditionally hardware-bound. A new target platform demands redevelopment or costly porting — tying up development capacity that should go into domain logic.

As a WebAssembly component, the same gateway logic runs identically on embedded systems and x86 platforms alike. The clean separation of runtime and logic makes the gateway independent of hardware, OS, and network layer.

Traditional testbenches are hardwired and site-bound — reconfiguring for new vehicle architectures takes hours. Each partner runs expensive infrastructure that sits idle most of the time and cannot be shared.

The SDVA-Bench is remotely reconfigurable in seconds. All stages (MIL → SIL → HIL → VIL → production) are traversed with identical binaries. OTA updates, remote debugging, and granular access controls enable parallel use by globally distributed teams.

Manual optimisation of network topologies in SDVs does not scale: as system complexity grows, bottlenecks and latency problems become ever harder to predict and resolve.

GNNs analyse topology graphs and real bench measurement data, detect bottlenecks early, and automatically suggest optimal communication and compute paths — from ECU level up to complex zone architectures in the SDV.

Missing standards force every OEM–supplier pair into proprietary integration — silos emerge, components cannot be reused, and every new project starts from zero.

WIT interfaces and AUTOSAR compatibility enable seamless combination of components from different vendors — a coherent, cross-manufacturer SDV ecosystem that systematically promotes reuse.

Every OEM has its own requirements for middleware stacks and certification formats — suppliers must re-port, re-test, and re-qualify components for each customer. This drives up costs and slows projects significantly.

The Same-Binary approach with WIT interfaces eliminates platform-specific porting. Faster validation processes, lower certification costs, and a clear foundation for OEM integrations — across all vehicle architectures.

Heterogeneous stacks of AUTOSAR, proprietary middleware, and WebAssembly components are difficult to harmonise. Every integration carries regression risk, and distributed teams work on inconsistent states.

WIT + WebAssembly create a unified interface foundation for all components. The globally configurable SDVA-Bench ensures consistent test states — with remote reconfiguration, OTA updates, and unified debugging tools for distributed teams.