FLIGHTOPS

← back to the bench

PRIVATE BETA

Bring us the failure that cost you a week.

The private beta is free for students and researchers. Run FlightOps on your real graphs, recordings and pull requests. Companies: contact us.

What you get

  • The full toolkit. Doctor, Scene Workbench, the gate, the agent kit and optional AI.
  • A free key by email. Confirm your address and the license key arrives. One key works on 3 devices.
  • Your failures first. What you bring shapes the next doctor checks.
  • Free for students and researchers. Every beta license ends on 31 March 2027.

Good fit: students and researchers · ROS 2 Humble or Jazzy on Ubuntu x86_64 · coding agents writing robot code

To: FlightOps private beta
beta.flightops.dev

We use your answers to run the beta and to contact you about it. Privacy notice

COMPANIES

Using FlightOps at a company?

The free beta is for students and researchers. Companies: tell us what you build, and we will reply by email.

For companies

Your team, your robots, your ROS 2 setup and what you want FlightOps to do for you.

To: FlightOps
beta.flightops.dev

We use these details only to reply to you.

QUESTIONS

Questions we get at the bench.

Does FlightOps control my robot?

No. Inspection never publishes on your topics and never sets parameters or changes lifecycle or service state. Its short-lived observer node appears on the graph, and onscope doctor pair sends UDP test packets. Hardware is off in the beta; any hardware step will need a human GO.

Does my data leave my machine?

Evidence goes to an AI provider or the optional Jev service only after you approve that exact request. lcc keeps evidence local unless you set local_only: false. Network tools contact the network when you run them.

What does the beta send?

Required usage metrics: which tools run, their outcome and duration, and the FlightOps, Ubuntu, Python and ROS 2 versions. Never arguments, paths, ROS names, recordings, evidence, logs, AI content or code. flightops telemetry show prints exactly what is queued (privacy notice).

Which platforms do you support?

Ubuntu 22.04 with ROS 2 Humble and Ubuntu 24.04 with ROS 2 Jazzy, x86_64 only. Simulation gates use your installed Gazebo: Fortress or Harmonic on Humble, Harmonic on Jazzy. Not yet used by an independent person on another machine.

Does it replace my coding agent?

No. FlightOps is the helper your agent calls, through MCP, skills and JSON output. Every check also works without AI.

Can my coding agent use it?

Yes. JSON output from onscope, splashdown and lcc checks, a read-only MCP server, and 14 ROS 2 skills.

What does the beta cost?

Nothing for students and researchers. Each device needs a free beta license. One key works on 3 devices; a device is one user account on one machine. Every beta license ends on 31 March 2027. Companies: contact us.

How do I get access?

Register with the form above or at beta.flightops.dev/register. The license key arrives by email after you confirm your address. Install from get.flightops.dev/install: no sudo, no source checkout.

Where do I send feedback?

Send feedback and problems to beta@flightops.dev. Include the exact command, what you expected and the error text.

NEXT DRAWER

THE DOCTOROne command. A finding your agent can act on. THE BENCHBack to the bench: the README, the tour and every object.