FlybyOps and the BVLOS stack: managing the operation is one half. Witnessing it is the other.

FlybyOps, from the team at Flyby Guys, has launched an enterprise platform for managing large-scale BVLOS and autonomous drone programmes: flight approvals, personnel qualifications, equipment, procedures, incident reporting and multi-project oversight, with auditable records throughout. “The challenge changes completely when you move from operating a few drones to running hundreds or potentially thousands of BVLOS flights,” says CEO Stephen Sutton. He's right — and operators are already using it globally.

Step back and the pattern of the last month is unmistakable: DJI signing declarations for aircraft design, Dronedesk automating SORA assessment, and now FlybyOps industrialising the operational workflow. The BVLOS compliance stack is professionalising layer by layer, which is exactly what an industry does just before it scales.

Two kinds of record, one operation

As that stack matures, a distinction becomes worth stating precisely. Workflow platforms produce the record of what your organisation decided and signed: who was qualified, which procedure applied, who approved the mission. Indispensable — and, necessarily, authored by the people running the operation. The other half is the record of what your machines actually did: what the dock's climate system drew at 3am, what firmware flew, what the airspace check found, what happened in the minutes nobody was watching. That record can't be authored at all — it has to be observed, continuously, by something outside the operation. That's the half Dock Pulse builds, read-only by design, which is precisely what makes it credible as evidence.

Scaled BVLOS operations will run both halves: a system of decisions, and a witness to outcomes. The operators who arrive at a thousand flights with both intact are the ones who'll be allowed a thousand more.