Before you buy a Unitree EDU robot.

EDU identifies Unitree configurations intended for education, research and application development. The configurations offered here provide development access and computing for building software around the robot. You do not have to be a university to consider an EDU platform.

The exact package still matters: body articulation, hands, sensors and computing can differ within the same robot family. Compare those items alongside the price, especially when comparing an EDU package with a lower-priced non-development version.

You are starting with a manufactured robot platform, its supplied operating functions and access to the supported development tools. Your first development steps are to confirm the delivered hardware and firmware, prepare a compatible computer and network, and run the appropriate manufacturer examples.

A custom task still needs software, integration and testing. Development-ready does not mean that a robot arrives with a finished application for your workspace.

You do not need to build the supplied movement functions from scratch. Start with the manufacturer's supported operating software and the documented startup, operating and shutdown procedures for the delivered model. Then use the available development interfaces for your work.

If your project replaces locomotion or low-level control, that is a separate development task. Confirm the supplied movement modes and firmware when planning a demonstration; manufacturer videos can show software and configurations beyond the package you are considering.

Those are application projects that must be defined and tested. A robot's walking software, cameras and hands do not by themselves provide a complete cleaning or production workflow. The application may need perception, grasping, motion planning, fixtures, process integration and a suitable operating area.

Describe one initial task, the objects involved and the result you need. Thetic can review the platform and development scope for that task before you commit to a larger application.

Start with the work: object size and mass, reach, required hand motions, workspace, development tools and budget. R1 is the compact starting point in this catalog. G1 offers a middle-sized platform with a meaningful choice between Standard and more articulated Ultimate configurations. H2 provides a full-size platform and a different computing and facility-planning requirement.

Use the comparison page to narrow the choice, then evaluate the complete configuration against the task. A larger robot or a more complex hand is not automatically the best fit.

TOPS means trillions of operations per second and is a reference for AI computing throughput under specified conditions. It is not a measure of the robot's intelligence or a guarantee of application speed.

The useful questions are which processor and memory are supplied, which software it supports, how your model runs on it, and the latency and power required by the task. Extra computing may help a particular perception or AI workload; it does not replace application software or testing.

Plan for a development computer, a suitable network connection and someone comfortable installing software, working with a command line and debugging hardware/software interfaces. Unitree publishes C++ and Python SDK resources, and its ROS 2 workflows use a compatible Linux environment.

Check the operating system and dependencies for the tools you plan to use before choosing the computer. Thetic can scope help preparing the environment and introducing the supported examples.

Unitree publishes SDK resources for C++ and Python, along with ROS 2 integration resources. These provide a starting point for communicating with supported robots and building your own tools.

Support depends on the robot, firmware, interfaces and software versions involved. Share your intended stack and the functions you need, such as robot state, arm commands, cameras or hand feedback, so compatibility can be reviewed at that level.

Simulation is a useful part of development. Unitree publishes simulation and learning resources, but each project has its own model, dependency and hardware-support requirements. Check the exact robot configuration before choosing a workflow.

Moving from simulation to hardware still requires validation of timing, contacts, sensors, motion limits and the test environment. A policy that works in simulation is a starting point for controlled hardware testing.

Teleoperation can be used to record demonstrations for a learning project. Turning those demonstrations into repeatable autonomous behavior also requires a suitable data pipeline, model, training or adaptation process, deployment and testing.

The number of demonstrations and development effort depend on the task and how much variation it must handle. An EDU robot or a tactile hand does not automatically include a one-click system for learning any task.

There is an official Unitree XR teleoperation development project with support for several humanoid and hand configurations. A usable setup also needs compatible tracking or controls, camera arrangements, networking and the appropriate software configuration.

Define whether you need arm-and-hand control, locomotion, live video or synchronized recordings. That makes it possible to specify a complete workflow rather than assuming a headset and a robot form a ready-to-run kit.

The R1, G1 and H2 configurations described here list Wi-Fi and Bluetooth hardware. Development workflows may also use a wired network connection, depending on the model and interface. Confirm the actual connections and network setup for your configuration.

Cellular connectivity requires a compatible modem or router, a data service and network integration. If you need remote access, specify the intended functions, latency requirements and behavior when the connection drops.

The configurations described here include microphones and speakers. Those provide the audio hardware; the supplied voice software, languages, accounts and network requirements need to be checked for the delivered firmware and region.

A custom conversational interface or spoken task workflow may require speech recognition, a language model, speech output and application logic. The application must also define which actions spoken commands can trigger and how those actions are checked before execution.

