Conceptual UAV component system architecture showing six interconnected layers Concept illustration
Capabilities / Component Families

Component Capabilities

Six component families sourced and configured around system interfaces, so the flight controller, powertrain, structure and payload work as one connected architecture.

Families6 System Layers
ScopeComponent → Stack
ApproachInterface-First
EntryAny Layer
System Approach

Six component families. One engineering conversation.

Each component layer connects to the others through interfaces, protocol, voltage, mechanical fit and data flow. We organize sourcing so those connections stay visible, not lost between separate catalog pages.

Flat lay arrangement of six UAV component layers — flight controller, ESC, motors, airframes, antennas, and camera gimbals Concept illustration
How Capabilities Connect

Every layer informs the next.

A flight controller choice determines which ESC protocols are available. Motor selection sets the current draw that the power system must handle. Payload weight and interface shape the airframe and comms architecture. We keep these dependencies visible.

01

Define

Aircraft type, mission profile and payload requirements.

02

Control

Flight controller, sensors and firmware architecture.

03

Power

ESC, battery and distribution matched to the control layer.

04

Motion

Motors and propellers aligned with power and airframe.

05

Signal

Radio, telemetry and positioning for the operational range.

06

Mission

Payload and platform configuration for the application.

Beyond Sourcing

Capabilities extend into configuration and verification.

Component selection is the starting point. Customization and testing turn parts into a platform.

Customization Path

From mission brief to configured build

Translate aircraft type, payload goals and operating environment into a matched component architecture, starting at any layer or depth.

Explore Customization
Testing & Validation

Parts become a platform through verification

Power-path checks, interface verification, parameter review and flight-readiness preparation turn sourced components into a validated system.

Explore Testing
Start With Any Layer

Bring the component family or the complete mission.

Start with a flight controller requirement, a full BOM or a mission concept. We will map the interfaces that connect your build across all six layers.

What a multi-layer build costs, and how the layers price against each other.

Each component family has its own cost page. The question a buyer asks at this level is different: when several layers are combined into one engagement, where does the money actually concentrate. The bands below are component build cost across typical industrial platforms, not resale price.

LayerTypical share of a matched buildWhat shifts the share
Flight control8 – 14 percentEcosystem choice, sensor set, whether redundant IMUs are specified
ESC and power12 – 20 percentCurrent class, whether a smart power module is included, harness complexity
Propulsion15 – 24 percentMotor class, thrust-to-weight target, propeller material and count
Airframe and structure22 – 34 percentWheelbase, ply schedule, machined interface count, test article
Communications7 – 13 percentRange class, whether redundant links are required, antenna customisation
Payload and gimbals10 – 30 percentSensor class, stabilisation requirement, mission-set configuration

The share that surprises buyers most is airframe and structure. On a fixed-wing or large multirotor it routinely exceeds the electronics combined, because structure carries machining, tooling and structural validation rather than catalogue parts. Teams that budget from an electronics BOM alone under-provide this layer more than any other.

Which obligations sit with the supplier and which with the operator.

When several families are sourced together, the obligation boundaries have to be drawn once for the whole stack, or each family is read independently and interfaces fall between them.

ItemSupplier responsibilityOperator responsibility
Cross-layer interface definitionDocument voltage, current, protocol and mechanical fit at every layer boundaryConfirm the mission the combined stack must survive
Matched-stack compatibilityVerify the selected families interoperate before shippingConfirm the intended build depth and target cost band
Firmware and parameter baselineProvide a documented baseline across control, power and signal layersOwn the final parameters once in its own operating environment
Bench and flight-readiness testRun the agreed combined checks and record resultsProvide the flight-test environment and accept the airworthiness call
Configuration controlFreeze a combined build revision and trace every changeMaintain the revision during field repair
Regulatory documentationDeclare the standards each family is tested toOwn the aircraft operator certificate and airspace authorisation

The failure that costs the most is a matched stack where each family is compliant and the combination is not verified. An ESC that meets its own specification into a motor the supplier never paired it with is how a build passes every incoming inspection and still fails on the bench.

Two reference builds that combine several layers.

Both are published in full on our projects pages. They show how the layers above come together on a real aircraft rather than on a component list.

  • The lidar mapping platform combines a VTOL airframe, a matched powertrain and a 5 kg sensor payload whose sensor and onboard computer draw 38 W of an approximately 888 Wh budget, about 22 percent across a 120 minute mission. Control, power, propulsion and payload had to be sized together, because payload power share decided the airframe, not the other way round.
  • The heavy-lift agricultural platform is an X8 coaxial octocopter with a 1,600 mm wheelbase carrying a 30 litre spray payload, running 12 to 15 minutes per tank because the spray load draws current continuously. Here the propulsion share of the build rises above the table range, because continuous payload current forces a larger power and thrust margin across three layers at once.

One build concentrates cost in payload efficiency, the other in propulsion and power margin. Reading your mission against the nearer of the two tells you which table row your own budget will actually be driven by.

What to specify before asking for a multi-layer quotation.

These points let a first quotation come back as a matched architecture rather than a component list.

  • Name the layers you want sourced together, and the one you consider fixed and non-negotiable.
  • State the aircraft type, mission and the operating environment, including the temperature range.
  • Give the payload as a class with its continuous and peak current draw, not only its mass.
  • Declare the endurance target and whether it is hover or cruise.
  • State the communication range and whether line-of-sight or beyond-line-of-sight operation is required.
  • List the standards the combined platform must be documented against.
  • Say whether witnessed acceptance testing is required, and at which layer boundaries.
  • Provide the target build cost band so each layer is sized to it rather than quoted open-ended.

Because the layers are priced as shares of one build, a target cost band is more useful here than on any single-family page. It lets each layer be sized against the others instead of optimised in isolation.