Platform
The operator layer on top of the robot stack you already have
Volant is built on ROS 2 and the same open ecosystem as NVIDIA Isaac ROS — designed for the plant manager or foreman, not the robotics engineer.
Your safety rules and facility layout stay yours. Volant only ever proposes actions inside them.
Operator runtime, not developer tooling
Isaac ROS 5.0 brings agentic AI tools to robot developers — helping engineers write and customize robot software faster. Volant is built for the operator: runtime instructions in plain language, simulated first, with a human-approval gate before anything physical happens. We sit on top of that ecosystem. We do not replace it.
How it works
A numbered path from intent to fleet — with a human approval gate before anything physical happens.
- 01
Describe the task
An operator gives a plain-language instruction. No ROS, no vendor IDE, no code.
- 02
Task graph generated
The system composes certified primitives — pick, place, navigate on the ground; takeoff, patrol, formation, geofence in the air.
- 03
Safety validation
Every graph is checked against the facility’s own safety zones and hardware limits. Your rules stay yours; Volant only proposes inside them.
Calculate what this saves on your line → - 04
Simulation run
Physics, collision, and timing are checked before anything touches the real robot or drone.
- 05
Human approval
A video preview and a diff of what will change. Nothing executes without sign-off.
Calculate what this saves on your line → - 06
Deployment
The graph compiles to vendor-specific commands — ROS 2 for ground, MAVLink / PX4 for air — and pushes to the fleet.
- 07
Fleet monitoring & flywheel
Real-world outcomes feed a shared skill library so the next instruction starts from verified behavior, not a blank slate.
Calculate what this saves on your line →
Cross-vendor by design
A conceptual abstraction layer compiles approved task graphs to each vendor’s native command path. Implementation details stay internal. What you see is a consistent operator workflow across mixed fleets.
Questions we hear from technical buyers
Does this replace ROS?
No. Volant is built on top of ROS 2 for ground systems. It does not fork, replace, or compete with the robotics middleware you already run.
What hardware does it support?
Vendor-agnostic by intent: humanoids, AMRs, and industrial arms on the ground; PX4 / MAVLink-class drones in the air. Support lands through the compile step, not a single OEM lock-in.
How is safety verified?
Facility rules and hardware limits you define, then simulation, then a human approval gate. See the safety & compliance page for how this is designed to align with EU regulation. →
How is this different from NVIDIA’s own agentic tools?
Those tools accelerate developers who write robot software. Volant is the operator layer at runtime: describe, simulate, approve, deploy — without a ROS or coding background.
ROI calculator
A conservative estimate of hours and cost returned to your team. Transparent math — not a sales gimmick.
Estimated hours saved / month
85.6 h
Estimated cost saved / month
€5,566
Assumptions (conservative): 40% of reprogramming hours returned; 25% of unplanned downtime hours avoided. 4.33 weeks/month. Figures are directional estimates, not a guarantee.