Platforms The record Method Company News Request a briefing
Defense technology · Charleston, SC · Non-traditional defense contractor

Accountable automation for defense.

HYPATIUS, LLC builds three platforms that decide, prove and account for the work of contested-domain defense — each one leaving a record a commander, a bid board or an auditor can take apart. Clarity for contested environments, with the evidence attached.

UEI UKELB3UV76V6 · CAGE 19S89

Explore the platforms → Contracting with HYPATIUS
HYPATIUS, LLCParent company · Charleston, SC · UEI UKELB3UV76V6 · CAGE 19S89
STARCHITECT ▲ Live · flagship · advanced reconnaissance starchitect.us ↗ ALIDADE ◆ In development · TBD 2027 Capture decision intelligence alidade.us ↗ CRATON ◆ In development · TBD 2027 DCAA timekeeping craton-erp.us ↗
One company · three platforms BMC3I-native simulation Orbit to seabed OTA · CSO · SBIR Phase III Every AI run on the record DCAA-aligned HYPATIUS, LLC · Charleston, SC
The problem

Defense software rarely fails the physics. It fails the review.

Every consequential decision in this domain has to survive somebody who was not in the room. Producing the answer is the easy half. Producing an answer that survives the person who signs for it is the work — and that person asks the same question in three different accents.

The commander
“Why this course of action?”

A recommendation made under a decision clock has to stay interrogable: the physics, the assumptions and the adversary model all reachable from the answer, not filed somewhere behind it.

The bid board
“Where does that number come from?”

A probability of win is an argument, not a readout. Every factor carries its citation, or the score is an opinion with a decimal point on it.

The DCAA auditor
“Show me the hour.”

Fourteen areas of the SF 1408, each one answerable from the ledger on the day it is asked — rather than assembled the night before by whoever still remembers.

Ninety percent accuracy is a one‑hundred percent failure rate.

In contested domains the margin for error is zero. We don’t build features — we engineer the decision. Every system assumes the environment is fighting back, and degrades to advantage instead of collapse.

Built
Orbital simulation, built; live operations planned
Measured results are shared in briefings.
3
Platforms, one operating layer
STARCHITECT · ALIDADE · CRATON. Exactly three.
Near-real-time
Sensor-to-COA, the loop closed
Design target · HYPATIUS platform directives · imminent threat level
One company · three platforms

Decide it. Prove it.
Account for it.

Three platforms on one loop. Each takes a stretch of the same problem — the mission you fly, the work you pursue, the record that proves both — and each hands the next a decision somebody can check. The loop closes: what the record settles is what the next decision is argued from.

DECIDE STARCHITECT PROVE ALIDADE ACCOUNT CRATON THE RECORD SHARED MECHANISM
DecideSTARCHITECT · live · flagship

Wargaming and mission command for the information and decision space. Courses of action generated against real orbital physics and a red cell that plays at machine speed, on a console built to be driven under a clock.

▲ Reviewed by a commander ProveALIDADE · in development

Everything a pursuit needs that is not the writing. Seven cited factors resolve to one probability of win with the gaps named, and teaming runs on consent rather than on introductions.

◆ Reviewed by a bid board AccountCRATON · in development

Hours, charge codes, indirect rate pools and the SF 1408 binder for small government contractors. Generated from the ledger on the day it is asked for, not assembled the night before.

◆ Reviewed by an auditor
01 / Live · flagship

STARCHITECT

Decide it.
Advanced reconnaissance · space wargaming

The operating system for space wargaming and BMC3I. High-fidelity orbital mechanics and a red cell that plays at machine speed drive a console built like a command grammar: control groups on hotkeys, a command card of legal orders, resources that force tradeoffs, a decision clock. AI-assisted analysis. Every operator commit is recorded.

Orekit
Physics core
BMC3I
Native integration
SDA / PWSA
Mission set
02 / In development · TBD 2027

ALIDADE

Prove it.
Capture decision intelligence · GovCon

Seven cited factors resolve into one probability of win, with the gaps named. Teaming runs on consent: a partner is a handle until both sides agree to be named. Built for delivery as an MCP tool server your agents call. Every operator commit is recorded.

7 factors
Each one cited
3 bands
Probability of win
Consent
Teaming
03 / In development · TBD 2027

CRATON

Account for it.
DCAA-ready timekeeping · the SF 1408 binder

