Learn from it. Change it. Build your own.
ESPFlight is designed to give enthusiasts, students, educators, Makers, developers, and engineers a working foundation they can understand, modify, and turn into their own ideas.
Learn. Experiment. Build. Create.
Use ESPFlight for a first build, a classroom or university project, a technical experiment, or a custom design. The platform is meant to help you learn by doing without forcing everyone toward the same outcome.
Firmware is licensed under the MIT License and the hardware reference under CERN-OHL-P-2.0. ESPFlight names, logos, “Powered by ESPFlight,” and Partner badges are separate brand identifiers. If you later publish or sell an independent kit or product, use truthful descriptive wording such as “Compatible with ESPFlight” unless specific brand authorization has been granted. Read the Brand Policy.
A platform underneath your ideas.
ESPFlight does not sell an official kit or hardware product line. You can use the reference as a learning tool, a starting point for custom hardware, or the foundation for a later independent kit or product.
Take it further when you are ready.
If a project becomes reliable and repeatable, you can choose to turn it into a kit or product under your own independent brand and sell it. Partner status is optional; the Founding Partner Program simply offers a closer ecosystem relationship for builders who find that useful.
Explore Founding PartnersFrom first build to your own creation.
Learn
Build from the reference stack and understand how the hardware, firmware, and app work together.
Experiment
Change the board, frame, components, configuration, or use case and observe what changes.
Build
Turn the experiment into a reliable implementation and validate behavior, compatibility, and safety.
Create
Develop a board, kit, teaching platform, or project that reflects your own goals and identity.
Go further
Keep it personal, share it, teach with it, or create an independently branded kit or product and choose to sell it.
Start with curiosity, not a contract.
Learn and build first. The documentation should make the technical path clear; everything beyond that is your choice.