06 Focus Area In development

CubeSats you can print, fly, and revise

Conventional smallsat structures wait on tooling. Ours do not. By additively manufacturing the primary structure and bus components, a design change can be printed, integrated, and back on the bench in the time a machined part spends in a queue. That matters most where it usually hurts most: keeping a constellation current instead of frozen at the date it was ordered.

1U – 12UConfiguration range in development
PrintedPrimary structure and bus components
EO & RFPayload classes targeted
RefreshBuilt for constellation iteration

01 Approach

Why additive, specifically

Printing a satellite is not the point. Collapsing the distance between a design change and a flight article is the point. Everything below follows from that.

01

Iteration measured in days

A structural revision goes from CAD to a physical article without a tooling cycle. Over a constellation program that compounds: the fifth batch can carry lessons the first batch taught, instead of repeating a design frozen years earlier.

02

Geometry a mill cannot cut

Integrated harness runs, conformal radiators, and lattice structures that put mass only where load actually goes. Fewer fasteners and fewer joints means fewer of the interfaces that fail on vibration.

03

Unit cost that permits risk

When a bus is cheap enough to lose, a constellation can fly newer technology sooner and accept a shorter design life. That is a different economic model from a single exquisite spacecraft, and it needs different manufacturing.

04

A supply chain you can see

Printing in house removes a tier of vendors from the critical path and from the threat surface. We treat the design files and the print process as things worth protecting, because they are.

02 Configurations

Four bus sizes in development

Design targets for the current development articles. These are engineering goals under active test, not flight-qualified specifications, and we will tell you exactly where each one stands on a program call.

CubeSat configuration design targets
Configuration Form factor Payload volume target Typical role
ND-1 1U Single small sensor or radio Technology demonstration, on-orbit component test
ND-3 3U Optical or RF payload with deployables RF survey, AIS and signal collection
ND-6 6U Imaging optic with onboard processing Earth observation, tasked revisit imaging
ND-12 12U Multi-sensor or hosted payload bay Multi-payload missions, hosted customer sensors

Structure

Additively manufactured primary structure with printed bus components and standard rail interfaces for common deployers.

Payloads

Earth observation optics and RF sensing packages, with a hosted payload option on the larger buses.

Ground segment

Tasking, downlink handling, and processing built by our software team on the same evidence store as the toolkit.

Security

Command authentication, signed firmware, and supply chain review treated as requirements from the first print.

03 Principles

What carries across every platform

The same three commitments govern our maritime and aerial programs.

Additive first

Short build cycles keep the fleet current instead of frozen at the date it was ordered.

Sensor to decision

These are collection assets. What they gather lands in the same command view that runs our cyber work.

Hardened by default

Firmware, command links, and supply chain are treated as attack surface from the first print.

Program status

Program status The satellite program is in active development. We are talking with agencies, integrators, launch brokers, and manufacturing partners about pilot programs, hosted payloads, and constellation requirements. If you have a payload looking for a bus, that is a conversation we want.

Talk to the Program Team

→ Next Step

Pilot programs and payload conversations.

Tell us the orbit, the sensor, and the timeline. We will be straight with you about where the program is and what it can commit to.