One Rust framework for every chip and every operating system
tQCS is the representative and delivery partner for Veecle across Asia-Pacific, including Korea, Japan and China.
Key Advantages
Write once, run anywhere. The same application code runs on a safety MCU, a Linux process on an HPC, or Android Automotive, without rewriting or manual porting.
Start before hardware is ready. Applications can be developed and tested on a normal PC, a cloud VM, or a simulator, and then moved to the real ECU.
Keep what you already have. Veecle OS does not replace your kernel, AUTOSAR stack or network stack. It sits on top of them, so existing certified software can stay in place.
Safety by design. Veecle OS is written in Rust, so many common errors are caught by the compiler before the code ever runs. It is designed to work with qualified Rust toolchains such as Ferrocene.
Telemetry from day one. Logging, tracing and timing information are built into the runtime and available from the first line of code.
Open and free to adopt. Veecle OS is licensed under Apache 2.0, with no vendor lock-in.
Operating System Abstraction Layer
Veecle OS is a Rust programming framework for distributed, real-time and mixed-criticality applications. It gives developers one way to structure an application — how it is split into parts, how those parts communicate, and how they run — no matter which hardware or operating system is underneath.
It helps to be clear about what Veecle OS is and is not:
| Veecle OS is | Veecle OS is not |
|---|---|
| Veecle OS isA Rust framework that defines how applications are built and run | Veecle OS is notA finished application with business logic or algorithms |
| Veecle OS isAn asynchronous application runtime that works on top of any kernel, middleware or hardware | Veecle OS is notA replacement for FreeRTOS, Linux, QNX, AUTOSAR or Android |
| Veecle OS isAn orchestration layer that uses existing middleware to move data between applications | Veecle OS is notA new network standard or a replacement for CAN, SOME/IP or DDS |
How it is built
Applications in Veecle OS are made of small, independent units called actors. Each actor waits for an event — a timer, or a new message from another actor — does its work, and waits again. Actors exchange data through a central store in which every data type has exactly one writer. The runtime checks this at build time, so wiring mistakes are found early.
| Layer | What it does |
|---|---|
| Applications | Your code, written once as a set of actors. |
| Base services | Ready-to-use services for communication, data persistence, tracing, logging and health monitoring. |
| Runtime and orchestrator | Schedules actors, manages timing and isolation, and moves data between applications. Deterministic and asynchronous. |
| OSAL | The Operating System Abstraction Layer. Gives applications one API for time, memory, address spaces and hardware access. |
| Underlying OS | Your existing operating system or bare-metal runtime, unchanged. |
The Operating System Abstraction Layer
The OSAL is what makes the same code portable. It has two parts. The first is a common API that defines what an application can ask the operating system to do. Applications only ever use this API. The second is a set of implementations, one for each operating system. The target is chosen in one place, when the runtime starts, so moving an application to a new platform does not require changes to the application itself.
| Platform | Status |
|---|---|
| Linux and macOS | Supported in the open-source release (through the Rust standard library) |
| FreeRTOS | Supported in the open-source release |
| EmbassyNative Rust embedded runtime | Supported in the open-source release |
| AUTOSAR Classic, QNX | Built for customer projects |
| Other operating systems | Custom OSAL implementations can be added |
On the network side, Veecle OS provides typed data support for CAN and SOME/IP and can connect to DDS, UDP, TCP/IP and custom protocols. Applications work with clear data types, such as a speed value in m/s, rather than raw bytes.
What this gives you
Application teams can build and test real software from the first week of a programme, long before target hardware is available. The same code then moves from a PC or cloud VM to the MCU, the HPC or the infotainment system without being rewritten. This shortens development time and finds integration problems when they are still cheap to fix.
Because Veecle OS sits on top of existing platforms instead of replacing them, it can be introduced step by step. Teams keep their certified kernels, AUTOSAR stacks and middleware, and gain a modern, shared way to build applications across all of them.