Skip to main content
Version: Next

Deploy a Service

Now that you have your device ready as a Unit, let’s run your application — or as we call it in AosEdge, a Service.

Service​

From static to dynamic​

In AosEdge, the term Service represents a modern way of thinking about in-vehicle software.

Traditionally, automotive software has been deployed as a fixed, monolithic application — tightly bound to a specific ECU and rarely updated during the vehicle’s lifetime.

However, as vehicles evolve as software-defined, this static model must shift to be much more dynamic and scalable.

AosEdge envisions that software within the automotive environment should be flexibly deployed, updated, and managed across diverse compute domains — while still ensuring the safety and security required for automotive-grade systems.

Architectural shift for SDV​

With the industry’s move toward centralized E/E architectures powered by high-performance computing (HPC) units and domain clusters, applications need to be portable, isolated, and secure by design.

This means treating software not as static binaries, but as Services — modular components that can run independently, interact through defined interfaces, and be orchestrated dynamically.

This shift enables continuous improvement, domain abstraction, and more efficient software reuse across vehicle programs.

AosEdge as foundation​

AosEdge provides the platform foundation for this transition. By integrating container orchestration, secure runtime environments, and safety isolation frameworks, AosEdge allows each Service to be deployed and managed appropriately according to its safety classification and operational domain.

Through AosEdge, you can:

  • Manage multiple Services on the same Unit with isolation and policy control

  • Deploy updates seamlessly and securely with multi-tenancy

  • Mix workloads across QM and ASIL domains under a unified orchestration framework (Mixed Criticality)

Types of Services​

In AosEdge, there are generally two categories of Services:

QM Service​

A QM (Quality Managed) Service is designed for non-safety-critical workloads — for example, telematics, data analytics, or connected vehicle functions. These services run within the Linux container framework, enabling rapid deployment, scalability, and remote updates similar to cloud-native systems.

ASIL Service​

An ASIL (Automotive Safety Integrity Level) Service, on the other hand, is intended for safety-critical workloads that require deterministic behavior, strong isolation, and certified environments. AosEdge enables these services to run as Unikernel-based microVMs, powered by Xen Hypervisor and Zephyr RTOS, ensuring both performance efficiency and safety compliance.

Section contents​

In the following section, you’ll learn how to run both types of Services on your Unit — starting with a QM Service using our container framework, then moving on to an ASIL Service using the microVM framework.

  • Run QM service

Upcoming contents...

  • Run ASIL service