AVEONI
Drone Kits

From Hardware to Intelligent Flight.

Drone development kits designed for the Aveoni ecosystem, intended to let a team start integration work on a known airframe instead of building its own test drone first.

In Development

“Intelligent Flight” names a direction for the platform, not a delivered capability. Flight systems, companion computing and AI development are being designed to work together.

Conceptual illustrations of an FPV quadcopter, a fixed-wing airframe and a custom production drone. Not product photographs.
The kit family

Three development kits

Conceptual illustration of a custom production drone kit. Not a product photograph.
01 · Multirotor · seven-inch

Aveoni Drone Kit 7″

In Development

A seven-inch multirotor designed as a development platform, not a finished product. It gives your team one known airframe to build on, from the first prototype to the classroom and the research bench, and it is meant to be opened, rewired and extended with the payloads and sensors your project needs.

  • Engineering
  • Prototyping
  • Education
  • Research
Conceptual illustration of an FPV 10 quadcopter kit. Not a product photograph.
02 · Multirotor · ten-inch

Aveoni Drone Kit 10″

In Development

A larger, ten-inch multirotor for work that outgrows a small frame. It is designed with room for a companion computer, cameras and heavier payloads, so your team can take perception and onboard-compute experiments out of the lab and onto a real airframe. Shown here as a folding-frame concept.

  • Engineering
  • Research
  • Companion integration
Conceptual illustration of a fixed-wing airframe. Not a product photograph.
03 · Fixed-wing

Aveoni Fixed-Wing Kit

In Development

A fixed-wing airframe for missions that need to cover distance rather than hover. It is designed for teams developing mapping, survey and inspection work on longer-endurance flights, and for teaching how fixed-wing flight control differs from a multirotor, with the same open, accessible build as the rest of the family.

  • Engineering
  • Research
  • Education
Hardware development philosophy

A development kit that shows the system instead of hiding it

Closed airframes slow development down: every change starts with taking apart something that was never meant to be opened. Each Aveoni kit is designed the other way round. The flight controller, the companion computer, the sensors and the software are separate, accessible parts, so your team can inspect, replace and test each one without rebuilding the drone.

  1. Open by designMounts, wiring and interfaces are designed to be reached and changed, so trying a new payload or sensor does not start with a teardown.
  2. Develop each part on its ownFlight, companion and sensor roles stay distinct, so one engineer can work on flight software while another works on perception, without getting in each other's way.
  3. Learn on a real systemEach kit is designed as a real airframe for learning embedded systems, flight software and hardware integration the way they fit together in a product.
Intended platform integration

Six directions the kits are designed to connect to

These are intended integration directions. They are not a working end-to-end stack, and no kit is yet integrated with any of them.

  • an intended integration area, not a status.

Flight systems

Flight controllers and their firmware, configured from the same project as the rest of the kit.

Companion computing

In Development Aveoni Companion is a first-party hardware companion computer, intended to pair with the kits for onboard compute.

Sensors and cameras

Sensor and camera interfaces the kits are designed to expose for development and recording.

AI and autonomy development

A place to develop and test models and autonomy code against the kit. On-device inference is not yet verified.

Connectivity

Links between the airframe, the companion and the ground. No connectivity option is confirmed for any kit.

Aveoni Studio and developer tooling

Studio is intended to configure and inspect the kit. Studio today connects to Betaflight flight controllers over USB and reads their identity.

Engineering and education use cases

Built for engineering, research and teaching

Engineering and research

Prototype a payload or companion integration on a real airframe. Test flight-system changes against a fixed development format before they go near a production build.

Teaching

Use a kit to teach embedded systems, flight software and hardware integration. Education programmes built on the kits are not yet defined.

Development status and specifications

Where the kit family stands today

Status
The three kits on this page are the first of a growing family. Many more formats are in active development alongside them.
Specifications
Being finalised. We publish a specification only once it is confirmed on a built kit, so what you read here will hold.
Pricing and availability
Prices, delivery dates and stock will be announced when the first kit is ready.
Performance
Flight figures will appear here once they have been tested and recorded, never before.
Compatibility
Hardware compatibility will be confirmed kit by kit, on real builds.
Imagery
The outlines on this page are design illustrations, not product photographs.
Next step

Explore an Engineering Pilot

Working on drone hardware, research or teaching? Once pilot enquiries open, tell us what you are building and we will say whether an engineering pilot fits.

Explore an Engineering Pilot