For decades, QNX has been running the systems people bet their lives on, from medical devices and factory floors to trains, robots, and more than 275 million vehicles. It guarantees not just that your code runs, but exactly when. Now QNX 8.0 is free for non-commercial use, and the QNX team wants to see what you do with it when nobody hands you a spec.
Build a robot that reacts in microseconds instead of milliseconds. Write the driver nobody has written yet. Port something you love to QNX, or build the tooling you always wished existed. If it runs on QNX 8.0, or helps someone else build for it, it counts. Pick your category and compete for a share of $50,000. Show us what you can do!
Why join?
- Get your hands on a real-time OS, free. QNX Everywhere gives you QNX SDP 8.0, QNX Developer Desktop, and the QNX Hypervisor for non-commercial use, plus free training courses to get you moving. No target hardware required; QEMU works, and so does a Raspberry Pi 5.
- In 275 million vehicles. Now on your laptop. Not a teaching edition or a stripped-down trial. It's the same QNX that ships in commercial systems, and until QNX Everywhere, building on it meant a commercial license.
- Compete for $50,000 in prizes. Plus swag, a coffee chat with a QNX exec, and a feature on the QNX blog and social channels.
Get Started
- Get free access to QNX SDP 8.0 through QNX Everywhere (5 minutes)
- Run through the QNX SDP 8.0 Quick Start Guide and get a program running on your target or QEMU (45 minutes)
- Browse QNX sample projects and open-source ports, then pick your category (30 minutes)
Requirements
What to Build
Build a project that runs on or targets QNX 8.0 (QNX Everywhere). Either:
- A software application, driver, library, or component that runs on the QNX 8.0 real-time operating system, on any target hardware QNX supports, including QEMU; or
- A host-based tool (Windows, macOS, or Linux) that builds, tests, analyzes, or otherwise supports software targeting QNX 8.0.
Choose one of the following categories:
- Robotics & Medical. Real-time applications where timing, safety, or reliability is critical.
- Automotive & Mobility. Software-defined vehicle and other mobility applications.
- Low-level Software. Board support components or device drivers built with the QNX Driver Development Kit.
- Developer Tooling & Host Tools. Tools that make building for QNX easier, on the host or the target.
- Open-Source Contribution & Ports. Porting an existing open-source project to QNX or contributing upstream to the QNX open-source ecosystem.
- Submit a new repository, created during the Submission Period, containing your porting or contribution work: the patches or porting layer, the QNX build files, build and run instructions, and your documentation. Reference the upstream project by URL rather than copying its history into your submission. Do not submit a fork of the upstream project.
See the official Rules for full details.
What to Submit
- A URL to your public code repository on GitHub, GitLab, or Bitbucket. It must contain all source code, assets, and build and run instructions needed to reproduce the project, and must show that the project genuinely builds for or runs on QNX 8.0, not merely that QNX 8.0 is named in the README.
- The repository must be public and open source, with an open-source license file detectable at the top of the repository page (About section).
- A text description explaining the features and functionality of your project.
- A demonstration video, under three (3) minutes. It should show the project functioning on the device it was built for, must be uploaded to YouTube and made public, and must not include third-party trademarks or copyrighted music unless you have permission to use them. Judges are not required to watch beyond three minutes.
- Build and run instructions specifying the QNX version, the target (hardware or QEMU), and the toolchain used.
- One category, selected on the submission form.
- For Open-Source Contribution & Ports submissions:
- The URL of the upstream project you ported or contributed to
- The URL of your pull request, if you opened one
- If you are entering the Best Codelab / Tutorial bonus prize, the URL of your codelab in the designated field on the submission form.
Evidence of QNX use. Your submission must explain how the project uses or supports QNX. Evidence may include QNX-specific source code or APIs; QNX libraries, headers, buildfiles, toolchains, system images, or configuration files in the repository; a demonstration running on QNX 8.0; or, for host-based developer tools, output or functionality specifically intended to build, analyze, test, deploy, debug, or manage software for QNX 8.0. This list is illustrative, not exhaustive. POSIX-compatible code, interpreted languages, ports of existing software, and tools that run on another operating system remain eligible when the submission clearly demonstrates a meaningful connection to QNX. Identify the relevant files, functions, output, or demonstration in your submission description so that reviewers can verify the QNX connection.
Prizes
Grand Prize
Code the Future Podcast episode
Coffee chat with John Wall (QNX CEO)
Best of Robotics & Medical
Coffee chat with QNX Senior Executive Team Member
Best of Automotive & Mobility
Coffee chat with QNX Senior Executive Team Member
Best of Low-level Software
Coffee chat with QNX Senior Executive Team Member
Best of Developer Tooling & Host Tools
Coffee chat with QNX Senior Executive Team Member
Best of Open-Source Contribution & Ports
Coffee chat with QNX Senior Executive Team Member
Robotics & Medical Runner-Up
Automotive & Mobility Runner-Up
Low-level Software Runner-Up
Developer Tooling & Host Tools Runner-Up
Open-Source Contribution & Ports Runner-Up
Honorable Mention
Best Codelab / Tutorial
Best use of QNX-specific Technologies
Community Choice
Blog and social feature
QNX swag
Devpost Achievements
Submitting to this hackathon could earn you:
Judges
Sheridan Ethier
VP, Engineering Middleware
Patrick Murtha
Senior Director, Product Management
Cris Sinnott
Senior Director Engineering, Open Source
Andy Gryc
Director, Developer Ecosystem
Dongkai Guo
Director, Software Development
John Dallas
Principal Academic Partnerships Manager
Morgan McKeen
Developer Engagement Marketing Manager
Mike Shane
Senior Systems Software Developer
John Hanam
Manager, Developer Relations
Judging Criteria
-
Technological Implementation
How well is the project built, and how effectively does it use QNX 8.0? Does the code reflect real engineering effort and a working, non-trivial implementation that genuinely builds for or runs on QNX? -
Design
Does the project deliver a complete, coherent product experience, not just a technical proof of concept? -
Potential Impact
Does the project make a credible, specific case for solving a real problem in a market QNX serves or wants to serve, and does it show why a real-time foundation like QNX is the right choice for it? -
Innovation & AI Creativity
Is this a creative, non-obvious use of QNX and does the team show genuine understanding of the problem space they're working in?
Questions? Email the hackathon manager
Invite others to compete
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
