Oil Spill Response

BirunIQ SpillTrace

9 department modules, all nine with a working console.

From the trailer · demonstration data
Industry served

Coastguards, environment ministries and port authorities

the party carrying the coastal duty, which is rarely the party carrying the operating duty.

SpillTrace records an incident, the slick area seen on each pass, and the receptors in its path. Drift and trajectory, escalation, shoreline survey, response assets and remediation follow from the same record.

Records in the demonstration are synthetic, and each one says so.

Department modules

9
each owned and accountable on its own.

01SpillTrace Command

The live incident, where it is predicted to go, and who is in its path — with the parts nobody has assessed shown as unassessed.

02Detection

Phase A: dark-patch candidates from a self-hosted Sentinel-1 tiler, called candidates until look-alike screening lands.

03Drift & Trajectory

An ensemble, not a line — and a run nobody computed has to say so rather than render an empty envelope.

04Receptor Readiness

Desalination intakes, nurseries, landing sites and berths, led by the ones nobody can currently act for.

05Escalation & Alerting

Keyed to how long there is to act rather than to severity, with a state that plainly means we cannot say.

06Incident Record

What was true and when we knew it — corrections supersede rather than overwrite, enforced at the database.

07Shoreline Survey (SCAT)

SCAT segments as surveyed, with the shore nobody has looked at held apart from the shore found clean.

08Response Assets & Tasking

Booms, skimmers, vessels and crews against the protection gap. The ensemble optimiser is designed, not built.

09Remediation & Waste

Cleanup as a capacity problem — recovered volume against somewhere lawful to put it — and the evidence pack that closes it.

Nine consoles live · detection in phase A · forecasts labelled simulated
AI decision support

One analyst across every source the asking user can see, inside that user's grants.

“Which receptors does this spill reach first, and which of them can nobody act for?”

The platform resolves

Runs the drift ensemble against the receptor registry and reports arrival by lead time — leading with the receptors that have no response arrangement behind them.

The guardrailA receptor with no data is not a receptor that is safe, and an unwatched sea is not a clean sea. Readiness leads with what is missing.
Same platform underneath
Shared

One map, one catalog, one sign-in

SpillTrace runs on the same engine as every other edition, with 30 shared capabilities built once.

Deploy

SaaS, sovereign hybrid, air-gap capable

Licensed per tenant, data kept apart by row-level security, access scoped by team. Sovereignty →