Skip to main content
Ceradon Systems
COTS Architect

From parts on the shelf to a field-ready UxS package.

COTS Architect sits between the lab spreadsheet and the ground-control station. It turns aggregate COTS inventory into validated builds, batteries and support, RF evidence, and a concise technical handoff.

The installed Windows application runs offline, keeps every organization in its own workspace, and never invents aircraft, radios, relays, or specifications.

Inventory → Build → Mission Support → RF Check → Handoff.

Offline-first Explainable rules Quantity-first

Built for UxS professionals who need to know what they can build, what support it needs, and which constraints must reach the planning team.

Five-stage workflow

One path from lab inventory to technical handoff

Work left to right. Each stage carries the selected UxS forward without turning the tool into another command-planning burden.

1 Inventory

Imports messy CSV and Excel lab inventories without dropping uncertain rows.

  • Separate organization workspaces.
  • Scored classification with review and reclassification.

2 Build

Assembles complete UxS and operator kits from parts actually in the lab.

  • Checks physics, endurance, and compatibility.
  • Equips control, video, data, and antenna interfaces.

3 Mission Support

Calculates what the selected builds need for the operating window.

  • Batteries, charging, spares, loads, and resupply.
  • Focused support planning, not MDMP replacement.

4 RF Check

Places saved UxS and operator assemblies in the AO.

  • Separate control, FPV video, and data link budgets.
  • Terrain LOS, Fresnel, margins, and spectrum constraints.

5 Handoff

Packages only the selected UxS and its support evidence.

  • Build snapshot, support products, RF annex, and checks.
  • The full lab inventory remains in its workspace.

Quantity-first by design

COTS parts arrive as bins, lots, and purchase lines.

COTS Architect preserves aggregate inventory. Lot, condition, storage location, and individual identifiers remain optional for the items that benefit from them.

Loose components stay in Build. RF Check receives the complete saved UxS and operator assemblies, with every configured interface and fitted antenna.

Organized UxS component bins progressing through assembly to a complete aircraft, controller, goggles, batteries, and support kit

Product behavior

Honest inputs, traceable constraints

The tool shows the operator what is incomplete and where to correct it instead of hiding the reason behind a single score.

Organization workspaces

RTIC, SORD, Mongolia, and future customer labs remain separate. Builds, mission support, RF analyses, and handoffs follow the active organization.

Reviewable classification

Import classification uses multiple signals and confidence. Operators can reclassify one part or a bulk selection at import or later.

Assembly-aware RF

A saved build carries its controller, goggles or receiver, control receiver, VTX, data radios, and fitted antennas into directional link checks.

Build-scoped handoff

The package contains the chosen UxS, support products, RF evidence, and technical checks. It does not disclose the organization’s entire lab.

The result is a concrete UxS configuration with known support demand and explicit limitations that can move to the rest of the planning team.

Status and deployment

A branded Windows application for labs and disconnected field kits

The installer packages a local Electron application backed by explainable physics, support, and RF rules. Customer data remains on the operator’s computer.

  • Core inventory, build, support, RF, and export workflows operate without a network.
  • Product lookup and online map tiles remain explicitly opt-in and cache results for later offline use.
  • Physics checks cover AUW, thrust-to-weight, endurance, compatibility, and environmental derating.
  • Open-source code and versioned Windows installers are published through GitHub.

Who it’s for

Small technical teams responsible for rapid unmanned builds and sustainment in contested or air-gapped environments.

Planners who need repeatable answers without surrendering control to opaque scoring systems.

Build with what you have. Know what you need.

Put COTS Architect on the lab laptop.

Install once, work offline, and move a defensible UxS support package to the rest of the team.

Download Latest Release