Our own satellite · Status as of 21 October 2026

A test bench we own.

A COSRYX-owned 6U CubeSat would let us test our payload on our own terms: power-cycle it, check that it re-acquires the signal, and run controlled fault drills, with every step receipted. It is a plan, at the planning stage.

Format6U CubeSat
Target~18 months after radiation testing
Depends onFunding · licensing
StatusPlanning
01 Why our own

Evidence about failure needs the freedom to cause it.

The most useful tests of a mission recorder are the uncomfortable ones: switching the payload off mid-task, losing the link on purpose, injecting faults. No one lends their satellite for that.

A satellite we own removes that barrier. We can run the same drill a hundred times, change one thing, and run it again, with every command, decision and health reading going into the chain.

It also gives the recorder something it has never had: real orbital conditions. That matters, because today everything is simulation-validated or ground-demonstrated, and nothing has flown.

02 Inside the CubeSat

Six blocks in a 6U frame.

A concept layout, not a final design. A 6U CubeSat is roughly the size of a large shoebox; every block below has to fit, and share power, inside it.

6U concept · planning01 / 07
01 · PAYLOAD

The COSRYX recorder

The reason for the satellite: the COSRYX V2 mission recorder and the health heartbeat, running on flight-like hardware and writing every record as a receipt.

02 · ON-BOARD COMPUTER

The vehicle's own brain

Runs the satellite. The payload records what it commands and how it behaves, so the bus itself becomes part of the evidence.

03 · RADIO

The link we will break on purpose

UHF and S-band communications. Re-acquisition tests start here: drop the link, then prove the backlog arrives intact.

04 · ATTITUDE CONTROL

Pointing

Keeps antennas and panels where they need to be. Its own decisions are recorded like any other autonomous action.

05 · POWER

The electrical power system

Solar wings and power distribution. Power-cycling the payload, and shedding load, run through here.

06 · BATTERY

What gets us through eclipse

The battery's health is exactly the kind of slow drift the heartbeat is designed to catch.

07 · THE WHOLE

Every block, one chain

Commands, decisions and health from every block land in one receipt chain that anyone can verify on the ground.

03 The three test campaigns

What we would do with it on day one.

01 · POWER

Power-cycle the payload

Switch the recorder off and on, cleanly and abruptly. Prove it comes back with its chain intact and that the gap is recorded honestly.

02 · LINK

Re-acquire the signal

Lose contact, keep recording, regain contact. Prove the backlog is forwarded in order and nothing is missing or altered.

03 · FAULTS

Controlled fault drills

Inject faults deliberately and watch detection, quarantine and recovery happen, then check the record of it on the ground.

04 One drill, receipted

How a fault drill becomes evidence.

Intent

Ground signs the drill

The drill and its limits travel as a signed intent.

Inject

The fault is introduced

The payload records exactly what was injected and when.

Verify

Anyone checks it later

The chain shows the whole drill, start to finish, offline.

05 Order of work

Radiation first. Then the satellite.

The CubeSat comes after radiation testing for a reason: we will not put the recorder in orbit before we have seen it handle real particles on the ground.

The target is about 18 months after radiation testing. If funding allows, a second, larger CubeSat follows, so DCS operates its own satellite capacity.

See the full roadmap →

06 The ground segment

Every pass ends in a check.

Each time the CubeSat passes over a ground station, its backlog of receipts comes down. The first thing the ground does is not to read the data but to verify it: recompute each hash, check both signatures and walk the chain.

A pass that arrives with a gap, a duplicate or an edit is flagged before anyone acts on it. That is the same verifier a third party would use, on the same receipts.

07 Limits

What this page is not saying.

Planning

  • A concept layout and three test campaigns
  • A target of about 18 months after radiation testing
  • A second, larger CubeSat if funding allows

Not in place

  • No launch contract is signed
  • No licences have been granted
  • No hardware supplier is announced
  • Nothing is flight-qualified
08 Questions

About the CubeSat.

Why 6U?

It is a common CubeSat size with enough room and power for a recorder payload alongside the bus, at a scale a research initiative can realistically fund.

Who will build and launch it?

Not decided and not announced. No launch contract is signed.

Will partners be able to fly experiments?

That is part of the reason for the larger, second CubeSat, if funding allows. Talk to us if you are interested.

Will the data be public?

Our intention is that receipts from the test campaigns can be verified by third parties. What is published, and how, will be decided with the mission design.

09 Get involved

Help us put the recorder in orbit.

Funding, licensing advice and research partnerships move this plan forward.

InvestorsContact