FLIGHTOPS

← back to the bench

PRIVATE BETA

Bring us the failure that cost you a week.

We are inviting a small group of ROS 2 teams who build with coding agents to run FlightOps on real graphs, real recordings and real pull requests.

What you get

  • The full toolkit. Doctor, Scene Workbench, the gate, the agent kit and optional AI.
  • Onboarding with the engineer who builds it. We set up the gate on one of your repos with you.
  • Your failures first. What you bring shapes the next doctor checks.
  • Free during the beta. Beta teams help set team pricing.

Good fit: 5–40 engineers · ROS 2 Humble or Jazzy · Gazebo · coding agents writing robot code

To: FlightOps private beta
get.flightops.dev

We use your answers only to contact you about the beta.

QUESTIONS

Questions we get at the bench.

Does FlightOps control my robot?

No. Inspection is read-only and never publishes on your graph. Hardware-in-the-loop runs wait for an explicit GO from a person.

Does my data leave my machine?

Your code, recordings, evidence and file paths never leave it. Everything runs locally, and the optional AI assistant shows you each item before it is sent and sends nothing until you approve. During the beta, FlightOps sends usage metrics only: command names, outcomes, durations, versions and your Ubuntu and ROS 2 distribution (privacy notice).

Which platforms do you support?

Ubuntu 22.04 with ROS 2 Humble and Ubuntu 24.04 with ROS 2 Jazzy on x86_64, with Gazebo Harmonic and Fortress.

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 on every check, a read-only MCP server, and 14 ROS 2 skills.

What does the beta cost?

Nothing during the beta. We will agree team pricing with beta teams before it ends.

NEXT DRAWER

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