Technology

One aircraft, four kinds of engineering

Most drone companies are a software company that buys airframes, or a hardware company that licenses someone else's flight software. We do both, plus the autonomy and the fleet system.

Not for its own sake. It is what lets us fix a problem where it actually starts.

In practice

One thread, all the way through

A pilot reports a vibration. Here is what happens next, and why it matters who built each piece.

  1. 1

    The aircraft recorded it

    Because we wrote the logging.

  2. 2

    The analyser found it and named the likely cause

    Because we designed the format it reads.

  3. 3

    The fix is a filter change in firmware

    Because we wrote the firmware.

  4. 4

    And if a filter cannot fix it, the motor mount changes

    Because we make the airframe.

Four companies would make that four conversations. Here it is one team and one afternoon.

The four layers

What each one is

01 Flying today

Hardware

Drawn for the aircraft, not bought and adapted.

We draw our own boards, so the electronics sit where the aircraft needs them and are built for heat, salt and humidity that would finish a board designed for a temperate lab. Every one is brought up and tested here before it flies.

Airframes are carbon fibre where a part has to be light and stiff, printed where the design is still moving — which is why a revision takes days rather than a tooling order.

02 Flying today

Firmware

Written from scratch, not forked.

Firmware and control algorithms are ours from the first line. That is how safety margins get designed in rather than tuned around, and how performance stops being a compromise you inherit. Everything else on the aircraft is built the same way: battery, radio, camera mount, updates.

Writing it ourselves is what makes owning the hardware worth anything: when a problem turns out to be mechanical, we change the machine instead of compensating for it in code forever.

03 In development

Autonomy

Today our aircraft fly routes a person planned. We are building ones that do not need the route.

The work is knowing position without GPS, recognising what is ahead, and choosing a path — all of it running on the aircraft, inside the power and weight a flying machine can carry. The algorithms are well understood. Making them fit is the hard part.

Flying in simulation now. Not yet on a customer's aircraft, and we will say so when it is.

04 Partly live

Fleet software

Where every aircraft is, what it has flown, and what needs servicing before it goes up again.

That is the job most operators still do in a spreadsheet, which works right up until it does not. Hangar is our answer to it, and it is built for bad signal: it keeps working offline and catches up when the connection returns.

The Flight Log Analyser is the part that is already live and free. It reads your logs in your browser and never uploads them — private because the data never leaves, not because we promise not to look.