Every Yantra robot runs on the same autonomy stack: multi-sensor navigation, a mixed-fleet scheduler, building control and open APIs. Add a forklift next to your delivery robots, and they share one map and one dispatcher.
Maps are built and edited from a phone, tablet or PC, and can be updated while the robots keep working.
Once a robot is connected, our engineers can build and annotate 2D/3D maps remotely, which cuts site visits and speeds up support.
When part of the layout changes, the map is updated for that area only, with no full re-map and no downtime for the rest of the site.
New features, fixes and map changes roll out remotely, with fault early-warning and traceable logs.
Go-live still includes station setup, task configuration, on-site testing and any lift or door commissioning. Timelines depend on site size, network and project scope.
One scheduler dispatches delivery robots, lift-and-carry AMRs, towing robots and forklifts together on the same map, so mixed fleets work as one system.
RoboCarry, RoboBase, RoboTow and RoboLift scheduled side by side, each matched to the jobs it suits.
Intersections, narrow corridors and two-way lanes are reserved for one robot at a time, which keeps the fleet from blocking itself.
Routes are recalculated around congestion in real time, and robots queue at workstations in the right order.
If a drop spot is occupied, the task pauses and resumes automatically as soon as it's free.
Battery levels are tracked live and robots are sent to charge below a threshold you set, so the fleet never runs flat.
Cloud dispatch for big sites, a local scheduler on-premises, and direct robot-to-robot messaging where there's no network.
With the right control modules installed, robots move through your building as freely as your staff do.
Each integration needs a compatibility check, any required installation, and coordinated testing during commissioning.
Keep your WMS, MES and ERP. Robots receive tasks from them and report results back, through open interfaces.
Receiving, dispatch and replenishment in the warehouse; line-side delivery driven by production demand; orders and plans tied to logistics.
REST APIs for requests and commands, WebSocket for live position and status, plus SDKs and examples in JavaScript, Java and TypeScript.
Support for the VDA 5050 standard (over MQTT) on supported models, for multi-brand fleets under one master control system.
Your MES sees a workstation running low on material.
It creates a transport request and sends it through the API.
The scheduler picks the best robot and sends it to the pickup point.
The robot carries the material to the station. Loading can be manual or automated with rollers or lifts.
Completion flows back to your MES, which updates its records.
| Level | Typical need |
|---|---|
| Operate & configure | Set stations, tasks and delivery flows. No coding. |
| System integration | WMS or MES sends tasks and receives status and results. |
| Apps & equipment | Custom tablet or robot-screen apps, conveyor or top-module hand-offs. |
| Low-level | Navigation, motion or safety changes. Scoped and approved separately. |
Remote monitoring, dispatch and analytics with nothing to host yourself.
The scheduler runs on servers in your facility, so data stays on your network.
Robots and local servers run without an internet connection where your security policy requires it.
No. Day-to-day use runs on the supplied interface and task tools. Developers are only needed to connect enterprise software, build a custom interface or add equipment integrations.
Yes. Integration covers task submission, status queries and result reporting. Both teams first agree the workflow, data fields, network and exception handling, then develop and test.
We can scope branded interfaces and custom apps, including logos, screens and operating flows, depending on the device and the functions you need.
Custom development is done through the open APIs, SDKs and tools. Access to core algorithms, system-level changes and special functions is agreed separately for each project.
Yes. A demo unit is a good way to learn mapping, task setup and API calls, and to prove one representative use case before a wider rollout.
Describe one complete transport task: where the load is picked up, where it goes, who loads and unloads it, and which system needs the completion status. Add your existing systems, network conditions and timeline, and we'll agree scope, responsibilities and acceptance tests.
Tell us which systems you run and which jobs you want automated, and our team will outline the integration path.