Build first. Partner when it helps.
You do not need Partner status to use ESPFlight. If a project grows from learning and experimentation into a kit or independent product, the Founding Partner Program can be an optional next step for builders who want a closer connection to the ecosystem.
For the people building what comes next.
PARTNER Launch cohort
You can start small. That is the point.
The first ESPFlight partners do not need an established brand or a finished product. The program is open to serious builders who are developing something real and would benefit from a closer relationship with the platform.
Still exploring an idea?
Tell us what you want to build, what you are trying to learn or solve, who it is for, and why ESPFlight fits. A working prototype is not required to start the conversation.
Already building?
Bring the prototype, rough board, or early design. This is the ideal point for compatibility guidance and practical feedback.
Turning it into a kit or product?
If your hardware is becoming a repeatable kit or independent product, partnership can add compatibility guidance, closer communication, and ecosystem visibility.
Founding partners receive founding benefits.
For the first ESPFlight Partner cohort, any benefits, discounts, fees, or brand permissions will be stated clearly before acceptance. Submitting an application does not itself create a partnership, benefit, or brand permission.
- Founding Partner recognition Be part of the first official ESPFlight partner cohort.
- Launch-cohort benefits Any special launch benefits or fees are disclosed before you make a commitment.
- Early product visibility Priority consideration for the ESPFlight Partner and ecosystem product directory.
- Compatibility guidance Closer feedback while you move from prototype toward a reliable product.
- Closer technical channel A more direct path for product-level ESPFlight questions and integration issues.
- Launch support Opportunities for ecosystem announcements and product visibility when appropriate.
- Authorized brand use Approved Partners may receive permission to use “Powered by ESPFlight” and official Partner marks under the Brand Policy.
Freedom stays the baseline.
ESPFlight should remain useful even if you never join the Partner program. Partnership adds a closer relationship; it does not remove the open path.
Swipe horizontally to see all columns.
| What you can do | Independent maker | ESPFlight Partner |
|---|---|---|
| Build with open ESPFlight components | ✓ Yes | ✓ Yes |
| Modify and optionally sell under your own brand | ✓ Yes | ✓ Yes |
| Use the free companion app | ✓ Yes | ✓ Yes |
| Official Partner recognition | — | ✓ Included |
| Partner product visibility | Community path | ✓ Priority path |
| Closer product-level guidance | Public resources | ✓ Partner channel |
Tell us what you want to build.
Keep the first application lightweight. We mainly want to understand your project, where you are today, and how ESPFlight could help you get to the next stage.
Idea, prototype, kit, or product — all are welcome.
There is no advantage in pretending to be further along than you are. Tell us your real stage and what you are trying to make.
Open Partner applicationV1.0 Partner intake is not open yet. When the official application form becomes available, its link will be published on this page.