Open Source RoboticsRobots, software & learning

Rerun

Software

Multimodal robotics logging and visualization SDKs with time-aligned views, robot-data ingestion and query interfaces. [1] [3]

Installation & first result →Official websiteGetting started

For
Robotics developers inspecting sensor streams, transforms, joint states or datasets [1]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
operating system, compute requirements 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

Rerun provides SDKs and a viewer for recording and inspecting time-indexed multimodal data such as images, point clouds, transforms and joint states. The repository describes robotics workflows involving live streams, logs and datasets. Choose one of those routes first: an SDK that logs data, a viewer that displays it and an importer that understands the original format are distinct parts of the workflow. [1]

Is this for you?

Known limitations
  • Selected Python source is0.42.0-alpha.1+dev, not automatically the current pip release.
  • Repository MIT/Apache source is separate from hosted/commercial open-core offerings and third-party data rights.
  • No viewer, recording import, memory limit, live stream, data query or training integration was exercised.

Editorial scope assessment from the cited implementation/documentation; no execution or compatibility test.

[1] [2] [3] [4] [5] [6] · Editorial assessment

What you need

Dependencies
  • Selected Python source requires Python>=3.11
  • Python SDK distribution includes the viewer; Rust and C++ need a separately installed viewer
  • Cargo viewer route's nasm feature requires the nasm command-line tool

[1] [2] [3] [4] [5] [6]

Installation & first result

Open the upstream getting-started guide [1]

  • Use the documented rerun-sdk Python distribution for a bundled viewer or select language-specific SDK and viewer installs; distinguish release packages from the selected development snapshot.
  • Preserve exact source/dependency/model versions and evaluate the selected workflow before connecting physical hardware or reusing data.

Editorial scope assessment from the cited implementation/documentation; no execution or compatibility test.

[1] [2] [3] [4] [5] [6] · Editorial assessment

Installation

Use the documented rerun-sdk Python distribution for a bundled viewer or select language-specific SDK and viewer installs; distinguish release packages from the selected development snapshot.

Editorial scope assessment from the cited implementation/documentation; no execution or compatibility test.

[1] [2] [3] [4] [5] [6] · Editorial assessment

Hardware, models & data

Inputs and outputs

Images, points, transforms, joint states and other time-indexed data to recordings, synchronized views and queryable robot data.

Editorial scope assessment from the cited implementation/documentation; no execution or compatibility test.

[1] [3] · Editorial assessment

Project notes

The Python and native-language installs differ

The README's Python quickstart uses pip install rerun-sdk; it says that distribution includes the viewer. Rust and C++ SDK use requires a separate viewer installation. Its Cargo viewer route includes a nasm feature that requires the nasm command-line tool. Do not diagnose a missing native-language viewer as proof that a logging API failed. [1]

The documented Cargo command is cargo install rerun-cli --locked --features nasm, with nasm available in PATH. Upstream says the feature can be omitted, potentially reducing video-decoding performance. It suggests rerun --help as an initial installation check; that check was not run here. [1]

The selected Python source checks for Python 3.11 or later and identifies itself as 0.42.0-alpha.1+dev. That is the inspected development snapshot, not automatically the package obtained from an unpinned pip command. Preserve the SDK/viewer versions when investigating a recording or comparing behavior. [3]

The README warns of breaking API changes. It also notes possible viewer slowdown with many entities and slow handling of multi-million-point clouds. These upstream cautions make version records and representative input sizes useful parts of an evaluation; they are not measurements from this review. [1]

Evaluate the data path with a bounded recording

The README lists robot-log and dataset routes including MCAP and LeRobot alongside its own recordings and query APIs. For an initial investigation, select one data source and determine the timestamp, transform and schema conventions needed by that route. Then evaluate it with representative data. No import, live stream, synchronized display, memory behavior or training-data query was exercised here. [1]

The repository supplies MIT and Apache-2.0 license files and describes an open-core business model. Distinguish repository source from commercial or hosted offerings and from the rights attached to recorded data. This profile is source research, not a benchmark, successful installation or claim that every advertised product feature is available in the inspected repository. [1] [5] [6]

What we checked

Source research only. Selected implementation/model text, repository tree and license declarations were inspected. No upstream compilation, dependency installation, simulator, network/USB/device integration, data collection, benchmark or physical robot test was performed. Source files are linked rather than redistributed; external services and paid products are not endorsed.

Not yet established

  • Requirements: operating system, host computer
  • Version-specific hardware compatibility (ecosystem tags alone do not establish it)

Updates

Upstream last updated
Not established
Latest release
Not established
Profile updated
Nov 1, 2026
Sources last checked
Nov 1, 2026
Next review
Dec 1, 2026
Reviewed revision
c862998

Source files and licenses

Distinct robot-facing tool contribution with actual implementation/model content and a bounded documented next step. Review covers source artifacts, not operational performance or a complete tested deployment.

LayerAvailability / license
softwareavailable · MIT OR Apache-2.0
Declaration for the scoped source implementation/documentation; dependencies, external services, model/data assets and inherited file-specific terms require separate checks. No blanket redistribution or operational clearance. [1] [2] [3]
documentationavailable · MIT OR Apache-2.0
Declaration for the scoped source implementation/documentation; dependencies, external services, model/data assets and inherited file-specific terms require separate checks. No blanket redistribution or operational clearance. [1] [2] [3]

This profile is scoped to source implementation/model descriptions and an initial inspection workflow; no physical manufacturing design, pretrained checkpoint or dataset is selected for redistribution or tested deployment.

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.7.0-draft.5

Change history