Timekeeping, charge codes, indirect rate pools and the audit binder, built to the fourteen areas of the SF 1408. At launch it keeps the four things a cost-type award asks a small contractor to prove, in one append-only ledger anyone can read — so the review is the least interesting hour of the auditor's week.

SF 1408
Fourteen areas
Append-only
Hash-chained ledger
Small teams
By design
In development craton-erp.us ↗
STARCHITECT
Live · space wargaming

The operating system for space wargaming and BMC3I — high-fidelity mechanics + adversarial AI, every run on the record.
ALIDADE
In development · capture intelligence

Capture decision intelligence. Seven cited factors, one probability of win, teaming on consent, every run on the record.
CRATON
In development · deterministic ERP and CRM

The audit-ready backbone for defense program execution — DCAA-aligned, cryptographically isolated.
STARCHITECT
Reasoning layer · live

Space wargaming and BMC3I simulation — the operating system for orbital conflict.

Explore →
ALIDADE
Capture layer · in development

Capture decision intelligence — seven cited factors, one probability of win, teaming on consent, a run ledger.

Explore →
CRATON
Execution layer · in development

Deterministic, audit-ready ERP and CRM for program execution — DCAA-aligned, cryptographically isolated.

craton-erp.us ↗
The mechanism

One record.
Three reviewers.

The three platforms look nothing alike and share one structural commitment. An AI-assisted run writes down what went in, which tools it called and what came out — and no output reaches a course of action, a bid or an invoice until a named person has signed for it. There is no automatic acceptance path to switch off, because there is not one to begin with.

The ledger never takes a write back

A correction is a new row that references the one it corrects. Each row carries the hash of the row before it, so a removed or reordered entry is detectable rather than arguable. The history of a number is the number.

append-only · chain verified on every read
The receipt is an object, not a log line

Inputs, tools called, outputs and reviewer are first-class fields attached to the thing they produced — queryable and exportable months later, rather than a line in a file somebody hopefully kept.

run.receipt · inputs · tools · outputs · reviewer
Nothing counts without a name against it

Acceptance is blocked until a reviewer is set. The automation proposes and a person disposes — in the console under a decision clock, at the bid gate, and at the close of the month. Same rule, three surfaces.

accept · blocked until reviewer_id is set
run receipt · craton.rates.snapshot · illustrative
Run2026-09-01T06:12:04Z · period 2026-08
Inputsledger rows posted to date
pools: fringe · overhead · G&A
Toolsledger.read
rates.compute
sf1408.map(area 03)
Outputsprovisional → final
G&A rate, recomputed
Reviewer◆ unset — acceptance blocked
▲ chain verifiedhash 7f2a…b41c
What it looks like on the receiving end

The fourteen areas, answered daily.

The SF 1408 is the pre-award survey that decides whether a small contractor may hold a cost-type award at all. Its last question asks whether the system is in full operation — a compliant package nobody uses fails it. CRATON is built to answer all fourteen from the ledger, and makes that last question the home screen.

01settled
02settled
03settled
04settled
05settled
06settled
07settled
08attention
09settled
10settled
11settled
12attention
13settled
14in full operation

Example tenant state. Area 14 is the one that cannot be produced on request, only demonstrated. Detail at craton-erp.us.

Hybrid-architecture multi-domain operations

Edge to core, and back.

Five domains sense at the edge — the domain space. One hybrid layer, designed to tolerate denied, disrupted, intermittent, and limited (DDIL) links, carries it to the core — the information and decision space. There, threat becomes measured courses of action (MOMs · MOEs · MOPs), verified by an operator, and battle management, command, control, communications, and intelligence (BMC3I) is pushed back to the edge at the speed the threat level demands.

Domain space · EdgeFind · Fix · Track
Space
SDA tracks · maneuvers · RF/EO custody
C4ISR
Air
ISR feeds · missile warning · air picture
C4ISR
Land
Ground sensors · fires · force posture
C4ISR
Maritime
Surface/subsurface tracks · AIS · radar
C4ISR
Cyber
Network telemetry · link health · intrusion
C4ISR
Hybrid layerTransport
Mesh, any path
Agnostic data paths · no single link
Store-and-forward
Designed for recovery on reconnect
Unified data
One record across domains
Cross-level sharing
DoD · IC · coalition · commercial
DDIL-tolerant · machine speed
Decision space · CoreInformation / decision space
1
Threat / response matrix
Threat level × pre-authorized response, per domain
2
TT&P + COA generation
Branches per scenario · kill-chain graph
3
Fast-forward adjudication
Physics + network wargame · Orekit · high-rate
4
Probability of success
Per scenario · measures: MOMs · MOEs · MOPs
5
Operator-verified decision
AI-assisted · every operator commit recorded
Combatant CommanderNational Command AuthorityMission partners · coalitionBusiness transaction model
Return · BMC3I to the edge

