hipperos.com

What It Is

HIPPEROS S.A provides a family of multicore hard real-time operating systems (RTOS) for safety-critical applications. It targets scenarios such as aerospace, avionics, defense, automotive safety, robotics, industrial control, medical devices, vision systems, and high-end IoT/edge computing, aiming to combine high performance, predictability, reliability, and safety on multicore platforms.

Core Capabilities

Based on the information on the site, HIPPEROS is built around redesigning an RTOS for multicore architectures, rather than extending a traditional single-core RTOS. Its master/slave microkernel architecture is intended to reduce overhead, minimize context switching and cache invalidation, and improve scheduling scalability. The system supports temporal and spatial isolation, and can work with MMU/MPU mechanisms to improve the reliability of critical tasks. It also supports mixed-criticality workloads, processor affinity, partitioning, and cluster scheduling. For scheduling policies, it offers configurable options such as RR, TS, RM, DM, EDF, EDFk, and UEDF, and mentions dynamic scheduling algorithms for benchmarking. On the engineering side, it includes mutexes, semaphores, message passing, mailboxes, shared memory, events, timers, alarms, efficient IPC, resource-sharing protocols, as well as starvation/deadlock detection and a recovery watchdog.

Platforms, APIs, and Ecosystem

HIPPEROS supports, or plans to support, multiple 32/64-bit architectures, including ARM, x86, PPC, MIPS, Leon, and ARC, and is compatible with embedded toolchains such as IAR, Keil, and GCC. In terms of APIs, in addition to its native API, it mentions compatibility directions such as POSIX 1003.12 RTOS, OSEK/AUTOSAR, ARINC 653, and ITRON. At the ecosystem level, the official site refers to collaborations with Thales, CEA-LETI, and the EuroCPS H2020 project, and has showcased an avionics mixed-criticality platform use case.

Pricing and Documentation

The site does not publish pricing, licensing models, payment methods, or edition packages, offering only evaluation request and contact entry points. As for documentation, the official pages provide a fairly substantial overview of the architecture, scheduling, certification goals, and application areas, but no API manual, development tutorials, sample code, download portal, or release update information was found. As a result, any practical evaluation would still require contacting the vendor.

Pros, Cons, and Who It Is For

Its strengths are its clear positioning and its focus on multicore safety-critical systems, with design emphasis on scheduling, isolation, fault recovery, profiling/tracing, and certification readiness. The drawbacks are the lack of public commercial information, unclear open-source/closed-source status, and relatively old official news, making it difficult to judge the current level of support activity. It is better suited to professional embedded teams that need multicore real-time performance, safety certification, and long-term engineering validation. It is not ideal for projects that only need a lightweight MCU RTOS or a community-driven open-source ecosystem.

Access from China

The crawled text did not provide information about access from mainland China, payment options, or local support, so the access status is unknown. If procurement is restricted, alternatives to compare include VxWorks, QNX, Integrity, FreeRTOS, Zephyr, ThreadX, and RTEMS.