Practical writing from our engineering team on building and running drone software, and on the regulation that shapes it.
What changes operationally and in software when an organisation grows from one drone to several.
Testing, failure handling and update practices that separate dependable drone software from demos.
Open vs Specific, what an operational authorisation involves, and what it means for operators planning more than one aircraft.
Patterns across sectors: what has become routine, what is still experimental, and where software makes the difference.
The main options, their trade-offs in range, bandwidth and cost, and how to match them to an operation.