NEPI for Oregon UAS Accelerator Cohort 2026

Plug-and-play Edge AI software to help UAS teams rapidly prototype, test, and deploy flight-ready systems

Why NEPI Is Included in the Accelerator

Rapid prototyping to help teams get to a working solution faster

NEPI is included in the Oregon UAS Accelerator to shorten the time it takes teams to move from concept to a working, testable system.

Instead of spending early weeks building foundational software, teams are given NEPI as a shared baseline. This removes the need to create custom infrastructure for device communication, data handling, and system coordination during the accelerator.

Throughout the cohort, teams use NEPI as an experimentation layer. They connect sensors and cameras, run edge AI directly onboard during live flight tests, adjust system behavior between flights, and evaluate results immediately rather than waiting for post-processing.

NEPI does not replace existing tools or architectures. Teams can adopt it where it makes sense to reduce friction, accelerate iteration, and reach a validated solution sooner.

For teams who want a deeper technical overview of NEPI’s architecture and smart data capabilities, you can explore the NEPI white papers below:

As part of the Oregon UAS Accelerator, cohort companies receive access to:

  • A preconfigured NEPI software environment available via the NEPI Container

  • Plug-and-play support for common cameras and sensors

  • Built-in tools for AI, automation, and mission workflows

  • Example workflows relevant to UAS and field-testing use cases

  • Documentation and community support provided by the Numurus team

  • As part of the program, teams that provide structured feedback on their experience using NEPI will be eligible to receive a free commercial NEPI license.

This access is intended to give teams a practical, ready-to-use software foundation while still allowing flexibility in how NEPI is applied to each system.

 

What role does NEPI play in your system architecture?

NEPI acts as the integration and orchestration layer between sensors, onboard computing, AI models, and mission logic. It sits alongside your existing flight stack and payload software, handling data flow, automation, and edge AI execution without forcing you to redesign your system.

Do we have to commit to NEPI long term to use it in the accelerator?

No. NEPI is provided as a tool to accelerate development during the cohort, not a lock-in requirement. Teams can use it where it adds value and disengage or extend it after the program based on their own roadmap.

How does NEPI help with rapid prototyping specifically?

NEPI removes the need to build foundational software for:

  • Sensor and camera integration

  • Data routing and synchronization

  • Onboard AI execution

  • Automation and event handling

This lets teams focus on testing ideas in flight, adjusting behavior between runs, and validating use cases faster.

Can we run edge AI onboard, or is this just data collection?

NEPI is designed for onboard edge AI. Teams can run AI models directly on the vehicle during flight, trigger actions based on results, and evaluate outcomes immediately rather than relying only on post-processing.

Does NEPI replace our flight controller or autonomy stack?

No. NEPI does not replace flight control, navigation, or autonomy frameworks. It complements them by handling payload-side computing, AI, automation, and data orchestration.

How flexible is NEPI as our system evolves?

NEPI is built for iteration. Teams commonly adjust sensors, AI models, automation logic, and data workflows throughout the cohort without rebuilding integration code each time.

What hardware and compute platforms does NEPI support?

NEPI runs on common onboard compute platforms, including NVIDIA-based systems, and supports a wide range of sensors and cameras. The platform is hardware-agnostic and designed to adapt to different airframes and payloads.

Is NEPI only useful for computer vision use cases?

No. While many teams use NEPI for vision-based workflows, it also supports:

  • Multisensor fusion

  • Telemetry-driven automation

  • Event-based data capture

  • Mission logic tied to onboard analytics

How steep is the learning curve for teams new to edge AI?

NEPI is designed so teams don’t need to be edge-AI experts to get started. Much of the integration and orchestration is already handled, allowing teams to focus on applying models and testing behavior rather than building infrastructure.

What kind of data does NEPI help us collect?

NEPI supports structured, time-synchronized data collection across sensors, AI outputs, and system events. This makes it easier to evaluate performance, compare test runs, and support reporting during and after the cohort.

Where can we learn more or go deeper technically?

Teams can explore documentation, tutorials, and examples on the NEPI website:
👉 https://nepi.com

Get Started With NEPI

NEPI Step-by-step process:

  1.  Visit the NEPI Container page and follow the step-by-step instructions to install and run the NEPI container.

  2.  Create an account on the NEPI Community page to access documentation, ask questions, and share feedback with the NEPI team.

  3.  Join the NEPI Discord channel for quick questions and discussion with other companies in your cohort.

  4. Use NEPI during the cohort as a common software foundation throughout the accelerator to support sensor integration, onboard AI, and mission automation as your system evolves.

  5.  Complete the short feedback survey to receive a free commercial license.

                         *This program is available exclusively to the registered 2026 Oregon UAS Accelerator Cohort *