Robotics software
Software for robot arms, mobile robots and fleets, built on ROS 2 and tested in simulation first.
01 · Build
What we build
A robot cell is software meeting heavy hardware and people. We build on ROS 2, with MoveIt 2 for arms and Nav2 for mobile robots, test every behaviour in Gazebo or Isaac Sim before it moves real metal, and integrate the cell with PLCs, conveyors and safety-rated stops.
- ROS 2 nodes for perception, planning and control, with MoveIt 2 and Nav2
- Simulation in Gazebo or Isaac Sim before code runs on hardware
- Fleet management for mobile robots over VDA 5050
- Cell integration with PLCs, conveyors and safety-rated stop signals
- Collaborative tasks designed within ISO 10218 and ISO/TS 15066 limits
- Logs, replays and metrics recorded for every run in the cell
02 · Demo · sample data
Try it live.
A working sample with made-up data. It runs in your browser; nothing is sent anywhere.
- AMR-01 · AMR 1 · to dock 3moving
- AMR-02 · AMR 2 · chargingidle
- AMR-03 · AMR 3 · aisle blockedalert
- AMR-04 · AMR 4 · to pickingmoving
- ARM-01 · Cobot 1 · palletisingmoving
- ARM-02 · Cobot 2 · person in zoneidle
03 · Features
What it does well
- 01
Simulation first
Every new behaviour runs in simulation against the cell model before it runs on hardware.
- 02
Replayable runs
Sensor data and decisions are recorded, so any failure can be replayed and examined.
- 03
Vendor-neutral fleets
Mobile robots from different makers are dispatched through one VDA 5050 interface.
- 04
Safety in hardware
Safety functions stay in rated hardware and PLCs; software never replaces a safety stop.
- 05
Cycle-time tracking
Every pick, move and wait is timed, so the slowest step is always known.
- 06
Recovery paths
Dropped parts, blocked aisles and lost localisation each have a defined recovery.
04 · FAQ
Questions
Who signs off the safety of the cell?
Your safety engineer or integrator does, through the risk assessment and validation the standards require. We design the software within ISO 10218 and ISO/TS 15066 limits, supply the information the assessment needs, and keep safety functions in rated hardware, not in our code.
Which robots do you work with?
Arms and mobile robots with ROS 2 drivers or open interfaces, including Universal Robots, ABB, KUKA and FANUC arms through their supported interfaces, and AMRs that speak VDA 5050. We confirm driver support for your exact model before any work starts.
Why simulate first?
Because a mistake in simulation costs a restart, and on hardware it can cost a gripper, a part or a stop of the line. Simulation also lets us test edge cases you cannot easily stage, such as a box half off the conveyor or a person entering a zone.
05 · Services
Services that go with it
- ServiceCustom software developmentSoftware designed and built around the way your business works, shown to you working at every review.
- ServiceSystems integrationYour business systems connected so orders, customers and stock move between them without retyping.
- ServiceGo-live supportA planned, rehearsed launch with engineers watching and ready to fix issues through the first days live.
06 · Software
Related software
- SoftwareComputer visionCamera-based software that inspects, counts and detects, running on edge devices beside the camera or in the cloud.
- SoftwarePLC and SCADAControl logic, operator screens and plant data links, from the PLC to the historian and the MES.
- SoftwareEdge AIModels that run beside the machine or camera, measured on the device, with no round trip to the cloud.
- SoftwareManufacturing softwareShop-floor systems that connect machines, work orders, quality checks and stock to show production as it happens.