Features

See the gradient before it becomes an event.

Bathys turns 4,092 moorings into one operator console: every reading placed on the topology, every anomaly opened with the minutes you have left, every automated action logged for a human to override.

Ocean Buoys
4,092 live
Acoustic Latency
12ms avg
Readings Sampled
2.4B / day
Mean warning lead
11 min
Why an array

A sensor tells you what happened. The array tells you what is about to.

Four things a single instrument cannot do, and what Bathys does instead.

  1. 01

    A sensor reports a value.

    The array reports where the value is going: gradients are evaluated along the topology, mooring by mooring.

  2. 02

    An alarm fires when a threshold is crossed.

    An event opens eleven minutes earlier, on the slope of the signal, with the lead time shown next to it.

  3. 03

    Automation acts, and you find out later.

    Autonomous rules act inside the warning window, log every decision and leave the operator a hold.

  4. 04

    The seafloor model is whatever the last survey left.

    Every transit is a survey. The bathymetry model is versioned, diffed and never older than the last passage.

N-ATLANTIC 00:00:00 UTC
RELAY MESH · 3 BASINS · 14 MOORINGS
MooringRelayPacket
M-09 · 3,164 M · WATCH
Topology · packets in transit
Command layer

Six modules, one console.

Each module answers one operator question. None of them hides a signal to look calm.

  1. CAP_01

    One topology, not a list of buoys

    Live mooring relationships, cable interdependencies and acoustic relay pathways rendered as a single map. A noisy hop is re-routed before it costs you a reading.

  2. CAP_02

    Events with a lead time attached

    Seismic deviations, cascading current shifts and pressure thresholds surfaced as events, each carrying the minutes you have left to decide.

  3. CAP_03

    Autonomy that leaves a trace

    Ballast release and ascent policies act inside the window. Every action is logged with the rule that fired, and an operator hold always wins.

  4. CAP_04

    A system log you can diff

    Bathymetry syncs, model applications and topology changes are versioned. Two states of the array can be compared like two commits.

  5. CAP_05

    Maintenance before it is urgent

    Battery reserve and hull pressure per mooring, with a flag raised while a vessel is still in range rather than after it has left.

  6. CAP_06

    Models you roll out like code

    thermocline_alpha, salinity anomaly detection and pressure mapping ship through a secure CLI with a version, a diff, a shadow-sm mode and a one-command rollback.

How it works

Detect, interpret, act. In that order, every twelve milliseconds.

The engine ingests every mooring, places the reading on the topology, and opens an event on the slope of the signal. Autonomous response runs inside the window it just bought you.

  1. 01
    Detect

    Signal Detection

    Ingest normalized telemetry from sensor buoys, filter noise, and surface material state changes in real time.

  2. 02
    Interpret

    State Interpretation

    Cross-reference live conditions against historical tide models, current graphs, and defined pressure thresholds.

  3. 03
    Act

    Autonomous Response

    Execute ballast logic, reroute acoustic relays, and broadcast severity alerts before instability expands.

SYS_READY bash — bathys proc
sys@bathys:~/core$ bathys start --env abyssal
>
Initializing baseline metrics...
Ingesting 2.4M samples/sec
>
Continuous evaluation active
Salinity nominal.
>
Pressure gradient breach detected!
Executing ballast release payload...
>
Mooring isolated. Systems secure.
Latency: 12ms
sys@bathys:~/core$
From the log

What the array did, written by the people who were there.

All dispatches
Questions

What operators ask before a shadow-sm deployment.

Q02 Can Bathys read the moorings we already have in the water?

Existing instruments join the array through a relay buoy that timestamps and normalizes their stream before the first hop. They appear in the topology like native moorings; only the ballast-release policy is limited to Bathys hulls.

Q03 How do you keep the anomaly console from crying wolf?

Events open on gradients evaluated along the topology, not on single readings, and every event carries its lead time and the moorings that support it. Operators can close an event with a hold, and that hold trains nothing silently — it is logged and reviewed in the shadow-sm deployment report.

Q04 Who decides when a model changes?

You do. A model update arrives through the secure CLI with a version and a diff, runs in shadow-sm mode next to the current one, and is applied when you say so. Rolling back is one command, and the system log keeps both versions comparable.

Q05 Who owns the telemetry and the bathymetry?

The programme that collected it. Bathys keeps anonymized array statistics to improve the models unless you opt out, and never publishes a survey contribution without the owner’s consent.

Shadow deployment

Watch the console run on your own telemetry.

Before a single mooring is wet, we connect the engine to your existing feed and show you every event it would have opened, with the lead time it would have given you.