Realtime, Security, Performance, Medical-Box and Railway Image

Flexible Safety RTOS with RustSafety software written in Rust, with memory protection and deterministic scheduling

The certified real-time kernel and its services are designed for Rust developers. They offer the same benefits as those for ANSI-C, combined with Rust's language safety.

Q4 2026: Non-certified version available

Discuss the pilot project

What Rust Developers Get

The kernel's services are available in Rust as well as in ANSI-C. Three features stand out.

Memory Protection per Task

Individual tasks run in their own memory areas. Isolation is achieved through memory domains, without the need for manual MPU or MMU configuration.

Memory Protection per Task Group

Related tasks can be managed as a group within a shared domain. This simplifies the architecture of larger applications.

Language Checks Plus Isolation

Rust checks memory accesses at compile time. The kernel limits the impact of an error at runtime.

Rust-native API: the compiler checks what the RTOS cannot

The Flexible Safety RTOS API is designed for Rust's ownership model. Data passed between tasks changes hands, so a sender cannot keep using what it has sent. Shared resources are reachable only while a task holds the lock. Many misuse patterns fail at build time instead of in the field, which means fewer defensive checks and less review effort for ownership errors.

Ownership of messages and buffers

When a task sends a message through a queue, ownership moves to the receiver. The sender can no longer read or change the data. The compiler rejects code that tries.

Exclusive access to shared resources

Shared data can be wrapped so it is only reachable through a lock. The compiler enforces this, so a task cannot read shared data without holding the lock.

Compile-time checks at the API boundary

Misuse of task creation, resource handles, or timing parameters can fail at build time instead of in the field.

Fewer runtime checks and less defensive code

Teams spend less effort on reviews for ownership errors, which supports safety analysis.

Clear error handling

Rust's Result type makes RTOS error paths explicit, so no return code is ignored by accident.

Seeking a Pilot Customer

We are looking for a pilot customer for the first Rust project using the Flexible Safety RTOS. The pilot will use the Q4 2026 release. We will provide technical support for the project and facilitate direct contact with our developers.

Technical support from our development team
Direct access to our developers
Early Involvement in Shaping Rust Support

Robot loading a Truck with Blocks Idea, Configs, and Security

Roadmap

A non-certified status precedes certification. This allows developers to evaluate the platform early on and get started with their first projects.

Q4 2026
Non-certified unit available. Suitable for evaluation and initial development.
Q1 2027
Start of pilot customer access.
Q4 2027
Certification of the Rust integration.

Note: Until certification is granted, different requirements apply to safety projects than to certified projects. We coordinate the implementation together at an early stage.

Contact us

During a technical scoping meeting (30 to 45 minutes), we will clarify the use case, hardware, toolchain, and safety objectives.

Discuss the pilot project

Home > Products > Flexible Safety RTOS > Rust