FLIGHTOPS / BETA 0.2.0b1

Your ROS system.
A clearer view.

Choose the installer for your exact Ubuntu, Python, and ROS combination. Each installer checks the host, then asks you to accept the FlightOps beta terms before downloading its pinned archive. You need the license key from your beta email; register for the beta if you have none.

Ubuntu 22.04 · ROS 2 Humble

Requires x86_64, Python 3.10, and an installed ROS 2 Humble environment. Official Humble installation instructions.

source /opt/ros/humble/setup.bash
curl --proto '=https' --tlsv1.2 -fS https://get.flightops.dev/install-humble-f1fa28a516f9bdfc.sh -o flightops-install.sh && bash flightops-install.sh
export PATH="$HOME/.local/bin:$PATH"
flightops license activate

Download Humble installer / Archive / Checksum / First-use guide

Release flightops-20261022-0.2.0b1-humble-public3 · source 9ec4bac7264b939be1439cbec8c52a82019b558c · 45,858,230 bytes · SHA-256 301b9f977b147b1cc670afcf353b57ca7c46ec58c212b32f26e63d6a142c387f

Ubuntu 24.04 · ROS 2 Jazzy

Requires x86_64, Python 3.12, and an installed ROS 2 Jazzy environment. Official Jazzy installation instructions. Source Jazzy before running the installer so its Python packages are available.

source /opt/ros/jazzy/setup.bash
curl --proto '=https' --tlsv1.2 -fS https://get.flightops.dev/install-jazzy-000050d5922b9dd2.sh -o flightops-install.sh && bash flightops-install.sh
export PATH="$HOME/.local/bin:$PATH"
flightops license activate

Download Jazzy installer / Archive / Checksum / First-use guide

Release flightops-20261022-0.2.0b1-jazzy-public3 · source 9ec4bac7264b939be1439cbec8c52a82019b558c · 46,073,102 bytes · SHA-256 7412e2c51ff2fcc672ddc39278a04846a52eebc44eacdfdd150c62b5c833db15

In this beta

Every Flightops tool is on your PATH after installing: flightops, onscope, splashdown, lcc, highbay, the MCP server, flightschool, flightlead (preview) and flightops-gym-smoke (research preview). flightops workbench --sample opens two Nav2 recordings in the Scene Workbench desktop app, and flightops docs --open opens the documentation shipped with your build.

Each device needs a license from the beta, and installed builds send usage metrics: command names, outcomes, durations and versions, never arguments, paths, ROS names, recordings or code. flightops telemetry show prints exactly what is queued. Privacy notice.

Independent acceptance pending

Both builds passed clean-install, license activation and workflow checks in containers on the development PC. First use by an independent person on another physical machine is still pending. Follow the matching first-use guide and keep its transcripts. Questions and feedback: beta@flightops.dev.