Overview
QNX® Neutrino® Real-Time Operating System (RTOS) is the industry-leading RTOS for developing mission-critical embedded systems software for industries including automotive, robotics, medical devices, industrial controls, and aerospace & defense.
The microkernel architecture provides an extensible operating system framework managed by the kernel foundational components, system libraries and frameworks. When modified or configured to operate on target hardware, the QNX Neutrino RTOS provides a microkernel operating system with advanced memory protection, distributed processing, symmetric multiprocessing, a dynamically upgradeable architecture, and real-time performance.
This cloud-enabled version of the RTOS is part of the BlackBerry QNX Accelerate initiative. Develop mission-critical embedded systems software, globally, at scale. Accelerate development cycles with full ARM64 binary parity and CI/CD pipeline integration. Focus on innovation, with reduced capital expenditure and faster time-to-market.
Highlights
- Microkernel RTOS - safe, reliable, scalable, secure, cost-effectiveness, real-time, high performance, with ARM64 binary parity from embedded target system to the cloud
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Dimension | Cost/hour |
|---|---|
t4g.xlarge Recommended | $0.37 |
t4g.2xlarge | $0.37 |
r6g.xlarge | $0.37 |
m6g.large | $0.37 |
r6g.2xlarge | $0.37 |
c6gn.medium | $0.37 |
m6g.4xlarge | $0.46 |
c6gn.8xlarge | $0.57 |
c6gn.large | $0.37 |
m6g.medium | $0.37 |
Vendor refund policy
Customer may cancel and cease using the software and service at any time. In no event will any refund or credit be provided.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (Arm) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Additional details
Usage instructions
Please refer to the linked documentation titled "Getting Started with QNX in the Cloud" under "Additional Resources"
Resources
Support
Vendor support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Standard contract
Customer reviews
Advanced traceability has improved debugging and now optimizes complex embedded architectures
What is our primary use case?
For seven years, I was a software architect and used QNX Neutrino as part of my platforms. QNX Neutrino was the main operating system for one of the processors that we were using. I find it difficult to mention one specific thing about my main use case or how I was using QNX Neutrino in my projects, as it is a substantial stack of libraries, tools, and SDKs. I believe we were using most of it.
I was mainly involved in projects with product lifecycle and software architecture on that processor, deploying different in-house built platforms while referencing them to QNX Neutrino and stepping on QNX Neutrino itself. It is genuinely difficult to mention just one thing.
What is most valuable?
QNX Neutrino offers excellent features including debuggability. I would highlight traceability of the processes, configuration of the processes, network, memory layout, and so forth.
Out of those features, the traceability of the processes and the threads made my life significantly easier and was especially valuable in my projects. I was able to easily see when a thread was being actively used or when it was just looping without making any progress or when it was in idle. This was very helpful when we had to improve the startup of the system, as we were able to reduce it from twelve seconds to approximately two or three seconds just by analyzing how the threads were being started and their dependencies. This was one of the most useful features.
QNX Neutrino has positively impacted my organization because it was chosen as the main operating system for the products, at least for the graphical interface communication and for the application layer management. It was established as the best operating system for those kinds of platforms in my organization.
What needs improvement?
QNX Neutrino can be improved by simply continuing the good support and enhancing the toolsets.
While I cannot identify specific improvements needed for QNX Neutrino right now, something that could improve what I was doing would be to somehow analyze those threads. Instead of me going through the trace logger, it would be beneficial for QNX Neutrino to make automatic analysis and determine what the correct order of the startup of the processes should be in order to achieve the best startup of the system. I think that could be a valuable addition.
For how long have I used the solution?
I have been using QNX Neutrino for approximately ten years.
How are customer service and support?
Regarding specific outcomes, I cannot speak to that because when I started, we were already using QNX Neutrino. We were only updating it, building upon it, and reconfiguring different systems. I observed that QNX Neutrino was easy to work with and had very good support. Therefore, I cannot say if it was better than anything else.
What other advice do I have?
I do not think I can give that kind of advice to others looking into using QNX Neutrino because it is very specific to the people that are using it, and it depends on everyone's specific needs, projects, and so forth. It is not advice that I would give in a general manner.
I would rate QNX Neutrino a nine on a scale of one to ten.
I give it a nine because I always operate with the idea that something could be improved, even if I do not know that it exists. I cannot give a perfect score just for that reason. It is certainly a better option than Linux for those kinds of projects.
I have no additional thoughts about QNX Neutrino.
Certified middleware has streamlined safety-critical ADAS development and supports future projects
What is our primary use case?
QNX Neutrino is currently one of many trials that we are conducting for testing the best match for our different product lines as we have been experimenting and preparing for potential customer projects.
For example, we are using QNX Neutrino for developing one of our ADAS domain controller ECU, which is based on Texas Instruments TDA4 VM SOC, as a middleware stack on which we were deploying some of our performance algorithms.
That is the only use case that I have been personally involved with, and that is all I have to add about my use of QNX Neutrino in these projects.
What is most valuable?
I would say for the performance cores, QNX Neutrino offers enhanced security features compared to functional safety and security features when compared to any Linux alternatives.
We use our products for ADAS and automated driving, which are ASIL B to ASIL D level safety-critical applications, and QNX Neutrino helps us by providing certified middleware stacks so we don't have to do extensive testing on it, allowing us to focus only on the functions and algorithms. Using any open-source Linux would cause a lot of effort for us to test the overall software, so QNX Neutrino actually helps us reduce our effort and focus our software testing only on the functions and algorithms. It also offers virtual ECU type environments for a lot of testing even before integrating the whole software onto the actual hardware, thus saving us a lot of time later.
What needs improvement?
I cannot answer how QNX Neutrino can be improved as I don't have any pain points or areas I wish were better.
There is nothing that comes to my mind regarding needed improvements.
For how long have I used the solution?
I have been using QNX Neutrino since 2024, although we haven't made any salable products with it, we have used it for most of our core development.
What do I think about the stability of the solution?
QNX Neutrino is stable.
Which solution did I use previously and why did I switch?
I did not previously use a different solution before QNX Neutrino.
Which other solutions did I evaluate?
I haven't evaluated other options before choosing QNX Neutrino, as we were just experimenting with it.
What other advice do I have?
There is nothing more that I would like to add about the features.
It's too early to say how QNX Neutrino has impacted my organization positively, as we haven't really noticed any significant advantages, but we are preparing for next-gen use cases. We haven't won any customer project where we had to use QNX Neutrino middleware stack, but we do have a lot of exposure to it right now, and when we win such businesses, we know we should be using QNX Neutrino.
I would say nothing specific regarding expectations or hopes for how QNX Neutrino could impact our team's workflow or efficiency if we move forward with it, as we already have other alternative solutions. One good thing that I can mention is that with the performance cores, like the A72 cores, we have very less mass production experience with them, so if we were to launch on a customer-selected SOC with performance cores, QNX Neutrino might give us some time savings because it has already proven middleware stack compared to Linux.
I gave this review a rating of 8.