Downloads

Download RLSOK

Compare saved robot settings locally, or manage robot setups and approvals. Choose the option that fits your computer and what you want to do.

The local workspace and Local Check do different jobs, so their version numbers differ. Choose by the purpose above. See a 3-minute example.

Need help with your first run? Ask in the RLSOK Discord or email support.

Start with an example

Windows and Mac include a one-click example. On Ubuntu, follow the commands below. You can also watch the video on any computer, then use your own project files when you are ready.

See what RLSOK checks3-minute video · Any computer · No installation

See matching settings, a changed setting, and what happens when the example’s approval is withdrawn.

Recorded local demonstration with synthetic inputs; it does not demonstrate live ROS or a physical robot.

Try the example on Ubuntu45.5 MB download · No robot, account or ROS installation needed

The download includes everything this example needs to run. It creates two reports: one with matching settings and one with a changed calibration value.

Already working with your own project? Open interface configuration and project guides.

Use an Ubuntu computerUbuntu 22.04 or 24.04 on an Intel/AMD 64-bit computer, with curl and tar. For Windows or Mac, choose the matching download above; this package runs on Linux x64.No administrator password is needed. Keep the example in a new folder; your existing RLSOK installation stays in place.

1. Copy, paste and run

Open Terminal on Ubuntu. Copy the commands below, paste them and press Enter. They download RLSOK, check the file and run the example. If rlsok-first-check already exists, choose a new directory name in the first line.

mkdir rlsok-first-check && cd rlsok-first-check &&
curl -fLO https://github.com/realitywarden/rlsok/releases/download/v1.5.12/rlsok-local-check-1.5.12-linux-x64.tar.gz &&
curl -fLO https://github.com/realitywarden/rlsok/releases/download/v1.5.12/rlsok-local-check-1.5.12-linux-x64.tar.gz.sha256 &&
sha256sum -c rlsok-local-check-1.5.12-linux-x64.tar.gz.sha256 &&
tar -xzf rlsok-local-check-1.5.12-linux-x64.tar.gz &&
./rlsok-local-check-1.5.12/bin/rlsok profile demo --output first-result

2. Check the two results

Settings matchWOULD_ALLOWThe sample matches its approved configuration.
A setting changedWOULD_BLOCKThe changed value no longer matches the approval.

Open these files in your text editor: first-result/baseline/report.md and first-result/changed-calibration/report.md to read why. These are sample comparison results; they do not move or stop a robot.

If a download or checksum check fails, stop there. Rerun in a new directory after resolving the error; do not skip verification. Use the download and checksum from the same version.

Download files, version and update notes
Ready for your own project? Choose a guide →
Check my own projectChoose the guide that matches the files you have

Have saved settings or source files? Choose your project below. Each guide explains which files to use and what the comparison can tell you. Some guides also need Python or Git.

Create 3 version comparison uses saved text files only. Live Mowgli observation needs your existing ROS 2/message environment, Git and Python; installing this download does not connect a mower for you.

I have a ROS 2 setup to configure

Use the configuration tool to import your discovered interfaces, choose what each one means, map custom fields and export a reusable local Shadow workspace.

You’ll needAn isolated or simulated ROS 2 environment with your interface types installed, an interface catalog exported from it, the configuration files you want to check, and local message or goal samples. The tool explains the catalog export command.

The tool supports Twist velocity topics, joint trajectories, absolute or relative Cartesian goals, and allowlisted TP program selectors. It checks your local samples and configuration; it does not set up ROS or connect a physical robot for you.

Configure my interfaces

Humble compatibility, private action compatibility and physical operation are not validated. A successful local check is not proof of physical safety or completed robot integration.

All project guides and requirements

Installation, updates and robot setup

Find Windows installation details, updates for an existing installation, or the guide for a specific robot setup.

I use the UR5e setup with a cloud account

Go to the supported reference setup

UR5e setup guide

Check a UR5e setup with your cloud account

Setup discovers the supported UR5e driver and active controller, binds the observed boundary to the exact release, pairs with Hosted Cloud, waits for independent approval, and writes hash-verified Evidence without sending a controller goal.

Before you run the commands

Ubuntu 24.04 x86_64, ROS 2 Jazzy, Fast DDS, the official UR5e driver, live JointState and an active scaled_joint_trajectory_controller are required.

Official-driver mock hardware and real DDS validated; physical UR5e validation is pending.

In your Ubuntu terminal:

curl -fsSL https://rlsok.com/install.sh | sudo sh
source /opt/ros/jazzy/setup.bash
export RMW_IMPLEMENTATION=rmw_fastrtps_cpp
rlsok setup
Runtime operations and download files

Published Runtime v1.4.5 · source 38478f6a6b8808dbd9c7eeb5085a54492b36bd05. The installer verifies the published SHA-256 and pins the expected digest before changing the active runtime. Setup discovers the model, namespace, joints, controller, state and action inside the documented reference boundary.

  • Re-run the install command to upgrade. Versions live under /opt/rlsok; the system command is /usr/local/bin/rlsok.
  • Credentials use user-only storage under ~/.config/rlsok. Configuration and Evidence live under ~/.local/share/rlsok.
  • Run sudo /opt/rlsok/uninstall.sh to remove the runtime. User configuration and Evidence are preserved.

Download Ubuntu x64 bundle · Machine-readable public release facts

I already have the Windows management app
Existing Windows management app

Update Windows 1.3.0 to 1.3.1

Add startup update notices and a Check for updates button. The update runs only after your confirmation and SHA-256 verification, and retains your database and configuration.

Previous programs are kept for recovery. Execution approvals stay unchanged.

Your first update is manual

Windows 1.3.0 cannot show update notices. Follow the guide with your existing installation; do not reinstall over your data.

Before you update

Upgrade and failure rollback have not been runtime-tested. This update keeps Cloud/API/schema 1.3.0 and does not update the robot Runtime. The guide describes the required unchanged migration baseline.

Install the Windows local workspace
New Windows installation

Your local workspace, without entering an account

Install Node.js 22.12+ (with npm 10.5+) and PostgreSQL 16 or 17 first. Download and extract the ZIP into a new folder, read its README, then open Open RLSOK.cmd. Follow the included Install command if setup is needed.

Use your own files and management tools. Saved work stays on this computer. Opening the workspace does not connect or move a robot.

Windows 1.3.2 · 18.3 MB ZIP

For a new workspace. Keep an existing installation and its data separate; this is not an upgrade over an older workspace.

Restart, repair and saved work

Version 1.3.2 preserves saved files and configuration when restarting or repairing with the same bundle. Follow its README for Stop, Reinstall and Uninstall. Keep your private state folder and credentials protected.

Already on an older version? Read the existing Windows update guide. Historical packages remain available in the original release; use the new package above for a fresh workspace.

Manage your workspace in your browser

Create an account or sign in to review connected setups, approvals and saved records. Local use of the Windows, Mac and Ubuntu downloads does not need an RLSOK account.

Create an account or sign in →
Older downloads, checksums and technical details

RLSOK provides execution authorization and Evidence. It is not functional safety, an E-stop, a safety PLC, collision avoidance, trajectory safety, or motion planning. It does not replace robot safety mechanisms or operator responsibility.