Open Source RoboticsRobots, software & learning

ALOHA

Robot / hardware build

A four-arm bimanual teleoperation and demonstration-recording system with a separate learning stack. [1]

Build & first use →Official website

For
Robot-learning labs with Interbotix and ROS experience [1]
Cost
No current cost or bill of materials established yet.
Source rights
Named licenses are documented by part. Review licenses
Unknowns
tools, operating system not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

This ALOHA repository provides teleoperation and data collection for four arms and four cameras. The hardware assembly tutorial is a separate document, and training imitation-learning models requires the separate ACT project. Copying this repository alone does not preserve a complete robot build or learning environment. [1]

The upstream guide calls for at least six USB 3 ports: four direct connections for the robots and two for cameras. It reports unstable multi-arm connections on some hosts, rejects hubs and extensions for the robot links, and limits cameras to two per hub. These are practical host-selection constraints even before training compute is considered. [1]

Follow the device-identity section when planning the setup: fixed aliases distinguish left/right leader and follower arms and the four cameras. The pinned guide reports Ubuntu 18.04 and 20.04 with ROS 1 Noetic and specifies a Python 3.8.10 Conda environment; these historical combinations have not been reproduced here. ROS 2 compatibility is described as ongoing work. Interbotix software is another required external dependency, including a documented change to its arm.py file to avoid forward-kinematics computation delaying teleoperation; see the upstream software-installation section before freezing that dependency. It also warns that torque-off arms can collapse because the joints have no automatically engaged brakes. [1]

The software is MIT-licensed; that does not establish rights to manufacture every purchased arm component. Current full-setup cost, dependency compatibility and our support effort remain unknown. We have not run teleoperation, recorded an episode or tested this hardware. [3]

Is this for you?

Known limitations
  • Robot connections should not use USB hubs or extensions in the documented setup
  • No more than two cameras per hub in the upstream guidance
  • Torque-off arms have no automatically engaged joint brakes

[1]

What you need

Host computer

Upstream calls for at least six USB 3 ports: four direct robot connections and two camera connections.

[1]

Dependencies
  • Interbotix software and ROS 1 Noetic in the pinned setup
  • Separate ACT repository for imitation learning

[1]

Hardware & parts

Hardware configuration

Two leader arms and two follower arms

[1]

Assembly & first use

Project documentation [1]

Cost

No current, complete configuration-specific build cost has been established for this profile.

3D preview

Preview not available yet. Design-source links are available, but the reviewed record does not establish unambiguous reuse rights for a hosted CAD preview.

What we checked

Source research only; no installation, physical build or performance test performed. No affiliate links added.

Not yet established

  • Requirements: operating system, tools
  • A step-by-step setup summary

Updates

Upstream last updated
Apr 19, 2024 [2]
Latest release
Not established
Profile updated
Sep 30, 2026
Sources last checked
Sep 30, 2026
Next review
Oct 30, 2026
Reviewed revision
06369f03cd8e0a47e16d3a90167853fd33af7557 (commit snapshot; no published stable release found) · combined hardware and software repository

Source files and licenses

Available project sources support research coverage; complete build and commercial qualification remain separate.

LayerAvailability / license
mechanical designnot found · License not fully assessed
No complete artifact for this layer established in the inspected primary repository overview and archive inventory. External component/dependency sources require separate collection; this is not a claim of closed source. [1] [4]
electronicsnot found · License not fully assessed
No complete artifact for this layer established in the inspected primary repository overview and archive inventory. External component/dependency sources require separate collection; this is not a claim of closed source. [1] [4]
firmwarenot found · License not fully assessed
No complete artifact for this layer established in the inspected primary repository overview and archive inventory. External component/dependency sources require separate collection; this is not a claim of closed source. [1] [4]
softwareavailable · MIT
Teleoperation and collection software only; external ACT, ROS and robot components have separate terms. [1] [4] [3]
documentationavailable · MIT
Repository documentation; linked hardware tutorial remains a separate artifact. [1] [4] [3]

This profile covers the described physical configuration and control route without a particular learned policy or dataset.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.5.0-draft.1

Change history