// the find
Luos-io/luos_engine
Open-source and real-time orchestrator for cyber-physical-systems, to easily design, test and deploy embedded applications and digital twins.
Luos-engine is a microservice framework for embedded systems — it lets you split a multi-board hardware product into independent 'services' (a motor driver, a sensor, a gateway) that communicate over a shared bus, regardless of MCU or transport layer. The abstraction sits between bare-metal HAL code and something like ROS, targeting teams building robotics or IoT products with multiple interconnected boards.
HAL coverage is genuinely broad: STM32F0/F4/G4/L0/L4, ATSAMD21, ESP32, Arduino, and a native POSIX target for simulation — you can run the same service code in unit tests or a digital twin without touching the hardware path. The Object Dictionary (engine/OD/) gives you typed physical units (angular velocity, pressure, PID params) as first-class message types, which cuts a lot of ad-hoc serialization boilerplate that plagues embedded comms layers. The bootloader module is included in-tree, so OTA firmware updates across a daisy-chained board network are part of the architecture, not an afterthought. CI with clang-format enforcement and a PlatformIO registry integration means the project is actually usable without cloning the repo manually.
544 stars after what appears to be several years of development is a warning sign — the community is small, and small communities mean sparse real-world examples beyond the handful provided. The README leans on external documentation (luos.io) for almost everything substantive, so if that site goes down or the project stalls, you're reading source code alone. The transport layer abstraction is opaque from the outside: it's unclear without deep reading how you add a custom physical layer (CAN, SPI, custom UART framing), and the HAL template doesn't make this much clearer. The 'digital twin' claim in the description is aspirational — the NATIVE HAL lets you run services on a PC, but there's no simulation environment, no virtual bus topology, and no integration with any actual digital twin platform.