Strategic deconfliction — ASTM F3548-21
Operational intent shared and conflicts resolved before takeoff, against a standard rather than a house algorithm. Generally available.
All products
Sovereign UTM · airspace command
FlightStudio
Airspace you hold, not rent.
Self-hosted UAS traffic management: strategic deconfliction, Remote ID and compliance evidence, running on infrastructure you control.
Maturity: AvailableAirNetwork
Designed outcome
A sovereign airspace operating picture where flight intent, constraints, live activity and the evidence trail remain under the authority or operator's control.
Best fit
Visit product siteCivil aviation authorities, critical-infrastructure operators and national programmes that cannot place operational dependence or flight records in a public SaaS.
Product capability
Most airspace management arrives as a subscription. Your flights, your telemetry and your compliance record live on somebody else's servers, in somebody else's jurisdiction, and the evidence you would need at an inquiry is an export request away from a vendor who may or may not still be trading.
FlightStudio inverts that. It is one codebase, deployed on premises, in a private cloud, or air-gapped — strategic deconfliction to ASTM F3548-21, Network Remote ID to F3411, ED-269 geozone authoring and SORA 2.5 risk assessment, with the evidence trail written where you can reach it. Plan, fly, prove, and hold all three.
The same build serves an enterprise operator programme, a civil aviation authority and a national system. What changes is configuration, not the product.
Network Remote ID — ASTM F3411 v19 / v22a
Broadcast and network Remote ID, both revisions, with the qualification suite re-runnable on your own deployment. Generally available.
Geozone authoring — ED-269
Author, version and publish geozones in the European standard format, so restrictions are a data artefact rather than a briefing note. Generally available.
Risk assessment — JARUS SORA 2.5
SORA 2.5 worked through in the platform, with the assumptions attached to the assessment instead of living in a spreadsheet. Generally available.
Fleet and field integration
DJI FlightHub 2 synchronisation, a field gateway that stores and forwards across a dropped link, and a live video wall with evidence recording. All in beta.
Deployed where you need it
On premises, private cloud or fully air-gapped. Licence verification is offline — nothing phones home — and configuration lives in your version control, not on a consultant’s laptop.
Concrete assets for the people who will operate the system.
- 01Configured authority and organisation model
- 02Versioned geozone and operating-rule set
- 03Operational-intent and conflict history
- 04Remote ID and mission evidence record
- 05Deployment configuration and operator runbook
- 06Re-runnable F3548-21 and F3411 qualification evidence
What this product does not claim.
- Maturity labels are literal and they do not move because a deal is close. Deconfliction, Remote ID, geozones and SORA are generally available; FlightHub sync, the field gateway, the video wall and cross-border delegation are beta; AI detection is preview; DFR dispatch is planned, which means not built.
- There is no certification badge, because in most jurisdictions no scheme accredits a UTM platform. What is offered instead is an evidence trail and re-runnable F3548-21 and F3411 qualification suites you can execute yourself.
- It does not defeat, jam, spoof or physically engage anything. Where it appears in a counter-UAS architecture it is the command and evidence layer above sensors and effectors supplied by others.
- Sensor and aircraft performance are their manufacturers’ claims, not ours. Integrating three detectors does not extend the range of any of them.
Questions buyers should ask early.
- Where must operational data live?
- Choose on-premises, private-cloud or air-gapped deployment from the sovereignty, connectivity and support constraints — not from a default hosting preference.
- Who owns an airspace decision?
- Roles, delegation, escalation and the evidence attached to each decision need named owners before configuration begins.
- Which interfaces are operationally required?
- Aircraft, Remote ID, fleet, field gateway, video and authority interfaces are selected against the workflow and accepted individually.
- How will the deployment be qualified?
- The acceptance plan identifies the standards, scenarios, records and rerunnable suites the operator must retain.
Capability domains
Products
Start with the problem, not the catalogue.
A scoping session establishes what you are actually trying to achieve, what is already in place, and whether we are the right people for it. If we are not, we will say so.