ORBIT brings the R-Series trust layer to spacecraft. Commands are signed and checked on board. Autonomy changes are signed. Mission logs come back to the ground as evidence anyone can verify.
A satellite flies for twenty years. The keys that command it must outlast the algorithms of today.
Every command is signed on the ground and checked on board before it runs. A replayed or altered command is refused, and the refusal is logged.
When the link drops, the spacecraft moves from operator-linked to degraded to autonomous. Each change is a signed decision record, not a silent switch.
Logs come down as a hash-chained, signed record. Two independent verifiers, in two languages, must reach the same verdict.
Command verifier, mission log, signed trust anchor and a link-loss simulator with 48 scenarios. Built and validated in simulation.
Signed decision records, autonomy modes and multi-station quorum. Validated in simulation.
Our flight software as a container on a host satellite’s payload computer, with logs downlinked and verified on the ground. Software built and founder-approved after five dated review rounds across two model families; records held internally.
ORBIT on partner spacecraft and ground segments, after the Stage 3 run is accepted.
A simulation of the planned run: the container is delivered, the host loads it, commands go up, logs come down, and the ground verifies every entry. It is a simulation, not footage.
After the orbital run, the claim will be: this named build ran on the named host computer, and its returned logs verify under the stated keys. Nothing is flight-qualified and nothing is certified. Until the run happens and the downlink verifies, we say “orbital test planned”, never “ran in orbit”.