Skip to main content

A humanoid robot and a robotic arm as an R&D platform

Open platforms with an SDK for prototyping and experiments: you take ready hardware and start testing algorithms instead of building a robot from scratch. We state explicitly which edition can be programmed.

Test your idea on real hardware, not only in simulation. You take a ready platform with an open SDK and iterate instead of building a robot from scratch. We state explicitly which edition can be programmed.

  • Rental · leasing · purchase
  • Open SDK (EDU and above)
  • Russian-language support
  • An isolated network segment on request

Getting started without a large purchase

A robot does not have to be a capital purchase up front. Start with rental or leasing: a monthly payment instead of a lump sum, and capital spending turns into operating spending.

Rental

Test a robot on your own task without putting an asset on the books.

  • An event, a season or a pilot at one site
  • No asset on your balance sheet, a quick start
  • Buyout is possible, terms are discussed
How rental works

Leasing

Put a robot to work now and pay in instalments. For companies, without a large payment at the start.

  • No one-off hit to the budget
  • A monthly payment, the robot works from day one
  • We help with the paperwork and the model
Leasing terms

Purchase

If the task is proven and permanent, take the robot into ownership with warranty and service.

  • Your own robot for a permanent task
  • Warranty support, commissioning and training
  • Service and spare parts after deployment
Purchase terms

The number one barrier in robotisation is not payback but the money up front. Rental and leasing remove it: you pay for the result by the month rather than for the hardware in full.

A monthly payment for a robot is often comparable to the salary of one front-line employee, and the robot works without sick days, holidays or turnover.

Common questions about this task

What is specific to the segment and where a robot's limits are. General questions about price, service and payback are answered on the home page.

Which edition do we need in order to program it for our own task?
Any work with the SDK requires the EDU edition or above. The base Air and Pro editions cannot be programmed — buy the wrong one and you will not get past teleoperation. The price gap between looking and developing is real, so we mark explicitly on the product page which edition gives open access to control.
What can actually be customised and what is locked in firmware?
More is open than it seems: the high-level API, locomotion, navigation, dataset collection, integration with LeRobot, Isaac Sim, MuJoCo, URDF. The low-level controller and the non-EDU editions are closed. The weak spot is precise manipulation on the move: for grasping and insertion the platform is a worse fit than for locomotion and datasets. We will say honestly where your task will land and where it will hit a wall.
Do the SDK and the examples work as documented or will we have to fix things?
Be ready for some fiddling at the start: a hard dependency on Python 3.10, CycloneDDS that can arrive broken, and examples that need manual SDK edits. The first days often go on setting up the environment rather than on the algorithm. We provide support in your language on exactly these snags, so you are not hunting for answers on forums for months.
Is it safe for a research institute with sensitive data?
The question is a critical one: vulnerable devices with access to their cameras have been found at universities in particular. For a research institute we are ready to deploy the robot in an isolated segment with no outside access and local-only control. We agree the isolation design to your security requirements before the deal.
How would you prefer a reply

R&D and research: send a request — we will suggest specific models and quote rental, leasing or purchase. Price on request.

Request a spec or talk to an engineer

[ purchase // rental // leasing ]