Deploy at Scale
with DEEPX
One-Line Migration from Isaac ROS
Swap a supported Isaac ROS package for its DX-Newton equivalent. Keep the same ROS 2 topics, messages, launch structure, and downstream nodes.
Production-Ready Edge Efficiency
Bring your ONNX or supported PyTorch models into DXNN and move inference to a DEEPX NPU in hours.

Keep the Graph
DX-Newton provides drop-in alternatives for supported Isaac ROS perception nodes. Change the package name while keeping the node graph, plugin settings, and parameters intact.

Not a Fork
Built on standard ROS 2 topics, message types, QoS profiles, and remappings. Keep using familiar tools such as RViz 2, ros2 bag, and ros2 topic.

From Sim to Robot
Validate the node graph in simulation, then reuse the same launch structure on the robot. DX-Newton routes inference to DEEPX hardware at runtime.

Rework
Nav2, planners, controllers, and custom subscribers keep receiving the same ROS 2 messages. Replace the perception node without rewriting the rest of the stack.
Reference GPU Platform VS. DEEPX NPU
Same Perception Task.
A Fraction of the Power.
Across the benchmark configurations shown below, DX-Newton runs supported robotic-perception workloads on the DEEPX NPU with comparable task performance and substantially lower accelerator power than the referenced GPU platform.
- Active Cooling
- Passive Cooling
- Active Cooling
- Passive Cooling
- Active Cooling
- Passive Cooling
- Active Cooling
- Passive Cooling
- Active Cooling
- Passive Cooling
- Active Cooling
- Passive Cooling
- Active Cooling
- Passive Cooling
- Active Cooling
- Passive Cooling
- Active Cooling
- Passive Cooling
- Active Cooling
- Passive Cooling
- Active Cooling
- Passive Cooling
- Active Cooling
- Passive Cooling
*GPU: Power (W), Temp (°C) (Published Reference) | DEEPX: Power (W), Temp (°C) (Simulated Estimate)
*GPU figures are based on publicly available specifications and benchmark data.
*DEEPX figures are simulation-based engineering estimates.
Full Stack Architecture
Replace the Engine, Not the Robot.
For supported packages, update the package reference in your launch file while preserving the ROS 2 node graph, topics, message types, parameters, and downstream interfaces.
Backend selection, execution policies, and accuracy validation. Switch supported compute backends without redesigning the ROS 2 application graph.
- Model Compatibility Inspection
- Pre/Post-Processing Contract Validation
- ROS 2 Interface Compatibility Check
- Backend Health Check and Safe Fallback
- Perf. & Power and Accuracy Validation
Built for Robots That Have to Ship.
Across humanoids, industrial robots, mobile robots, service robots, and drones, power, thermal design, and compute cost determine whether an AI prototype can scale into a production-ready system.
cooling used to occupy.
automation within tighter power, thermal, and cost budgets.
and longer operation between charging cycles.
lobbies, hospitals, stores, and other human-centered spaces.
translate into more payload capacity or longer mission time.
Silicon Platforms
One DX-Newton Interface.
From Perception to Multimodal AI.
Accelerate object detection, segmentation, pose estimation, tracking, and re-identification on the DX-M1 NPU through DX-Newton.
Talk to the DX-Newton Team.
Whether you are evaluating model compatibility, planning a ROS 2 deployment, or exploring a production partnership, tell us about your project and we will connect you with the right DEEPX team.
integration, and performance benchmarking.
technology partnerships.