COSRYX · ORBIT

Evidence that survives orbit.

ORBIT is the COSRYX programme for trusted software in orbit: who authorised a command, what a machine decided when nobody was in contact, where every key came from, and how that evidence stays checkable for the life of the mission and beyond.

Stage 1 · Ground trust layerBuilt · Simulation-validated
Stage 2 · Autonomy and quorumSimulation-validated
Stage 3 · Flight containerReviewed internally · founder-approved
Orbital runPlanning
01 What ORBIT is

The same receipt, pushed to the hardest place it will ever have to work.

COSRYX turns every command, decision and health record a spacecraft produces into evidence a third party can check later. ORBIT takes that idea into orbit itself: a small, frozen software container that runs on a host satellite's payload computer, refuses commands it was not authorised to run, keeps a signed record through every gap in contact, and sends the record down for anyone to verify on the ground.

Space magnifies every problem evidence systems already face: links that last minutes per pass, frames measured in bytes, assets that fly for fifteen years without a patch, and inquiries held long after the people who built the system have moved on.

ORBIT is founder-owned and runs inside COSRYX. Its receipts are DCS R-Series receipts, hybrid-signed with Ed25519 and ML-DSA-65, hash-chained and checkable offline. Its one-line position is the COSRYX one: we do not replace mission security; we add mission evidence.

Your command chain already has authentication, encryption, counters and replay protection. None of it leaves evidence a third party can check years later.

02 Where ORBIT stands

Two stages simulated. A flight container ready. The orbital run planned.

ORBIT status as of 21 October 2026

STAGE 1

Ground trust layer

Built · Simulation-validated

Commands formed, authorised and receipted on the ground; telemetry bound to the same record; an offline verifier that checks it all with DCS servers switched off. Built and run in simulation.

STAGE 2

Autonomy and quorum

Simulation-validated

Decisions taken out of contact, sealed and chained on board; release of authority by a signed quorum of separate approvers. Exercised in the link-loss simulator.

STAGE 3

Hosted-software run

Container built · five internal review rounds · founder-approved

The flight container is built and frozen. The orbital run is planned with a host satellite operator: one booked orbit, two passes, verified on the ground. Nothing has flown yet.

STAGE 4

Partner missions

Future direction

ORBIT as a standing evidence layer for partner missions, after the Stage 3 run is complete and its records are published for checking.

What this does not claim. No flight qualification is claimed. Nothing in ORBIT is radiation-tested. Stage 3 is a hosted software run on a satellite someone else operates; it adds no hardware. The host operator is not named on this site. Simulated feeds on these pages are labelled Simulated.
03 Architecture

Space, ground, verifier. And where the trust lives.

Simulated · space → ground → verifier01 / 04
01 · GROUND SEGMENT

The command is formed and receipted on the ground.

Mission-operations software forms a telecommand. The receipt is minted where the command is formed: who authorised it (two-person authorisation), under which key and key epoch, and exactly which bytes were sent.

  • Signing keys for the mission stay on the ground.
  • The receipt wraps the mission stack; it replaces nothing in it.
02 · SPACE LINK

The existing link security carries the frames.

Fielded command links protect each frame with symmetric authentication under the CCSDS Space Data Link Security protocol. ORBIT leaves that alone and binds the receipt to the link's sequence count.

  • No stateful signer on board.
  • On board: hash commitments and a sealed, chained recorder.
03 · TELEMETRY

The acknowledgement closes the loop.

The spacecraft's acknowledgement telemetry comes down and is bound to the same receipt, so the record shows what was sent and what the asset reported back.

04 · VERIFIER

Anyone with the spec can check it later.

A verifier rebuilt from the published specification and test vectors checks the hybrid signatures, the sequence binding, the acknowledgement and the key epoch, with DCS servers switched off.

04 Films

ORBIT in four short films.

Animated explainers, first released in October 2026. The scenes are illustrative: nothing shown has flown yet.

ORBIT · launch film1 min · 11.6 MB
01 · Software in orbit30 s · 13.5 MB
02 · Link loss30 s · 15.3 MB
03 · Verified on the ground30 s · 10.9 MB
06 Three tiers

Tiny in flight. Rich on the ground. Checkable anywhere.

ON THE PLATFORM

