Preparing the published article.
Leju Robotics: KUAVO Humanoids, Research Software and Industrial Applications
Shenzhen robotics company developing KUAVO humanoids and research tools. Compare current generations, supported software interfaces and application evidence before specifying a deployment.
Company and development
Leju Robotics is a Shenzhen robotics business established in 2016. Its company filing records the predecessor's incorporation on 24 March 2016 and conversion to a joint-stock company in September 2025. These are separate milestones. KUAVO is its full-size humanoid family; the website also presents smaller humanoids and educational products.
Current KUAVO lineup
The current official website lists KUAVO 4Pro and KUAVO 5 / 5-W. A purchasing specification should identify the exact generation and configuration, including hands, onboard computing and supplied accessories. Historical KUAVO-MY descriptions should not be used interchangeably with current models. Ask for the dated configuration sheet accompanying the quotation.
ROS development and simulation
Leju's public kuavo-ros-opensource repository documents robot control and simulation using MuJoCo, Gazebo and Isaac Sim. It requires the configured robot version and total mass to match the actual machine. End-effector choices also need explicit configuration. Simulation support provides a development route; it does not establish equivalent physical performance.
LejuLab and SDK scope
The separate LejuLab-Deploy project describes reinforcement-learning deployment, MuJoCo simulation and physical control for specified Roban and Kuavo versions. Its low-level SDK covers motor commands and state or IMU readings, while the listed high-level SDK remains marked as forthcoming. Confirm the supported software release, available interfaces and maintenance commitments for the ordered hardware.
Industrial application evidence
Leju's industrial page presents automotive material handling, logistics and electronics production scenarios, including plastic-container recognition, depalletizing and transport. These are supplier application descriptions and demonstrations. They do not by themselves establish a buyer's cycle time, unattended operating period or staffing reduction. Request a repeatable trial using the actual containers, fixtures and process sequence.
Questions for an acceptance trial
Define successful picks, placement tolerance, dropped-object handling, intervention frequency and recovery time before testing. Include obstructed routes, changing lighting and a representative shift schedule. Record whether each task uses teleoperation, a scripted sequence or autonomous control, and retain failed attempts alongside successful runs. Evaluate the proposed work area and stopping behavior with the responsible integrator.
Delivery and ongoing operation
Clarify which party supplies commissioning, operator training, spare joints, batteries and software support. Agree access to logs, configuration backups and update rollback, plus ownership and export of collected task data. A phased rollout should have written acceptance criteria for each location and an agreed process for resolving hardware or software changes after delivery.