NEPI software

The software platform for edge AI.

The fastest way to run NEPI is on a NEPI-ready S2X system, with NEPI installed and the license included. Already have hardware? Install NEPI on it below.

Wildfire detected in satellite imagery with location and size readout Tuna detected and measured in an underwater camera feed Crane sheave identified on a construction crane Wear detected on a wind turbine blade with measurements Person and vehicle located in snow by a search and rescue drone camera Weld undercut measured on a pipe inspection image Drone tracked in flight with bearing and speed readout Red buoy detected at sea with range and bearing Corrosion area measured on a storage tank Navy ship tracked at sea with range and bearing
NEPI-ready hardware

Start on NEPI-ready hardware with the license included.

Connect your sensors and open the browser interface on day one. Nothing to install.

NEPI + license included

S2X-RPI5

Raspberry Pi 5
From $513.15

An affordable, compact NEPI edge AI computer. Add a Hailo-8 accelerator for 26 TOPS of real-time vision.

See S2X-RPI5
NEPI + license included

S2X-ONX

NVIDIA Jetson Orin NX 16GB
From $1,812.65

A mid-range NEPI system with 100 TOPS of NVIDIA Orin NX performance for demanding vision and robotics.

See S2X-ONX
NEPI + license included

S2X-AGX64

NVIDIA Jetson AGX Orin 64GB
From $4,233.69

NEPI's highest-performance system, with 275 TOPS and 64 GB of unified memory for the most demanding multi-sensor AI.

See S2X-AGX64
Install

Install on hardware you already have

Two ways to run NEPI on hardware you own.

NEPI Container Recommended

Evaluating, prototyping, your own hardware

A Docker image with drivers, AI frameworks, automation tools, and the browser UI already built. Runs on any Linux machine in minutes. Needs about 60GB of free disk.

Get the Container

Source code

Teams that need to change the platform itself

Clone the full NEPI source from GitHub. Build it, modify it, and deploy on your own hardware and timeline. Requires a Linux build environment and familiarity with ROS.

View on GitHub
Licensing and pricing

Free until you ship. $100 per device when you do.

These tiers are for NEPI installed on hardware you own. S2X systems are priced on the hardware page.

Every tier includes the full NEPI platform, source code access, documentation, tutorials, and the community forum.

Evaluate and build

Source-available

$0
Free forever
  • Commercial use allowed
  • Community forum support
  • Not included: Support plan
Get started
Teach and compete

Educational

$0
Free
  • Classroom and competition use
  • Community forum support
  • Not included: Shipping in commercial products
Request a license
Run a fleet

Enterprise

Request Quote
  • Volume licensing
  • Priority and enterprise support
  • Integration help from our engineers
Request a quote

Educational licenses are for non-commercial use and cannot ship in commercial products. Prices in USD.

Before you buy

Licensing questions

What teams ask before choosing a tier. Product questions are on the full FAQ.

Yes. NEPI is source-available and the full code is on GitHub. You pay $100 per device when you ship NEPI inside a commercial product. Enterprise adds volume licensing and support.
One Professional license covers one unit running NEPI in the field. Development and test machines are covered by the free Source-available tier.
Yes. Universities, labs, and teams that cannot use a card can request a quote and pay by PO or invoice. Use the Request a quote or Contact sales button, or the contact page.
Classrooms, student competition teams, and academic labs using NEPI for teaching or research. It cannot ship in commercial products. Request one and we will confirm eligibility.
No. Every S2X system ships with NEPI installed and licensed. These tiers only apply to hardware you supply yourself.
Start with the Container. It is the same platform, pre-built. Build from source only if you need to modify NEPI itself.
Ocean Aero Argus autonomous vessel on display, with its folding solar wing raised Ocean Aero vessel at sea with its camera mast
Built for the field

Deployed underwater, at sea, and on working vessels

Ocean Aero integrated five directional cameras with onboard AI in six months. WESMAR shipped next-generation AI sonar for commercial fishing in five. VideoRay runs ROV incident-response inspection with SeeByte AI on it.

"It saved our internal team from a lot of development work we'd otherwise have to do ourselves."

Kevin Decker, CEO, Ocean Aero
  • Ocean Aero
  • WESMAR
  • VideoRay
  • University of Washington Tacoma
  • Lane Community College
Why teams build on NEPI

The parts every smart system needs, and nobody wants to write twice

A smart system takes in data from the real world, makes a decision with AI, and acts on it. Before any of that works, someone has to build the layer underneath. That layer is NEPI.

ComponentBuild it yourselfOn NEPI
Sensor driversOne driver per camera, sonar, lidar, GPS, light, or pan and tilt. Rewritten when the hardware changes.Plug-and-playGrowing driver library, configured in the browser
AI model deploymentConvert the model, wire it to live frames, manage versions, publish results somewhere useful.Model managerDetection, classification, segmentation, pose. YOLO family supported
Automation logicCustom code that watches outputs and triggers actions. Hard to change in the field.Event-driven scriptingLow-code rules: detect a condition, trigger an action
Data logging and syncTimestamps, storage, synchronized streams across sensors and model outputs.Structured collectionSynchronized logs, ready for review or training
Operator interfaceA UI for configuring hardware and watching the system, built after everything else.Browser-based UIConfigure, deploy, and monitor from any browser on the network
ROS plumbingNode graphs, message types, launch files, and the glue between all of the above.Built on ROS and ROS 2Keep your existing nodes. NEPI adds the layers ROS does not have
TotalMonths, then yours to maintainIncluded. You write the 10% that is yours.
How it works

Connect sensors. Run AI on the data. Trigger an action.

Everything runs on the device. No cloud connection required, which is the point when the device is underwater, at sea, or on a working vessel.

Sensors in

  • Cameras, visual and IR
  • Sonar and lidar
  • GPS and INS
  • Pan and tilts, lights, robots

NEPI, on the device

  • Hardware drivers
  • AI model management
  • Event-driven automation
  • Data collection
  • Browser interface
  • Your 10%: low-code scripts and your own ROS nodes

Actions out

  • Alerts and events
  • Logged, synchronized data
  • Device control: point, track, record

Before Windows, only computer scientists could use computers. Windows gave everyone an interface, built-in apps, and hardware that just worked. NEPI does the same for edge devices.

The point is access. Researchers, program leads, educators, and operators can run real AI on real hardware without a specialized engineering team.

In the browser

Every sensor, model, and rule in one place

Open the NEPI interface from any browser on the network. Connect hardware, load a model, write a rule, and watch it run. The screenshots below are the actual interface.

NEPI image viewer showing color, depth, point cloud, and AI alert streams from a stereo camera
Image viewer Color, depth, point cloud, and AI alert streams from one stereo camera, side by side.
NEPI AI model manager with YOLOv8 and YOLOv11 frameworks and a list of active and disabled models
AI model manager Enable a framework, pick a model, connect it to a stream. Swap models without rebuilding anything.

Runs on

NVIDIA Jetson (Nano through AGX Orin), Numurus S2X hardware, and any Linux machine with Docker.

Model formats

TensorRT, ONNX, and PyTorch. Detection, classification, segmentation, and pose estimation. YOLO family supported.

If your hardware is not listed

The driver framework lets you write a custom driver that works with the rest of the platform. Check the documentation for the current list.

Ready to try NEPI?

Install in minutes. Free to try. No hardware needed.