Space-RF

Distributed Systems for
The Ocean and Space

An uncrewed vessel is a distributed system: many computers inside one hull, and many hulls across the sea. We twin that system, run its real code, and replay any failure exactly, so it is proven before it sails.

Where we work
Ocean · now Air · next Space · later
Zero new issuesat the first sea deployment of a product built in our twin
Exact replayevery failure is a file, fixed rather than chased
Bit for bitone run key gives the same result on any machine
Why · the real problem

Today's "autonomous" boats are driven from shore.

Removing the human is a distributed-systems problem, twice over.

Micro · inside one boat

A distributed system in one hull

Many computers, sensors and one clock, in one hull.

Inside one USV A hull containing an autonomy computer, an autopilot MCU, a radio board and sensors, all joined by an onboard network that shares one clock. onboard network Autonomy computer planner · ROS 2 Autopilot MCU firmware in C Radio board ARM · VHF radio Sensors radar · AIS · GNSS one clock
  • Messages race. Two computers act on the same event in a different order.
  • Clocks disagree. Every board keeps its own time; the fusion trusts them all.
  • One board reboots. The rest carry on with a picture that is now wrong.
Digital twin

We twin it down to the code, run the real software, and replay any failure exactly.

Macro · across boats and shore

A distributed system across the sea

Low power. Links that come and go. Satellite-denied.

Across boats and shore A shore operator linked to three USVs over VHF and HF; one link is down, the boats also link to each other, and there is no satellite. ✕ link down VHF HF mesh Shore operator USV USV USV satellite low power · intermittent the human still in the loop
  • Links drop. A boat is out of reach exactly when it needs a decision.
  • Power is scarce. Every message and every retry costs battery.
  • No satellite to lean on. The fleet must agree with the links it has.
Built for it

Radio, messaging and consensus designed for links that come and go, then proven in the same twin.

Cloud systems assume steady power, reliable networks and good clocks. At sea, none hold.

Everyone twins the physics. We twin the distributed system.

The digital twin · as it runs today

Not a twin of the hull. A twin of the distributed system.

Each part of the boat and its shore has a counterpart in the twin. Where it is software, the twin runs the same software, unchanged. Where it is the world, the twin models it deterministically.

At sea
In the twin
Under the twin
Planner and autonomyPython, or a ROS 2 stack with Nav2
The same code, unchangedIn lockstep: it never runs ahead of simulated time.
Autopilot firmwareC, on the boat's microcontroller
The same source, built for the hostIn lockstep over a small C protocol.Roadmap: the unchanged binary on an emulated MCU
RadioRoIP on an NXP i.MX8M Plus, driving a marine VHF set
RoIP, unchangedBehind a virtual radio that answers its control frames as the real set does.
SensorsRadar, AIS, GNSS, camera, echo sounder, sonar
Deterministic sensor modelsDetection-level, with faults and GNSS spoofing.
Ocean and chartWaves, wind, current, tide; S-57 charts
Deterministic worldThe chart the planner believes, kept apart from the true seabed.
The air between radiosVHF over water
Deterministic RF modelPropagation, noise, squelch, capture, dual watch.
ShoreRelay server and operator consoles
UnchangedOperators work the twin exactly as they work the fleet.
Deterministic core

One run key. Bit for bit.

Integer-nanosecond event kernel, seeded randomness, its own maths. The same state hash on any machine.

Oracles

Every run is judged

  • Collision rules (COLREG)
  • Closest approach
  • Grounding, whole-hull clearance
  • Lanes, restricted areas, arrival
Evidence

Every failure is a file

Replay it, rewind it, shrink it to its cause, bisect it to the commit.

This is the twin that exists today. RoIP, our radio system for uncrewed boats, was built inside it and went to sea with zero new issues.

gSD/T · the platform

The incubation and simulation platform for maritime autonomy.

Six layers, built on a deterministic core. Your planner, charts and firmware plug in unchanged.

  1. 6Search and evidence
    Find→Replay→Shrink→Fix→Prove→Release
  2. 5Customer plug-insPlanner, chart and firmware, unchanged
  3. 4OraclesCOLREG · closest approach · whole-hull clearance · lanes
  4. 3Maritime worldOcean · hull · radar · AIS · GNSS · sonar · charts · datums
  5. 2Component SDKDeclared ports, units, state · 0.2 s check · lint
  6. 1Deterministic coreInteger-ns kernel · own maths · seeded randomness · hashes

One run key.
Bit for bit.
Any machine.

  • No rewrite to adoptTeams bring their real software and charts.
  • Judgement, not picturesA simulator becomes evidence.
  • Correct from build oneUnder 2 s to a checked component.
  • First failure to releaseThe same loop on every release.
1 · TodaySimulation

Thousands of voyages on the boat's own code.

2 · NextComponents

Real autopilots, sensors and radios plug in, one at a time.

3 · NextDry dock

The finished hull, on blocks, runs the same voyages.

4 · The outcomeSea trial

Once, low risk, to sign it off.

The same voyages and the same pass/fail checks at every step, so nothing new is found at sea.

Products

Built inside gSD/T. Each one sells on its own.

Every component was built and proven on gSD/T, and each one built there makes gSD/T stronger.

Fielded

RoIP

Radio over IP for uncrewed boats: a VHF voice that shore can operate. Zero new issues at its first deployment; chosen over the incumbent on security.

Available

Simulation lab

Real boards, radios and timing beside their exact digital twin, as a service.

Beta

Security and PKI

Fleet identity and trust, tested inside gSD/T from the first build.

v0.8

SRF-DB and ChronoQuorum

The boat's database, messaging and consensus, deterministic at sea too.

USV · now UAV · next Space · later

The same distributed-systems problem, in every place without a crew.

About

Built by distributed-systems engineers.

Chiradip Mandal, founder, built and architected the databases behind Apple Music and Commerce, and has spent the years since on uncrewed vessels, maritime radio and satellite ground systems.

Distributed systems are our superpower, and we understand the constraints the USV industry imposes: power, links and clocks that cannot be taken for granted.

Contact

Prove it before it sails.

Tell us about the vessel, the software and what it has to prove. Expect a human reply within two business days.

Or write to chiradip@space-rf.com