PX5 RTOS

PX5 RTOS is a hard real-time operating system for embedded applications, built around a native POSIX pthreads API. It best suits teams developing safety-critical products on constrained hardware. Its stated timing characteristics and safety certifications are compelling; the licensing cost and fit with a target processor deserve careful consideration.

Overview

PX5 is designed for embedded systems where memory limits and predictable response times both matter. On typical 32-bit microcontrollers, a minimal configuration can use as little as 1KB of flash and 1KB of RAM. At 80MHz on those processors, most API calls and context switches take less than one microsecond, and processing time does not depend on the number of active threads. These are useful properties for tight real-time workloads, though project teams should assess them against their own hardware and timing requirements.

The stated certifications span IEC 61508 SIL 4, IEC 62304 Class C, ISO 26262 ASIL D and EN 50128 SW-SIL 4. That range makes PX5 relevant to regulated automotive, medical, industrial and rail projects. RTOS certification is an important part of a safety case, not proof that a complete product or its development process meets every applicable requirement.

Key features

The POSIX pthreads API provides a familiar concurrency interface for embedded developers. Runtime verification checks function pointers, system objects, buffers and stacks, adding safeguards against corruption in critical software paths. The maker also reports complete C statement and branch decision coverage across the RTOS code base for each release, a meaningful discipline for teams that need systematic software testing.

Architecture support includes Arm Cortex-M, Cortex-R and Cortex-A, RISC-V, Renesas RX, AMD MicroBlaze and Infineon TriCore. Support for IAR, Eclipse/GCC, Arm DS and Arm Keil tools gives teams several established development environments to work with. Integrations or examples cover TensorFlow Lite Micro, Microsoft Azure, Amazon AWS, lwIP, Mbed TLS, NetX Duo and OpenAMP, which helps connect PX5 projects to common embedded and cloud components.

Free evaluation kits cover processors and platforms from AMD Xilinx, GigaDevice, Infineon, Microchip, NXP, Renesas, SiFive, Silicon Labs, STMicroelectronics and Texas Instruments. A free PX5 Community login is required to access them. The published support SLA targets responses in under one working day for critical and serious issues, and under two working days for moderate and cosmetic issues. The support team also says it proactively alerts customers to newly identified CVEs and provides exposure guidance and known workarounds when a fix is not yet available.

Pricing

PX5 is paid software, with packages starting as low as $5K and a free trial. All three published licensing options include full source code, no royalties and professional support; the distinction is the license structure and, for enterprise deals, sublicensing options.

• Device/Product Licensing — $5,000, paid once: a perpetual license with a one-time fee. It suits a product team seeking ongoing use without annual renewal.
• Subscription Licensing — $5,000 a year: an annual-fee option with full source code, no royalties and professional support. It may fit teams that prefer a subscription structure, but carries a recurring yearly cost.
• Enterprise, SoC, Semiconductor, and Custom Licensing — $5,000, paid once: a one-time perpetual license with the same core inclusions and options for sublicensing. It is the relevant route for enterprise or semiconductor arrangements that need sublicensing flexibility.

Custom licensing is available, and pricing is on request. The published plans state no seat or usage caps, but teams should confirm terms for their intended deployment before committing.

Platforms

PX5 is an edge-deployed RTOS for embedded hardware. Its processor list spans several MCU, application-processor and real-time architectures, while its supported development tools cover IAR, Eclipse/GCC, Arm DS and Arm Keil. The breadth is useful for teams working across varied embedded targets, but the named processor and tool support should be checked against the exact project configuration.

Who it's for

PX5 is best suited to embedded teams in automotive, industrial, medical and rail sectors, or other demanding applications where real-time behavior, memory constraints and safety requirements are central. Its footprint and predictable processing are attractive for constrained 32-bit microcontrollers; its certifications and support model matter to teams building safety-critical systems. It is a less natural choice for projects that do not need those assurances and would rather avoid a paid, custom-oriented licensing process.

Pros and cons

• Pros: A stated minimum footprint of 1KB flash and 1KB RAM can suit tightly constrained microcontrollers.
• Pros: Sub-microsecond timing for most calls and context switches, with processing independent of active thread count, is relevant to predictable real-time workloads.
• Pros: Certifications across functional safety, medical, automotive and rail standards make PX5 a credible candidate for regulated projects.
• Pros: Runtime verification and full statement and branch coverage for each release provide concrete safeguards for critical software.
• Cons: The starting package cost of $5K puts PX5 beyond the reach of teams seeking a free embedded OS.
• Cons: Project suitability depends on the precise processor and toolchain combination, so teams need to confirm their target is supported.
• Cons: Custom licensing terms may require discussion before a team can settle on the right arrangement.

Alternatives

IoT Operating Systems is a broader category to explore if the project needs a different kind of connected-device software.

• Apache Mynewt is a free, open-source embedded OS and development-tools option under the Apache License 2.0; choose it when avoiding a commercial license matters more than PX5's stated safety certifications and support.
• Contiki-NG is a free operating system under the 3-clause BSD license; it suits readers seeking an open-source alternative rather than PX5's paid licensing model.
• Particle Device OS offers a free tier for up to 100 devices and 100K Data Operations per month, making it worth considering when those quotas fit the deployment.
• Micrium OS is another option to compare for embedded operating-system needs.
• VxWorks offers a free plan for up to 3 seats online; consider it if that seat allowance fits the team.
• OpenWrt is a free alternative to consider for projects that fit its Linux platform.
• RT-Thread is a free option to compare for embedded operating-system projects.
• TencentOS Tiny is another free alternative to consider.

Verdict

Choose PX5 RTOS for a safety-critical embedded project that needs a small stated footprint, predictable real-time processing and a certified RTOS with professional support. Its strongest case is the combination of those timing and safety credentials; look elsewhere if the $5K starting point or licensing terms outweigh those requirements.