About ESPFlight

A starting point for learning, building, and creating.

ESPFlight began with a technical challenge: build a capable flight-control stack around accessible ESP hardware. The bigger idea came from a simple question—could that work become a practical starting point for anyone who wants to understand, experiment with, and build an ESP-based drone?

Learning is easier when the basic pieces already work together and can still be opened, studied, changed, and understood.

Flight control, hardware integration, networking, telemetry, configuration, safety behavior, and a companion application all take time to make work together. ESPFlight brings those layers into one platform so enthusiasts, students, teachers, instructors, Makers, developers, and engineers can begin with a coherent foundation instead of a collection of disconnected parts.

The goal is not to turn learning into simple assembly. Builders should be able to inspect the design, change the board, change the frame, test different ideas, understand the results, and eventually create solutions that are genuinely their own.

“Learn from it. Experiment with it. Build it. Make it your own.”

For some people, the journey ends with learning, experimentation, teaching, or a personal project. Others may choose to take a mature design further and turn it into a kit or product under an independent brand. ESPFlight keeps that path open without making selling the purpose of the platform.

Four principles

Open where freedom matters. Structured where compatibility matters.

01

Don’t start from zero

Firmware, reference hardware, and the companion app provide a coherent starting point instead of three disconnected projects.

02

Learn by building

Use the working stack to understand real flight hardware and software, then change it deliberately as your knowledge and ideas grow.

03

Keep the foundation inspectable

The embedded core and reference hardware should stay understandable and adaptable so makers can learn from them and build beyond them.

04

Leave room to go further

A project can remain educational or personal for as long as you want. If it later becomes a repeatable kit or product, you can use your own independent brand and choose to sell it under the applicable licenses and Brand Policy.

What success looks like

More learning. More experimentation. More things built.

Success is not an ESPFlight-branded drone or official kit. It is people learning how these systems work, building real drones, sharing knowledge, creating new designs, and taking their projects as far as they choose.

01Builder startsUse ESPFlight as a working foundation and learn how the stack fits together.
02Ideas evolveExperiment, modify the design, and create something that fits your own goals.
03Knowledge spreadsProjects, lessons, feedback, and compatible builds bring more people into the ecosystem.
04Platform improvesFeedback, contributions, and real-world use help guide the next iteration.

ESPFlight should enable builders, not define their final result.

ESPFlight stays underneath as the platform. If a builder chooses to create a kit or product, that creation can use its own independent name and brand, and it may be sold without turning ESPFlight itself into a hardware-kit brand.

Start buildingFor Makers