An open-source autopilot stack for drones and unmanned vehicles, supporting multicopters, fixed-wing, VTOL, rovers, and more.
PX4 is an open-source autopilot software stack that provides flight control and navigation for drones and other unmanned vehicles. It solves the problem of needing a reliable, flexible, and vendor-neutral flight control system by supporting a wide range of vehicle types—including multicopters, fixed-wing aircraft, VTOLs, and rovers—across various hardware platforms.
Drone developers, robotics engineers, researchers, and companies building or integrating unmanned vehicle systems who need a robust, customizable autopilot solution.
Developers choose PX4 for its modular architecture, extensive hardware support through the Pixhawk ecosystem, and strong integration with tools like MAVLink and ROS 2. Its unique selling point is its vendor-neutral governance under the Dronecode Foundation, ensuring a community-driven project with a business-friendly BSD license.
PX4 Autopilot Software
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built around the uORB publish/subscribe middleware, enabling fully parallelized, thread-safe modules and highly customizable configurations as emphasized in the architecture section.
Supports a wide range of autopilot boards and sensors through the Pixhawk ecosystem, documented in the hardware support list and airframe reference.
Offers first-class MAVLink and DDS/ROS 2 integration, plus comprehensive SITL simulation and hardware-in-the-loop testing tools, facilitating efficient development and debugging.
Governed by the Dronecode Foundation under the Linux Foundation with a BSD license, ensuring open collaboration and no single-vendor control over the roadmap.
Some supported vehicle types like helicopters and experimental platforms have only basic support and are not part of the regular flight-test program, as admitted in the airframe reference.
Requires recursive cloning, specific toolchains, and configuration steps that can be daunting for newcomers, especially without embedded systems experience.
Heavy reliance on the Pixhawk standard may limit flexibility with non-standard or proprietary hardware, potentially increasing integration efforts for custom projects.