Ceradon Systems mark
Architect Stack

A UxS planning toolkit for COTS hardware.

Architect sits between spreadsheets and enterprise logistics systems. It turns real inventory—frames, radios, batteries, 3D printers, compute—into concrete node, drone, and kit designs tied to a specific mission.

Architect Stack is maintained as an open-source project by Noah Schultz (individual).

Inventory → Node designs → Drone designs → Mesh layout → Kits and sustainment.

Offline-first Explainable rules Mission-aligned

Go from RFIs to repeatable answers with small, focused tools that respect austere, air-gapped deployments.

View open-source demo View GitHub

Tool family

Small tools for nodes, platforms, and kits

Each module is scoped so small teams can mix and match without dragging a full ERP into the field.

Node Architect

Designs COTS RF/sensor nodes from compute, radios, antennas, and power.

  • Estimates draw, runtime, and RF role classes.
  • Applies LOS/NLOS assumptions explicitly.

UxS Architect

Builds multirotor, fixed-wing, and ground platforms around chosen nodes.

  • Checks all-up weight and thrust-to-weight.
  • Validates endurance and payload fit against mission profiles.

Mesh Architect

Rough RF coverage planner to highlight relay requirements.

  • Maps which links likely hold by band, power, and environment.
  • Flags where repeaters are needed.

Mission Architect

Mission-first planner that starts from task, environment, and endurance.

  • Pulls candidate node and platform templates.
  • Feeds Mesh Architect for coverage validation.

KitSmith

Turns final architectures into rucks, boxes, and sustainment plans.

  • Generates BOMs, per-operator weight, and battery counts.
  • Exports 24/48/72-hour sustainment views.

Planning flows

Plan from any starting point

Architect doesn’t lock you into a single workflow. Any constraint can drive the rest.

Mission-first

Start in Mission Architect, define task, environment, and endurance → pull candidate nodes/airframes → validate coverage in Mesh Architect → export kits with KitSmith.

Inventory-first

Begin with what’s on the shelf → Node/UxS Architect show what’s realistically buildable → Mesh and KitSmith wrap those into coverage and sustainment plans.

Constraint-first

Set strict SWaP or power limits in KitSmith → push those constraints back into Node/UxS Architect so only feasible designs are considered.

RF-first

Start from the RF environment in Mesh Architect (urban canyons, indoor, rural) → that dictates node classes, relay count, and platform roles.

The output is always the same: a set of concrete node and UxS configurations tied to a mission, with known battery demand and packing lists.

Status and deployment

Built for labs and offline kits

Architect is being built as a local, offline web toolset backed by simple JSON catalogs and explainable physics/RF rules.

  • ▹ Runs on a small server or lab machine, no cloud dependencies.
  • ▹ Inventory and blueprint libraries live as plain-text data.
  • ▹ Open-source prototypes are available for labs that want to experiment and contribute.
  • ▹ Repositories: github.com/noahschultz/architect-stack.

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.