For research and development projects, the first thing to check is whether the specific robot configuration offers the software, sensor and data access you need – not what movements it can perform. The Unitree G1 EDU may suit development work where access depends on the variant, while Reachy 2 is designed for mobile manipulation and teleoperation. For THORMANG3, its documented Ubuntu 16.04 and ROS Kinetic environment is a key integration consideration. Before ordering, teams should also clarify data rights, service arrangements and which German-language documents are required for the specific delivery format.
Your research goals determine which type of development access and robot design will work for your project.
If you’re testing perception, motor control or whole-body control on physical hardware, you’ll need access to the right actuators and sensors, as well as a route to simulation. Unitree Robotics documents development resources for G1, but their availability must match the configuration on offer.
For experiments involving bimanual manipulation, camera feedback and recorded movements, data access matters just as much as control. Pollen Robotics documents VR teleoperation for Reachy 2, along with SDK features for camera images and trajectories.
Teams with in-house ROS and Linux expertise can integrate a sensor-rich platform into their research environment. For THORMANG3, this means checking the Ubuntu 16.04 and ROS Kinetic setup documented by ROBOTIS against your lab’s existing IT infrastructure.
First, choose the type of robot that suits your experiment, then check the development access available for the exact variant. Renting may also be an option for a time-limited pilot, but only if the contract grants the development, administrator and data rights you need.
Consider it: if you want to investigate motion control or perception using a G1 development configuration. Unitree Robotics documents G1 SDK interfaces for this purpose.
Key limitation: Access is not automatically available with every retail G1 variant; one Joybuy listing explicitly states that SDK/API access is currently unavailable.
Consider it: if your work focuses on mobile bimanual manipulation, human–robot interaction or demonstration data. Pollen Robotics describes Python, ROS 2 Humble and VR teleoperation.
Key limitation: Reachy 2 is a mobile manipulator, not a bipedal walking robot. The SDK connection also requires the computer and robot to be on the same network.
Consider it: if your experienced ROS team can integrate a large-scale platform for locomotion, manipulation or sensor-based research.
Key limitation: ROBOTIS documents Ubuntu 16.04 and ROS Kinetic as the development environment. A migration and security plan is important if your lab has newer IT infrastructure.
| Requirement | What to check before buying | Who should pay particular attention |
|---|---|---|
| Development access | Ask the supplier to confirm the SDK or API level, ROS version and simulation support for the exact model and firmware variant. | If I want to programme movements myself, access needs to go beyond a demonstration. Around 36 % of buyers put development access first. |
| Teleoperation and data | Clarify the local network connection, as well as the rights and export options for image, state and motion data. | For demonstration data, I need usable recordings as well as remote control. Around 29 % of buyers prioritise teleoperation and data access. |
| Suitability for the experiment | Match the robot’s form, hand and sensor configuration to your planned measurement or manipulation task. | A mobile manipulator won’t help with an experiment on bipedal locomotion. Around 21 % of buyers give the highest priority to the robot’s design and sensors being right for the task. |
| Operation and documentation | Check the required computers and power supply, software maintenance, service arrangements and which German-language documents apply to the delivery format. | If my lab is to operate the platform over the long term, the supporting infrastructure needs to be sustainable too. Around 14 % of buyers focus primarily on operating and procurement requirements. |
Unitree Robotics documents a G1 SDK for development, but a Joybuy listing for a retail G1 model states that SDK/API access is currently unavailable. A similar model name does not prove that development rights are the same.
Ask for written confirmation of the model designation, EDU configuration, firmware, SDK scope, sensor access and licence rights for the specific offer.
For Reachy 2, Pollen Robotics describes a local SDK connection and features for camera images and trajectories. This does not tell you which raw data a lab may use, export or retain, or which additional features require remote access.
Before your pilot, request a description of the data flows for camera images, motion data, logs and remote support, together with the associated usage rights.
Network segmentation and managing recorded data may require additional work in the lab.
ROBOTIS documentation for THORMANG3 specifies Ubuntu 16.04 and ROS Kinetic. If you use a newer ROS environment, don’t assume compatibility based on general ROS support alone.
Check drivers, dependencies and security responsibilities as part of a migration plan, and prepare a bill of materials for your chosen operating setup.
A control PC and, for external power, additional power supplies may need to be purchased separately. Porting will also take development time.
Under Section 2 of the MaschinenDG, as published by the Federal Ministry of Justice, machinery and related products within its scope must have, among other things, instructions for use, safety information and an EU declaration of conformity drawn up in German. Which documents apply depends on the classification and delivery format of the specific product.
Clarify the product’s classification before you buy, and have the German-language documents required for the specific offer checked.
The G1 range includes different configurations, so the exact version matters for development projects.
Reachy 2 is a mobile, humanoid-style manipulation platform for development and teleoperation experiments.
THORMANG3 is a large-scale research platform with ROS-related development resources.
Not simply because it is being used for research. Section 2 of the MaschinenDG, as published by the Federal Ministry of Justice, specifies German-language instructions for use, safety information and EU declarations of conformity for machinery and related products within its scope. For partly completed machinery, the documents specified there for assembly and installation apply. You’ll need to clarify before buying which category covers the specific model and its delivery format.
Yes. Pollen Robotics describes an SDK connection using the robot’s IP address, provided the computer and Reachy 2 are on the same network. This confirms local SDK access, but not that updates, diagnostics or all teleoperation features will work without additional services.
Teams shouldn’t assume that it will integrate directly: ROBOTIS lists Ubuntu 16.04 and ROS Kinetic as the documented development environment for THORMANG3. Before buying, check drivers, dependencies, package maintenance and responsibility for security updates in your planned ROS 2 environment.
No. Unitree Robotics documents SDK features for the G1 development environment, while a Joybuy G1 listing states that SDK/API access is currently unavailable. Ask for written confirmation of development permissions, SDK version, API scope, firmware and data rights for the exact variant in the offer.
According to the ROBOTIS product page, a control PC may need to be supplied separately. If you use an external power supply instead of a battery, separate power supplies for the PC and actuators may also be required. Check what’s included and how you plan to operate the robot before deciding on your lab infrastructure.