SOAFEE (Scalable Open Architecture for Embedded Edge) is an industry-led architecture and collaboration effort that applies cloud-native development practices to automotive software. It is designed to let teams develop and test workloads in cloud or virtual environments, then deploy them on heterogeneous vehicle computers while accounting for safety, security, timing and resource constraints. SOAFEE is not a single Arm product, a cloud service or a blanket safety certification.
What SOAFEE is—and what it is not
The current SOAFEE site describes the initiative as a working group within the CoreCollective Open Collaboration Initiative. Its purpose is to unite automakers, suppliers and technology companies around an open architecture for software-defined vehicles.
That distinction matters. SOAFEE defines architectural practices, interfaces and reference material; individual members supply implementations, tools and vehicle programs. The title’s reference to Arm should therefore not be read as a standalone Arm automotive cloud product. A SOAFEE-based system can combine software from several vendors and run on different embedded platforms.
The initiative’s charter frames the vision as bringing “cloud-native development paradigm and its ubiquitous ecosystem” to the diverse compute platforms used by automotive and other safety-critical systems.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
Why automotive software needs a cloud-to-vehicle architecture
Cloud-native teams commonly rely on containers, automated builds, orchestration and virtual test environments. Vehicle software has additional constraints: processors and accelerators differ between vehicle programs, network and timing behavior are bounded, and workloads may have different safety and security criticalities on the same computer.
SOAFEE’s architecture addresses this combination by separating software packaging and development workflows from the exact vehicle hardware, while still requiring a path to embedded deployment. Its scope includes workloads with:
Rank #2
- Dual RS485 & CAN485 interfaces for reliable communication in industrial and automotive setups, even in noisy environments.
- Compact STM32F103C8T6 ARM core board that works great for beginners learning embedded systems or experienced developers prototyping.
- All pins fully exposed, so you can easily connect sensors, displays, or other peripherals for custom projects.
- Built with quality PCB materials for long-lasting use, whether you're testing in the lab or deploying in the field.
- Simple to program and debug — just plug in and start coding. Perfect for learning ARM architecture or building professional applications.
- safety and security requirements;
- real-time and temporal-partitioning requirements;
- spatial isolation requirements; and
- different resource and operating-system needs on shared vehicle computers.
These are requirements the architecture is intended to address. They do not prove that every SOAFEE deployment is safe, certified or suitable for a particular production vehicle.
How the “develop in the cloud, deploy at the edge” workflow works
- Package software using standard interfaces. The v1.0 architecture identifies an OCI-compliant container engine and runtime, giving applications a common packaging and execution model.
- Develop and test before target hardware is available. Teams can use cloud or virtual environments for application work, integration and software-in-the-loop testing.
- Coordinate workloads. SOAFEE v1.0 names Kubernetes-compatible workload orchestration. That describes compatibility with an orchestration model; it does not mean every vehicle runs an unmodified Kubernetes distribution.
- Move the same application concepts toward embedded targets. The goal is to reduce rework when software moves from a virtual environment to vehicle-edge computers with different processors, accelerators or operating systems.
- Validate on the actual vehicle platform. Virtual execution can improve iteration speed, but physical hardware remains necessary to verify timing, I/O, resource limits, network behavior and the safety case for a real system.
The architecture describes environmental parity as a goal: a virtual or cloud environment should be useful enough to expose problems before target hardware is available. It does not establish universal equivalence between simulation and production vehicle behavior.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- ESP32-S3 4.3″ LCD Development Board,Integrates RGB Interface LCD
- IPS Display Panel,Excellent Display Performance, 160°Viewing Angle
- Supports Multiple Peripherals,Supports The Expansion Of Multiple Peripherals Via Sensor, CAN, RS485, And I2C Interfaces
- A microcontroller development board with 2.4GHz WiFi and BLE 5 support,
- Equipped with Xtensa 32-bit LX7 dual-core processor, up to 240MHz main frequency.
What SOAFEE v1.0 specifies
SOAFEE’s architecture documentation identifies the following elements for its published v1.0 architecture:
| Element | What it means in practice | Qualification |
|---|---|---|
| OCI-compliant container engine and runtime | Applications can use a standards-based container packaging and execution model. | An OCI interface does not by itself solve real-time, safety or hardware-integration requirements. |
| Kubernetes-compatible workload orchestration | Workload descriptions and lifecycle concepts can align with Kubernetes-compatible orchestration. | The documentation does not say that every in-vehicle deployment uses stock Kubernetes. |
| Develop-in-cloud, deploy-at-edge workflow | Cloud or virtual development is connected to deployment on vehicle computers. | Useful parity must still be demonstrated for each target platform and workload. |
| CI-supported reference implementation maintenance | Continuous-integration practices help maintain and test the reference implementation. | This is an engineering and maintenance approach, not a production certification. |
| Standards-based firmware platforms | Firmware and low-level platform integration are treated as standardised architectural concerns. | Actual hardware support depends on the implementation and vehicle program. |
The documentation names EWAOL (Edge Workload Abstraction and Orchestration Layer) as the reference implementation expressing that release. EWAOL is therefore a concrete implementation of the architecture, not a synonym for SOAFEE itself.
SOAFEE architecture versus member blueprints
SOAFEE also publishes blueprints: member contributions that demonstrate applications, tools or technology patterns using the architecture. A blueprint is an example implementation, not a mandatory SOAFEE component.
| Blueprint example | Focus | Capabilities described by the contributor | Evidence status |
|---|---|---|---|
| Panasonic Automotive Systems’ vSkipGen | Virtual cockpit-domain-controller development | Panasonic’s 31 March 2026 article describes VirtIO-based device virtualisation, multiple guest operating systems, and cloud, on-premises, simulation and browser-streaming workflows. | Vendor-authored blueprint description; not an independent benchmark of every claimed capability. |
| EPAM’s AosEdge | Vehicle-edge deployment and orchestration | EPAM’s 3 June 2025 article describes an in-vehicle runtime paired with a cloud backend. | Vendor-authored example of one deployment approach; not a universal SOAFEE runtime. |
SOAFEE’s 2025 blueprint campaign announcement also describes work around cloud-native tooling, MLOps, virtual development and safety-critical workloads. Those subjects show the breadth of the program, while the individual blueprints show how members choose to implement it.
Recommended Free Tools
Best Value
- ALL-IN-ONE FORMULA (PMWCSPI23430): Cleans, protects, and refreshes every interior surface including dashboards, vinyl, plastic, leather, fabric, and glass for a complete detail in one easy step.
- NEW CAR SCENT EXPERIENCE: Infused with the signature New Car Smell fragrance to restore that just-detailed freshness every time you clean your vehicle’s interior.
- SAFE FOR ALL INTERIORS: Designed for modern automotive materials; use on steering wheels, door panels, consoles, and more without streaks, fading, or residue.
- QUICK AND CONVENIENT: Pre-moistened wipes make touch-ups effortless at home or on the go; perfect for daily maintenance or quick cleanup between full details.
- CLEANS AND PROTECTS: Removes dust, light grime, and smudges while leaving behind a smooth, dry finish that helps maintain a clean look and feel across all surfaces.
What SOAFEE does not guarantee
- Automatic safety compliance: adopting the architecture does not certify a vehicle against ISO 26262, cybersecurity regulations or another required standard.
- Identical cloud and vehicle behavior: simulation and virtualisation can differ from physical timing, sensors, buses, accelerators and failure modes.
- Complete hardware independence: applications still depend on platform drivers, firmware, accelerators, memory, real-time behaviour and integration work.
- A single required product stack: SOAFEE is an open architecture and collaboration effort, while EWAOL and member blueprints are implementations or examples.
- A guaranteed production outcome: the available material establishes goals and architecture elements, not universal deployment results, cost savings or performance improvements.
What an engineering team should verify before adopting it
- Confirm the target release. SOAFEE announced its initial Architecture v1.0 release on 5 April 2023 in its official release notice. The available documentation still discusses v1.0, but the sources do not establish that it is the latest authoritative architecture. Check the official release channels before fixing version numbers in a project.
- Map workloads to criticality and timing. Identify which tasks are safety-related, real-time, security-sensitive or isolated from one another before selecting containers, operating systems and orchestration policies.
- Choose the reference implementation or another conforming stack. Evaluate EWAOL or a member blueprint against the actual vehicle computer, firmware, accelerators and required lifecycle controls.
- Define virtual-to-physical validation gates. Specify which tests run in cloud simulation, which require hardware-in-the-loop and which must run on the production configuration.
- Audit supplier claims separately from architecture requirements. Ask vendors for supported hardware, guest operating systems, timing limits, update mechanisms, security evidence and certification artifacts rather than treating a blueprint description as proof of compliance.
Why SOAFEE matters for software-defined vehicles
SOAFEE’s central contribution is a common way to discuss automotive software across cloud tooling and embedded deployment. It gives teams standards-oriented building blocks and a shared workflow for moving from virtual development toward vehicle-edge execution, while acknowledging that mixed-criticality and hardware constraints cannot be abstracted away completely.
For developers, the practical value is earlier integration and more reusable automation. For vehicle manufacturers and suppliers, the open architecture can provide a common reference point when comparing platforms. The final safety case, hardware integration and production qualification still belong to each vehicle program.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
