Coastlines

Where every buoy goes,
and what it really covers.

A coastline and a budget of buoys in, a defensible sensor barrier out. PHAROS clips every footprint against the seabed, scores the barrier as a probability rather than a picture, and keeps that barrier honest for its whole service life. Self-hosted, air-gapped, vendor neutral.

Plan · Watch · Tend · Ledger

PharosGulf coast · 4 buoys moored
Shoreline 2019
2026
Sector 07 · Hs 1.4 m · 41 km surveyed
Retreat −1.8 m / yr
Decision
Renourish sector 07 before the winter cadence.

Terrain-masked coverage

The datasheet draws a circle. The seabed does not.

PHAROS walks the depth profile out along every azimuth from the node, finds where the geometry stops the sensor, and returns the polygon that survives. A barrier that looked continuous on a range map usually is not, and it is better to have that argument at the planning table than after an incident review.

Radar and sonar

Protected water is the intersection.

A sonar contact is worth something operationally where the radar picture is also clear, because that is where it can be resolved and acted on. Take the union of the two footprints, as most planning tools do, and you overstate the coast by a margin nobody wants to explain afterwards.

Detection probability

A barrier is a probability.

Covered or not covered is what the market reports. PHAROS computes detection probability across every overlapping sensor on a crossing track, over the whole set of tracks, and reports the weak one. That is the track that gets used, so that is the number the barrier should be judged on.

The gap

Four industries touch this. None solves it.

Aid to navigation monitoringWatches buoys already in the water. Silent on whether the chain ever made sense.
Metocean fleetsCapable fleet interfaces. No tactical reasoning of any kind.
Subsea positioningSolves a target inside a known array, and assumes the array exists.
Coastal surveillance command systemsConsume sensors. They do not decide where the sensors go.
PHAROSThe planning layer none of them have.

Platform

Four modules.

01 Plan

Design the barrier

A sector and a number of nodes in. A costed layout, a gap list and a verdict out, with the reasoning attached to each.

02 Watch

Feed your command system

A sensor source for the command system you already operate, not a second screen for the watch officer to ignore.

03 Tend

Before the gap opens

The date and the kilometre where the barrier will fail, and the boat routed to it while it is still maintenance rather than an incident.

04 Ledger

Prove it later

Hash-chained decisions, role-gated export and authorisation dossiers, so a layout can be defended years after it was signed.

Deployment

Built for buyers who cannot use a cloud.

Air-gapped appliance One database per customer Silent and public regimes Vendor-neutral sensor catalogue Hash-chained decision log Role-gated, audited export Edge processing, metadata uplink
Dual use

Export control review

PHAROS is dual-use software subject to export control review. We establish the end user and the jurisdiction before a technical conversation goes further, and we decline the enquiries we cannot place. The full position is on the trust page.

Isolation

Your installation is yours

A separate deployment per customer rather than a filter in a shared database, up to an installation with no public hostname at all and updates delivered as signed images.

Book a briefing

Name the sector and what has to cross it.

Give us a stretch of coast, the sensors available to you and the traffic you care about. We return the coverage the seabed actually allows, the gap list, and the probability the barrier would hold at its weakest crossing.

Enquiries are subject to export control review. We establish the end user and the jurisdiction first.