# OceanOps · Selected work · ZAC

> A working prototype of an operating layer for reef-crisis response, from live ocean data to staged action and audit-ready reports, built solo with AI.

Source: https://zanatelloacosta.com/work/oceanops

Case

# OceanOps

A working prototype of an operating layer for reef-crisis response, from live ocean data to staged action and audit-ready reports, built solo with AI.

[Visit oceanops.tech](https://www.oceanops.tech/)

Own venture · OceanOps Ocean and climate risk 2025–2026

![OceanOps live crisis map and alert list, dithered](https://zanatelloacosta.com/_astro/oceanops.BwvI_lS7.png)

## Outcome

Own venture · OceanOps

-   Prototype

    Working platform, built solo

## The work

**Context:** Reef crises such as coral bleaching have early alerts, response capacity and funding, but no shared workflow that connects them.
**Friction:** Alerts arrive, but turning them into a coordinated response, tracking it in the field and proving the result to funders happens by hand, across scattered tools.
**Intervention:** A platform that ingests public ocean data every day, classifies each event by severity and urgency, triggers a staged response protocol, tracks field actions and exports audit-ready records.
**Adoption:** Prototype in use, in conversation with reef programmes about a tailored pilot. Not yet in paid use.
**Role and scope:** Founder. Designed and built the whole platform on my own, from data ingestion to reporting.

### Deliverables

-   Daily data ingestion from public ocean sources (NOAA, Copernicus)
-   Live dashboard and crisis map
-   Severity and urgency staging, with a coral-bleaching trigger
-   Response protocols, field tracking and audit-ready exports
-   Methodology and technical documentation

## In short

OceanOps started from an operations problem, not a technology one. Reef programmes already receive alerts when water gets dangerously warm, and there are teams and funds ready to act. What is missing is the operating layer in between: who acts, on which reef, in what order, and how to prove afterwards what was done.

I built the whole platform myself. Every day it ingests public ocean signals, classifies each event by severity and urgency, and stages a response with clear protocols. Field actions and evidence are logged as the response unfolds, and the platform exports structured records that a funder or insurer can audit.

AI was part of the work in two ways. It helped me develop and test the platform much faster than I could have alone. And a parallel beta system read the live data with me, surfacing patterns and forecasts that I used to tune the coral-bleaching trigger, with the logic always mine and checked against the science.

OceanOps is a prototype today. It is the kind of system ZAC builds for clients: real data in, a clear decision, a staged action and a record of what happened.

### Evidence

Own venture, not ZAC client work. No figures from the product's marketing are used here; those are illustrative.

Partner and prospect names, funding and roadmap are not published.

[All selected work](https://zanatelloacosta.com/work) [Next case: Scout](https://zanatelloacosta.com/work/scout)

[Discuss a similar problem](https://zanatelloacosta.com/contact)

---
Zanatello Acosta Consulting · Org.nr. 938 525 390 · Øyer, Innlandet, Norway · post@zanatelloacosta.com · https://zanatelloacosta.com
