Skip to main content
Why Operators Should Demand Open Ecosystems
Part 108 DJI Transition Open Ecosystems BVLOS Operations

Why Operators Should Demand Open Ecosystems

Louis Trebaol •

Switching drones is a weekend project. Rebuilding your operational infrastructure is a six-month one. That’s the lesson of the DJI transition — and the next time you choose a drone platform, there’s one question that matters more than flight time, payload, or camera resolution: what happens to my operation if I switch hardware?

The Lock-In Problem Nobody Talks About

When operators discuss the DJI transition, the conversation focuses on hardware specs. Flight time. Payload capacity. Camera resolution. Thermal capability. These matter, obviously. But they’re not why the transition is painful.

The pain comes from everything around the hardware: years of flight logs tied to DJI’s cloud. Training programs built on DJI’s specific interfaces. Maintenance schedules tracked in DJI’s proprietary systems. Mission planning workflows that only work with DJI’s controllers. Client reports generated from DJI’s data formats.

This isn’t a drone-industry problem. It’s a maturity problem every industry eventually solves. Airlines don’t run Boeing’s proprietary crew scheduling software alongside Airbus’s proprietary maintenance system — they run Sabre, Jeppesen, and AMOS across every airframe they fly. The aircraft vendor builds aircraft. The operations vendor builds operations. Commercial drones are one regulatory cycle away from needing the same separation.

What “Open” Actually Means

An open drone ecosystem separates three layers that most vendors bundle together:

  • The aircraft layer. Hardware, propulsion, sensors, flight controller. This is what manufacturers should focus on — building the best aircraft for specific missions.
  • The operations layer. Flight planning, crew management, training records, maintenance tracking, compliance documentation, incident reporting, safety management. This should be hardware-agnostic and operator-controlled.
  • The airspace layer. Strategic deconfliction, conformance monitoring, ADS-B/Remote ID integration, ADSP services. This needs to work across all operators and all aircraft types.

When these layers are independent, you can swap aircraft without rebuilding your operation. You can fly a Freefly Astro for mapping and a Watts PRISM Sky for heavy-lift inspection, managing both from the same operations platform with the same compliance records, the same training system, and the same safety management program.

When these layers are bundled by a single vendor, switching hardware means switching everything. That’s not a technology problem. It’s a business risk.

Part 108 Makes This Urgent

Under Part 107, the compliance burden was light. A Part 107 certificate, a few waivers, and a spreadsheet for flight logs was enough for most operators. Lock-in was annoying but tolerable.

Part 108 changes the equation. The compliance requirements — SMS, organizational training programs, airworthiness acceptance documentation, ADSP integration, incident reporting, FAA inspection readiness — represent significant ongoing obligations. Building this infrastructure on a hardware vendor’s proprietary platform means your compliance program is only as durable as that vendor’s business model.

Every operator planning for Part 108 should ask their platform vendor three questions:

  1. If I switch aircraft manufacturers, do my compliance records transfer?
  2. Can I manage a mixed fleet — different aircraft from different manufacturers — in a single operations system?
  3. Who owns my operational data if I leave your platform?

If the answer to any of these is unsatisfactory, you’re building on a foundation that won’t survive the next hardware transition.

The Standard Your Operation Deserves

Your flight logs should be yours. Your training records should survive a vendor change. Your safety management system should work with any aircraft type. Your compliance documentation should be portable, auditable, and independent of the hardware you fly.

The operators who build on open, hardware-agnostic infrastructure will transition smoothly from Part 107 to Part 108, adapt to new aircraft as technology evolves, and never face another fleet-wide operational disruption because a single vendor was banned, acquired, or shut down.

The DJI crisis is the lesson. Don’t learn it twice.

Virabelo is the operations layer for commercial aviation — independent of the aircraft you fly. Learn more at virabelo.com.

Back to Blog