Battle management, command, control, communications, intelligence — pushed back into the domain space. The threat level decides who acts and how fast.

Target · Engage · Assess
Low
Who acts
Core deliberates · commander commits
Latency
Hours → days
What moves
Updated TT&P · re-plan · retasking
Elevated
Who acts
Core pushes ranked COAs · operator verifies
Latency
Minutes
What moves
COAs with probability of success · tasking
Imminent
Who acts
Edge acts on pre-authorized response matrix
Latency
Seconds · near-real-time sensor-to-COA
What moves
Effects · then report to core

TT&P = tactics, techniques & procedures · COA = course of action. The latency curve and the five domain lanes are on the Platforms page. Measured results are shared in briefings.

How we work

Method, not posture.

Four commitments that show up in the architecture rather than on a capability statement. They are why a firm of this size can ship into this domain at all.

01 · Cadence
Commercial speed, federal vehicles

We ship on OTA, CSO and SBIR Phase III while the budget cycle argues with itself. Non-traditional is a delivery model here, not a box we tick — it is the reason a capability reaches an operator in the quarter it was asked for.

02 · Scale
Built for small teams and their first awards

Enterprise systems assume a finance department, a programme office and an implementation year. The firms this work depends on have none of those. Everything is designed to be operable by the team that actually exists on the day.

03 · Conditions
DDIL is the default, not the failure case

Denied, disrupted, intermittent and limited is the assumed operating condition. Quorum-free consensus and enclave-local autonomy mean a node that loses the link keeps fighting, and the system degrades to advantage instead of collapse.

04 · Provenance
Every run reviewable, by construction

Tenant isolation, an immutable audit trail and a named reviewer on every acceptance are architecture, not a compliance layer added before a review. It is the same mechanism in all three platforms because it is the same problem.

The vision

The next decade of conflict is a software problem.

Deterrence now runs on who can sense, decide, and act faster across every domain at once — orbit, spectrum, sea, and the contracting line that funds it all. HYPATIUS is building the operating system for that fight: one connected reasoning layer, owned by the people defending the mission.

Build it with us →
Leadership

Operators, engineers, builders.

National-security space, platform architecture, brand, operations, and aerospace strategy — each has been doing this kind of work for years.

Full bios →
Stan Kennedy
Stan Kennedy
Co-Founder & Chief Executive Officer
 James (Jim) LeMieux
James (Jim) LeMieux
Founder & Chief Technology Officer
 Jordan Broe
Jordan Broe
Co-Founder & Chief Mission & Product Officer (CMPO)
 Shawna LeMieux
Shawna LeMieux
Chief of Staff
Executive advisor Maureen O'Brien
Maureen O’Brien
Executive Advisor
News

Latest from HYPATIUS.

All news →
Press release · 08 Sep 2026

HYPATIUS names Stanley O. Kennedy, Jr. Chief Executive Officer

Oakman Aerospace co-founder brings four decades of space systems and digital engineering leadership to the company behind STARCHITECT. James (Jim) LeMieux transitions to Founder & Chief Technology Officer.

Charleston, S.C. · Read the release →
Contracting with HYPATIUS
STATUS Small business  ·  Non-traditional defense contractor
UEI UKELB3UV76V6  ·  CAGE 19S89
HQ Charleston, SC  ·  CONTACT leadership@hypati.us
Small-business set-asideNon-traditional defense contractorSBIR Phase IIIOTACSO NAICS 541512NAICS 541330NAICS 541715SAM.gov registered

Building something contested? Let’s talk.

Request a briefing →
Start the conversation

Tell us what
you’re building.

Someone from leadership responds within one business day. Briefings available under NDA.

Emailleadership@hypati.us
Phone253.230.4166
HeadquartersCharleston, South Carolina

Goes straight to leadership@hypati.us. We reply to the work email you give.