Local robot communication and fully offline operation are different requirements. The complete setup may involve manufacturer applications, activation, updates, remote support or optional cloud software, each with its own connections.

If your organization has network or data restrictions, identify them before ordering. Request a connection and data-flow review for the complete setup, including manufacturer applications, updates, optional cloud services and remote support.

Plan the operating and storage area, clearances, handling and support equipment, charging location, development computer and network. Identify who will operate the robot and review the manufacturer's procedures for the exact model.

For a worksite application, include access restrictions, nearby people and equipment, and the conditions under which tests will be run. An onboarding scope can help organize these preparations; a product specification alone is not an application safety assessment.

The base starting price refers to the named EDU Standard configuration with non-actuated dummy hands. Dummy hands do not grip. Selecting a functional hand package changes the robot package and its displayed starting price; that package includes a pair of the named hands.

You can request a hardware-only quote. Onboarding, integration and development services are optional and separately scoped. Review the selected-configuration summary and written quote for the complete equipment, quantities and charges.

Shipping and applicable taxes are quoted separately from the displayed hardware-package price. The written quotation identifies the configuration, delivery charges and any import charges or responsibilities for your order.

Include your delivery city, state and ZIP code when requesting a quote. Compare the complete delivered configuration and cost, including any optional equipment and services.

A useful quote identifies the robot family and exact factory package, body articulation, hand model and tactile variant, computing, sensors and included equipment. It should separate optional equipment and services from the robot price.

Before ordering, review availability, delivery responsibilities and charges, payment terms, the applicable warranty, and any cancellation or return conditions. For development work, also review deliverables, milestones, testing and handover. These details make quotes for the same robot family meaningfully comparable.

No. It sends Thetic the configuration and requirements you are considering. We review the request and reply by email with the next step, which may be a clarification, a discussion of suitable options or a quotation.

An order requires agreement on the exact hardware, price, availability, delivery terms and any services. The website form does not take payment or reserve inventory.

Availability and lead time need to be checked for the selected robot, hands and options. A manufacturer production estimate is different from delivery to your address; shipment preparation, transport and import clearance can also affect the schedule.

Tell us your required delivery date and whether it is tied to a class, grant, demonstration or project milestone. Ask for a current estimate for the complete configuration before making plans around its arrival.

Include your organization's vendor setup requirements, purchase-order process and delivery deadline in your inquiry. If you need particular documents or approval steps, list them at the beginning so they can be reviewed alongside the equipment request.

We will confirm the purchasing and payment arrangements available for your order before you commit.

Warranty coverage can differ between the robot, third-party hands and other components. Review the coverage for each item separately from any Thetic onboarding or support services.

Before ordering, confirm the warranty period and exclusions, whom to contact if a fault occurs, the diagnostic information required, and how repair, return shipping and any costs are handled. If you would like Thetic to coordinate warranty claims, include that assistance in the support scope.

Review the cancellation, configuration-change and return conditions in the written sales terms before placing your order. These conditions form part of the agreement for the equipment you are purchasing.

If your plans change, contact us promptly with the order reference and requested change so we can confirm the available options.

Budget for the whole development setup: optional hardware, spare or replacement equipment, your development computer, software or cloud resources you choose to use, and any separately agreed engineering support.

Any subscription, third-party software license, cloud service or continuing Thetic support included in a proposed setup should be identified and priced separately.

Contact us with the robot and application you would like to see. We will confirm the equipment and demonstrations available and discuss the visit arrangements.

Our office and warehouse are in Warminster, Pennsylvania. Please arrange the visit with us before planning travel.

Yes. Thetic serves U.S. buyers from its Pennsylvania base. Include the delivery location and any onsite requirements so equipment supply and the requested support can be considered together.

An onsite visit or installation is separately scoped around the work, location, travel and schedule. It is not automatically included with a robot purchase.

Start with a nonconfidential description and tell us if your project requires an NDA. Agree appropriate confidentiality arrangements before sending proprietary designs, datasets or other restricted material.

The general website form is for initial inquiries. Sending it does not establish a confidential project relationship or transfer your proprietary data rights to Thetic.

For an equipment quote, start with the model or configuration, quantity, delivery location and target timing. For application advice, describe the objects, size and mass range, surface materials, workspace, desired motions and what a successful result would look like.

Include any existing robot, software stack or purchasing requirements. You can leave the hand and model undecided; a clear task description is more useful than guessing a configuration.