Robot product dossier · 08

Unitree G1, H1, Go2 and B2

Unitree Robotics · Global / China · Humanoids · quadrupeds

Commercial / operationalCommercial hardware portfolio; capabilities and readiness differ sharply by modelLast reviewed: 11 August 2026

Decision questionHow should buyers separate accessible robot hardware from application-ready automation?

08

FUURAA thesis

Unitree makes legged platforms comparatively accessible across research and inspection categories. Availability of hardware is not the same as a validated application, safety case or supportable production system.

Reading method

Do not ask only what the robot can do; ask how the whole system works, fails and recovers.

01Stage

Separate commercial, limited, prototype and development stages.

02System

Inventory software, payloads, facilities and people beyond the robot.

03Evidence

Move from demos to repeated tests, field data and auditable records.

04Boundary

State what first-party reporting still cannot prove.

System and workflow map

Four interdependent layers turn a product name into real operating conditions.

Each layer explains its role and what procurement, research or deployment teams should watch.

01

Platform choice

G1, H1, Go2 and B2 span humanoid and quadruped forms with different envelopes.

02

Payload and sensing

Useful work depends on the sensor, compute and tool configuration.

03

Software stack

SDK access can enable research while shifting integration work to the user.

04

Application engineering

Navigation, task logic, safety and fleet tools must be built around the platform.

Decision checklist

Five checks turn product interest into verifiable procurement, research or pilot questions.

Define the task, interfaces, safety and operations before requesting evidence that supports a decision.

  1. 01

    Task fit

    Choose the exact model against a bounded research or inspection objective.

  2. 02

    Integration load

    Inventory sensors, compute, SDK, communications, payload and data interfaces.

  3. 03

    Safety case

    Assess stability, energy, remote stop, access and bystander risks.

  4. 04

    Operating model

    Plan engineering ownership, spares, firmware control and service response.

  5. 05

    Evidence to request

    Request model-specific tests under representative terrain, payload and duration.

Scope boundaries

Product availability, a video demonstration or a commercial agreement each supports only bounded conclusions.

Sources and evidence status

Primary product material and independent evaluation context are kept distinct.

Dates, source identity, supported conclusions and reading boundaries remain reviewable.