Tiny, frozen, boring

  • A Linux container with a fixed image digest
  • Command authoriser, signed mission recorder, receipt signer with mission-test keys
  • Hash chain kept on board through every gap
  • No network call to DCS; must keep working if DCS disappears
ON THE GROUND

Where receipts are minted and checked

  • Mission-operations receipt wrapper, bound to the link sequence count
  • Key registry and receipted key events
  • Reconcile and cosign for decision records
  • Archive manifests and renewal
ANYWHERE, LATER

Independent verification

  • One verifier, one receipt format
  • JavaScript and Python verifiers, same verdict
  • Raw signed files, byte for byte: no screenshots, no summaries
  • "Refused by policy" kept separate from "unverifiable"
07 Stage detail

What each stage has shown, and what it has not.

StageShown so farNot yet shownStatus
1 · Ground trust layerGround-minted command receipts, telemetry binding, offline verification, all exercised in simulationUse on a live mission linkBuilt · Simulation-validated
2 · Autonomy and quorumSealed decision records through connected, degraded, lost and reconnect; quorum release under separate approver keysUse on a real platformSimulation-validated
3 · Flight containerContainer built and frozen; reviewed internally in five dated review rounds; founder-approvedRunning in orbitReviewed internally · founder-approved
3 · Orbital runRun plan written; every step rehearsed in simulationThe run itself, with a host satellite operatorPlanning
4 · Partner missions-EverythingFuture direction
No flight qualification claimed. The Stage 3 claim, once the run happens, will be exactly this: this build ran on that satellite's computer, and the records that came down verify against these keys. Nothing more.
08 Out of scope

What ORBIT deliberately does not do.

HARDWARE

No new hardware

Stage 3 runs as software on a host's payload computer. ORBIT builds no optical terminals, no photon sources and no radiation-hardened roots of trust.

LINK SECURITY

No replacement link security

Receipts countersign around the existing protected link and never become part of the command path.

STANDARDS

No protocol of its own

ORBIT works inside existing space data-link standards and publishes profiles, not a competing protocol.

AUTONOMY

No targeting or autonomy algorithms

ORBIT records what an autonomous system decided and under which authority. It builds no decision logic and does no weapons work.

SAFETY

No claim about command safety

Receipts cover authentication, integrity and validity. Whether a command was safe is the mission system's call.

KEYS

No production keys in flight

The Stage 3 container carries mission-test keys only. Production signing keys never go up.

09 Questions

What reviewers ask about ORBIT.

Is ORBIT running on any spacecraft today?

No. Stages 1 and 2 are built and run in simulation. The Stage 3 flight container is built, reviewed internally in five dated review rounds and founder-approved, and the orbital run is planned with a host satellite operator. Nothing has flown yet, and no flight qualification is claimed.

Who is the host satellite operator?

We do not name operators, launch providers or vendors on this site. The operator will be named, if at all, only with their agreement and after the run.

What does "founder-approved" mean?

The flight container went through five dated internal review rounds by reviewers who did not build it, and the founder approved the frozen build. It is an internal engineering sign-off for a hosted software run. It is not an independent audit and not a flight qualification.

Does ORBIT replace our link encryption or command authentication?

No. It wraps the existing chain. The link keeps its protection; ORBIT adds a ground-minted receipt bound to the sequence count and the acknowledgement, which a third party can verify later.

How is ORBIT different from COSRYX-WATCH?

COSRYX-WATCH is the COSRYX product for conjunction and anomaly alerts. ORBIT is the programme for trusted software running in orbit and the evidence it leaves. They share the same receipt format and nothing else.

Which algorithms does ORBIT use?

Receipts are hybrid-signed with Ed25519 and ML-DSA-65 through the DCS R-Series engine; key agreement on the ground is planned to use X25519 with ML-KEM-768 (the X25519MLKEM768 hybrid) as the baseline, with ML-KEM-1024 for defence programmes. A stronger defence parameter set (ML-DSA-87, ML-KEM-1024, SHA-384) is planned, per programme.

Is "verifiable for decades" a property of the receipt?

No. Long-horizon verification is custodial: a named custodian renews the evidence as algorithms age, and witnesses cosign checkpoints. See the archive page.

A receipt made now must still verify at the inquiry.

ORBIT keeps the claim small and the evidence complete: what ran, what it was told, what it refused, and what it recorded while nobody was listening.

The Stage 3 runDecisions under link loss