ORBIT · Stage 3 · Simulated

Our software, on someone else's satellite.

Stage 3 is a hosted software run: the ORBIT container goes up to a payload computer on a satellite a host operator already flies, runs for one booked orbit, and sends its signed record down to be checked on the ground. No new hardware. The run is planned; below, it plays out in simulation.

Flight containerFive internal review rounds · founder-approved
Orbital runPlanning
HostA satellite operator (not named)
01 The claim

Small on purpose.

When the run is done, ORBIT will claim exactly one thing: this build ran on that satellite's computer, and the records that came down verify against these keys. Nothing more.

Not radiation tolerance, not flight qualification, not that any command was safe. A small claim that a stranger can check from raw files is worth more than a large one they have to take on trust.

Everything the run needs to prove that is already fixed: the image digest is frozen before launch day, the keys are mission-test keys made for this run only, and the verifier and test vectors are ready on the ground.

02 The run, simulated

Two minutes forty-five, prep to proof.

An interactive simulation of the whole run: the satellite, its pass over the ground station, the uplink, the blackout and the downlink, with the mission log filling in as receipts are made. Pause, restart or scrub the timeline. Captions and step titles are in English, and the eight steps are also written out below.

Simulated  Pass lengths and timings are illustrative; real values come from the host's schedule. Open full screen.

03 Eight steps

From a container on the ground to a verified log.

01 · PREP

Ground preparation

The ORBIT ARM64 container is built: command authoriser, signed mission recorder and receipt signer. Separate mission-test keys are made for the run; production keys never go up. The offline verifier and test vectors are ready.

02 · HOST

Host contact and sandbox

The host receives a one-page intake sheet and six questions. The whole mission runs on the ground in the host's sandbox and its logs verify. In parallel, a software-only classification is requested from the national space regulator.

03 · FREEZE

Review, freeze, book

The host's engineer reviews the container. Its image digest is recorded, and after that not one byte changes. One orbit is booked, about 95 minutes.

04 · PASS 1

The container goes up

The satellite rises over the ground station and the link comes up. The container is uplinked, and the host gives a signed attestation: which satellite, which digest, at what UTC time.

05 · PROVE IT

Fresh challenge, three commands

A new random nonce goes up; receipt 1 echoes it, proving the software is running now, up there. Then three commands: authorised (accepted), without permission (refused), and a replay (refused). Every decision gets its own signed receipt.

06 · BLACKOUT

Out of contact

The satellite moves out of view. The software signs each mode change (operator-linked, degraded, autonomous) and keeps working. Each new receipt joins the hash chain and is stored on board.

07 · PASS 2

Everything comes down

The link returns. Every receipt stored on board comes down as raw signed bytes: no screenshots, no host-made summaries. The sequence runs 1 to 12 with no gap.

08 · VERIFY

Independent check on the ground

Our verifier runs on a separate machine. The claim is only that this build ran on that satellite's computer and the logs verify with these keys. No claim of radiation testing or flight qualification.

04 What the ground checks

Four checks. All four, or no claim.

SIGNATURES

Every receipt verifies

Each of the receipts in the simulated run (12 of 12) verifies against the mission-test keys, with both signatures required.

CHAIN

No gap, no reorder

Each receipt carries the hash of the one before and the next sequence number. A missing, inserted or reordered receipt breaks the chain and shows.

FRESHNESS

The nonce comes back

Receipt 1 echoes the random nonce sent on pass 1, so the record cannot have been prepared before the run.

IDENTITY

The digest matches

The host's signed attestation names the same image digest that was frozen before launch day, so the software that ran is the software that was reviewed.

The counts above come from the simulation. The real run will publish its own counts, its raw files and the verifier, so anyone can repeat the check.
05 Status

Ready on the ground. Planned in orbit.

ORBIT status as of 21 October 2026

ItemState
Stage 1 · ground trust layerBuilt · Simulation-validated
Stage 2 · autonomy and quorumSimulation-validated
Stage 3 · flight container (ARM64 Linux image, digest frozen)Built
Stage 3 · internal reviews of the flight containerFive internal review rounds
Stage 3 · sign-offFounder-approved
Stage 3 · orbital run with a host satellite operatorPlanning
Flight qualificationNot claimed
06 Films

The run, as a film.

01 · Software in orbit30 s · 13.5 MB
03 · Verified on the ground30 s · 10.9 MB
07 Questions

On the Stage 3 run.

Has the run happened?

No. The flight container is built, reviewed internally in five dated review rounds and founder-approved. The orbital run is planned with a host satellite operator. What you see on this page is a simulation.

Why not name the host?

We never name operators, launch providers or vendors on this site. A host may choose to be named after the run; until then it is "a host satellite operator".

What happens if a command is refused?

The refusal is the evidence. The container signs a receipt saying the command was refused and why (no permission, or a replay), and that receipt joins the chain like any other.

What if the link never comes back?

Then the records stay on board, sealed and chained, and nothing is claimed. The claim needs the raw files on the ground and all four checks passing.

Does Stage 3 make ORBIT flight-qualified?

No. A hosted software run shows that this build ran on that computer and that its records verify. No flight qualification is claimed, and nothing in ORBIT is radiation-tested.

The link drops. The receipts keep coming.

Signed and chained on board while nobody is listening, sent down on the next pass, checked on the ground by someone who did not write the code.

Decisions under link lossORBIT overview