Isaac Lab-Arena
- Software
- Humanoids and robot learning
- Framework
A framework for composing robot simulation environments from scenes, embodiments and tasks, and for running and analyzing policy evaluations at scale in Isaac Lab.
- Closed core
Made by NVIDIA.
Source on GitHub: github.com/isaac-sim/IsaacLab-Arena (opens in a new tab). Facts read at commit 9afdcd0 (opens in a new tab).
Licenses
- Code
- Apache-2.0 (opens in a new tab)
Read by Robotheca from LICENSE.md (opens in a new tab) (Apache-2.0) at commit 9afdcd0 (opens in a new tab), on 16 Oct 2026.
- Commercial use
- Unknown
It needs closed parts under their own terms: read them before any commercial use.
One part it needs is closed
- Needs NVIDIA Isaac Sim: Isaac Lab-Arena, built on Isaac Lab, runs on NVIDIA Isaac Sim, whose Omniverse components are under NVIDIA's own terms.
Labels
- Closed coreIt needs closed parts: NVIDIA Isaac Sim.
What it does
- Builds reusable simulation environments by combining a scene, a robot embodiment and a task into a standard Isaac Lab environment.
- Places objects using spatial relationships such as on and next to instead of hard-coded coordinates.
- Chains atomic skills into longer composite tasks.
- Can generate environment specifications from natural-language prompts, which is experimental.
- Evaluates one policy in parallel across thousands of GPU environments, locally or distributed through OSMO.
- Tracks subtask milestones and runs sensitivity analysis over perturbed conditions to locate policy failures.
Written by Robotheca from the project's README (opens in a new tab) at commit 9afdcd0.
Getting started
- Difficulty
- Advanced
- Hardware it needs, as the project states it
- Linux (Ubuntu 22.04+), an NVIDIA GPU (see Isaac Sim hardware requirements), and Python 3.12 or newer.
- How to start
- The project's README (opens in a new tab)
Maintenance
- Status
- Active: a commit in the last 90 days
- Newest commit
- 16 Oct 2026 on main
- Latest release
- None published on GitHub
Checked on GitHub on 16 Oct 2026.
Links
Robots that can run it
No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.
Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.