Built here, start to finish
The airframe is our own design, made and assembled in the workshop rather than sourced and rebadged. If a part of it breaks, we know exactly what it is, because we made it.
Controllers · Aircraft · Software · Support
Two things, and only two. A flight controller sold with its software and real support, and complete drones assembled and tested here. The board, the firmware on it and the program that sets it up are all ours, so when something needs answering, the person answering is the one who wrote it.
Product one
Sold the way a flight controller should be: with the program that configures it, the updates that keep it current, and somebody to write to. Designed in KiCad, assembled at a board house, brought up on the bench one peripheral at a time.
| Processor | STM32F405, 168 MHz |
|---|---|
| Sensors | IMU, barometer, magnetometer |
| Motors | Four outputs, DShot |
| Radio | ELRS and other serial receivers |
| Logging | On-board blackbox flash |
| Mounting | 30.5 × 30.5 mm |
| Updates | Signed, dual-slot, over USB |
| Status | Version 1 flies. Version 2.1 is at the board house. |
A board is easy. A board somebody stands behind is not. Every controller comes with the configurator, firmware updates signed with our key for as long as we make them, and support from the people who designed the thing, not a forum thread from 2019.
30.5 mm, deliberately. If ours ever lets you down, a commercial board bolts straight into the same holes. And if you already fly something else, ours drops into that. We would rather earn the slot than lock you into it.
Product two
A complete drone, built here: our airframe, our controller inside it, motors, ESC and receiver fitted and wired, set up and bench-tested before it goes anywhere. Nothing to assemble and nothing to print. You charge a battery and fly it.
The airframe is our own design, made and assembled in the workshop rather than sourced and rebadged. If a part of it breaks, we know exactly what it is, because we made it.
Radio mapped, motor order and directions checked, battery configured, failsafe tested, firmware current. It arrives flying, not needing a weekend of configuration first.
The controller in a finished aircraft is the one we sell on its own, so everything on this site applies to it: the configurator, the signed updates, the support, the flight logs.
The software
It is where you will actually spend your time. It shows the board it is talking to, says what it is doing in words, and refuses a bad value with the reason rather than accepting it and letting you find out in the air. Windows, macOS and Linux. Free, no account.
Radio mapping and reversal, arm and mode switches, motor order, battery cells and chemistry, rates and gains. Stored on the board, never by editing or rebuilding firmware.
Live attitude, sticks, battery and link, a motor test that only runs with props off, and flight logs you can pull down and read after a flight.
When newer firmware exists, a line appears under the header saying so. The tool checks the signature, sends it, and waits for the board to confirm the new version booted.
Why our updates are different
Most firmware updates are an act of faith: overwrite what works, hope it comes back. Ours cannot be. The rules live in the board, not in the program that talks to it, so they hold even if this website, or the computer you plug into, is not ours any more.
Every image carries an Ed25519 signature over its own hash. The bootloader checks it against the key inside the chip before a single byte is written, and refuses anything else, including an older version of ours.
The board keeps two copies of the firmware and writes the one it is not running. A transfer that dies halfway leaves the flying copy untouched, because the manifest is written last.
New firmware gets three boots to prove itself: three seconds running, disarmed, with a live gyro. If it cannot, the bootloader goes back to the version that worked. A bad update costs one reboot.
The server you download from is not trusted either: it only holds signed files. How that works, in detail.
Support
This is half of what we sell. A controller nobody supports is a component; a controller somebody supports is a product, and the difference shows up on the evening something will not arm.
Help with the first setup (radio, modes, motor directions) from whoever wrote the firmware you are configuring.
Send the flight log. The board records what it saw; between that and the source, an answer is usually a reading, not a guess.
Signed firmware and a tool that offers it. A fix reaches the board you bought last year and the ones we ship tomorrow.
We replace or repair it. And because it is on the 30.5 mm standard, you are never grounded waiting for us.