Federated Autonomous Operating System

The operating system for sovereign autonomous operations.

DRACONEX makes any brain safe to connect. Governed Mission Operatives — DRACONIDs — execute under your authority: cloud, on-prem, edge, air-gapped.

Request a demo How to buy See it work ↓

DRACOMIND DRACO’s mind — stating the mission

Looking into DRACO’s mind — the DRACOMIND shell and its apps, a recorded walkthrough of the beta from draconex.ai. Not a live console.

How it works

The Reasoning Layer

Which intelligence may think about which problem, under which policy. Sovereign brains first; frontier models are opt-in and never for restricted data.

Summarize the CUI incident report CUI · wants a frontier route

1Sensitivity
2Complexity
3Availability
4Cost / latency
5Doctrine

Every routing decision is logged, with its reason
request	brain_id	policy hits	reason	confidence	cost

Sovereign brains first; frontier models only by opt-in, never for IL6, CUI or PII. Figures illustrative.

The Secure Control Plane

NEXUS CORE governs models, tools and data under one authority. Every action is logged, and every artifact is attested before it ships.

L1 DRACOMIND State it in plain language.
L2 The Reasoning Layer Which intelligence may think about which problem — under which policy.
L3 The Secure Control Plane Autonomous by design. Governed by policy. Proven by evidence.
L4 The Mission Operatives The operative survives the model.

The Mission Operatives

The DRACONIDs ship with DRACONEX, and you can train and define your own mission operatives. Each has its own identity, doctrine, memory and audit. The brain can change; the operative does not.

DRACO · identity

operative_id: draconid.draco
role: The Captain — CAPT, the 3B Orchestrator that ships with DRACONEX; it begins and ends every mission
doctrine: doctrine/draco
personality: persona/draco
skills: skills/draco · adapters bound
grants: grants/draco
memory: memory/draco
audit: written by LOG
brain: DRACO-3B · sovereign

Brain swaps: 0 · identity changes: 0

Each operative keeps its own identity, doctrine, memory and audit; the values shown are references. Twelve is the canonical flight — the constellation can grow beyond it.

v0.9.0-BETA is what runs today; the layers above are the v1.0.0 architecture. Learn more in the docs.

The DRACONIDs factory

From what the operatives learn on missions, the factory trains specialized adapters — validated, evaluated, signed and attested before an operative uses one.

Run A · DRACO-OPS skill refresh · a disallowed configuration

Seedsfrom mission memory
Validate
Trainpolicy check
Eval
Publishsigned · attested
Bind

Resumable from a checkpoint; each human gate is an interrupt; zero telemetry. v1.0.0 target: promoted memory to a bound skill in under ten minutes.

A mission run

State the mission; DRACO plans it and the operatives execute it. Every gated step stops on a Decision Card and waits for your approval.

Sample mission Patch the Edge gateway fleet (DRACO-OPS, DRACO-CAGE, DRACO-FLY)

Decision CardAwaiting human approval

Recommendation: Roll the patched gateway image to Edge node group B during tonight’s 02:00–04:00 window.
Reason: The CVE fix is attested by CAGE; group B has absorbed rolling restarts in that window three times without loss.
Confidence: 0.86
Learned from: Missions M-102, M-109, M-114 (Edge gateway rollouts)
Memory provenance: fact mbr/ops#41 ← mission M-114 · tool OPS.rollout · operator approval
Model used: DRACO-3B · sovereign (DRACO-OPS)
Captain consulted: Yes — plan reviewed by the Captain (CAPT · 3B Orchestrator)
Human approval required: Yes — a deployment to Edge is a gated action

A sample card. The eight fields and the approval gate are the v1.0.0 Decision Card.

The section animations are illustrations of how DRACONEX works; their figures are illustrative.

DRACONEX includes DRACOWING and DRACOTALON. The FORGE app in DRACOMIND — v0.9.0, in work — embeds them for the SPEC and CODE phases, then runs the autonomous pipeline: deploy, scan, test, ship.

Both remain their own products: DRACOWING runs without DRACONEX, and DRACOTALON without either.

How to buy

Demo

Free

A guided mission demo.

Request

Deploy

Quote

Per enclave · FDE Pod.

Request a quote

Partners

Govt · VARs

Prime on Navy SeaPort-NxG and IWRP OTA. Any federal product contract through a Value-Added Reseller or our distributor.

Talk to us Partners

Request a demo

A guided mission demo, on your calendar. Pick a time.

Open the booking page Opens Microsoft Bookings.

Questions

What is a Mission Operative?

A DRACONID: a governed operative with its own identity, doctrine, memory and audit. Reasoning can be replaceable; mission authority cannot.

Which brains does it use?

Any model. The reasoning layer of the NEXUS CORE runs whichever model you choose. The Captain (CAPT) is our 3B Orchestrator and ships with DRACONEX. Our DRACONEX 70B is an option at additional cost; NEXUS CORE EDGE includes it quantized, and an edge large enough can run the full model. Frontier models are opt-in, metered in DRACOEGGs, and never for restricted data.

Can I make my own operatives?

Yes. Train and define your own DRACONIDs, mission operatives, alongside the ones that ship with DRACONEX.

Where does it run?

Core on Azure Government AKS. Edge on Spark-class hardware, cord-pull ready: disconnected, it keeps working, then syncs on reconnect.

What runs today?

v0.9.0-BETA. The seven layers are the v1.0.0 architecture.

How is it bought?

Quoted to the mission, not sold from a shelf — as prime on Navy SeaPort-NxG and IWRP OTA, or on any federal product contract through a Value-Added Reseller or our distributor. FAR Part 12.

Read the DRACONEX docs