Solaros EOS Max
EOS Max supports prioritised, event-driven Active Object state machines, with OS-native timed-event management and power-saving logic.
// 01 · Why it's different
EOS Max dispatches events directly to VSMs, it is not a task scheduler like a conventional RTOS, which wastes time searching for tasks that are 'ready to run'. EOS Max doesn't. Every event is prioritised and processed to completion by the appropriate state machine. Code executes only when an event occurs, so behaviour remains predictable and fast as the system grows.
It dispatches events to virtual state machines (VSMs) using a single shared stack, with variable-priority event handling and a minimal memory footprint. It's proprietary, controlled and commercially supported, for MCUs where every byte and cycle counts.
// 02 · How it works
Every concurrent process in the system runs in its own Active Object environment as a virtual state machine. One MCU, many processes, each modelled on the states and transitions it must follow.
Each process is modelled as states and the actions performed in each. VSM count is limited only by the memory required by their code.
A VSM runs only when an event message is pending, avoiding the task scans used by conventional RTOS schedulers.
VSMs cooperate by priority. Each runs to completion before the next highest-priority event is dispatched.
Prioritised interrupts and deterministic event processing latency.
Event notifications are raised by interrupt handlers and VSMs using event messages. Event scheduling, queuing and timed event management is handled by the OS.
Read The Developer Guide →// 03 · Runtime
EOS Max forces scalable use of system resources. Nothing is wasted, so the limiting factors become your processor's MIPS and the memory footprint of your application logic. There is minimal overhead in terms of performance and resources.
The highest-priority event runs first, to completion.
Minimal RAM requirements and no task scheduling overhead.
Fixed-block memory management, no fragmentation.
Event scheduling overhead remains constant as the system grows. Limited only by peak event notification frequency.
Pre-emptive interrupt handling with minimal latency and prioritised event processing.
Scales with code functionality, not with overhead.
// 04 · Production
Proprietary, controlled and commercially supported with full documentation and aftercare.
Run hundreds of state machines, without the performance degradation of conventional task scheduling.
Code runs only when there's an event, with power-saving logic managed by the OS.
Proprietary, controlled and commercially supported with full documentation and aftercare.
// 05 · Editions
Three editions aligned with one architecture, each built for a different class of system. Lite is free for simple, frequency-scheduled task based projects. Plus offers message-driven task scheduling for small products. EOS Max supports prioritised, event-driven Active Object state machines for complex, safety-critical systems.
Behaviourally complex products that still have to run on a small, resource-constrained MCU.
Complex and safety-critical products - medical, automotive, industrial automation and Edge AI.
Small-footprint products with low to moderate event and interrupt handling.
Embedded systems with modest functionality that still need performance and minimal resources.
Simple systems with minimal interrupt configurations.
Small projects, hobbyist and educational use.
Every edition ships under a deployment licence - Lite free, Plus $100, Max priced by scope.
// 06 · Ownership
Solaros OS follows a commercial real-time OS model. You keep full ownership of everything you build on it. Lite is free; Plus is a single-product licence, and Max is licensed to the product and deployment plan you ship on.
Everything you build with Solaros belongs to you.
Lite is free to develop, ship and deploy - commercial products included - under a free deployment licence.
Plus and Max ship under a paid deployment licence - $100 for Plus, priced by scope for Max.
Describe your system in plain and Structured English on the Solaros platform, and generate validated code architecture that runs on the OS. The platform is optional. The execution model is target and toolchain agnostic, so you can run your code base on EOS Max or your RTOS of choice. See The Platform →
// See it work
See a reference project get built from specification to code architecture.