Manolin is an aquaculture intelligence company. Our two products (Watershed, for farm operators, and Harpoon, for suppliers) are built on a shared data infrastructure purpose-built for the biological and operational complexity of fish farming.
Manolin wins through its architecture. The data problem in aquaculture is not a shortage of sensors or software but the absence of a foundation that makes the data those systems generate trustworthy enough to model from. For years, that foundation has been missing. Every farm runs its own disconnected internal data stack with each technology vendor storing data differently. Each integration breaks when the biology does what biology does — i.e. fish move, populations split, production cycles span years across completely different environments.
Intelligence is only as good as the data underneath it. Farms have to get their data architecture right first.
Below, we detail the architectural decisions behind Manolin's data foundation: why we made them, what they make possible, and why they compound in ways that systems designed for a different purpose cannot replicate.
Aquaculture intelligence requires data infrastructure capable of representing biological reality, not just recording operational events from the farm. The foundation of this data must be continuous, not periodic. It must track populations, not just locations. And it must be clean and structured from the moment data arrives into a system, not as a downstream cleanup step that introduces delay and compounds error.
Our platform is built around three core commitments:
The architecture addresses a problem that is both a data engineering challenge and a biological one. Fish farms generate data from feeding systems, environmental sensors, biomass estimation tools, lice counting cameras, health records, and production management systems. Each unique farm is running on different technology stacks, recording data in different formats, at different temporal resolutions, and using different identifiers for fish.
No single system was designed to integrate with the others. No common standard exists for how operational data should move between them. The result is that data which is individually accurate becomes collectively meaningless because there is no shared structure that allows it to be connected and reasoned about together.
Our architecture resolves this at each layer: ingestion, normalization, biological modeling, and intelligence delivery. Each layer operates continuously and independently, so that the foundation strengthens in real time rather than degrading between manual updates.
Aquaculture data does not arrive in a clean stream. It arrives from hardware APIs, manual entry systems, vendor exports, and proprietary protocols. These are often inconsistent, with gaps, and with no guarantee that the same data event is recorded the same way twice. Our integration layer is built to handle this reality without requiring farms to change the systems they already run.
This is not a one-time ETL process. Integration runs continuously, so that every new data point is incorporated into the unified structure as it arrives, not at the next export cycle.
Raw data from aquaculture systems is inconsistent in ways that go beyond simple formatting differences. Vendors use different terminology for the same concepts. Units fluctuate. Recording conventions change when software is updated or staff turns over. A field labeled "mortality" in one system may represent daily count, cumulative count, or percentage and the difference matters enormously for any downstream calculation.
Our normalization layer resolves this systematically:
The result is a dataset that can be compared across farms, across vendors, and across time — without the silent errors that accumulate when normalization is treated as an afterthought.
This is the core architectural decision that separates Manolin's foundation from every farm management and analytics system built before it.
Existing aquaculture systems track data at the cage level. When fish are transferred between pens (for grading, treatment, or management) the data record resets. When populations from multiple pens are combined, their histories merge without any mechanism for maintaining continuity. The cage-level model is operationally convenient and biologically meaningless: it ties outcomes to locations rather than to the populations that produced them.
Manolin tracks at the population level: the biological unit that actually carries the fish health history.
Population tracing cannot be bolted onto a cage-level system through a software update. The biological continuity of fish groups has to be the organizing principle of the data model from day one, not a feature layered on top of records that were never designed to carry it. This is the structural change that makes FCR calculations reliable, that connects treatment events to health outcomes with enough causal resolution to learn from, and that allows performance comparisons across cohorts, farms, and production generations to mean something.
The analytics Manolin delivers are built directly on the population-traced, normalized, continuously-maintained dataset described above. It is intelligence that is only possible because the data underneath it is structured correctly.
Every analytical capability compounds with every new data connection. Each farm that joins our network improves the benchmarks. Each production cycle adds depth to the historical record. The architecture improves continuously, not by releasing new features, but because the data that powers it keeps getting richer.
The same architectural foundation powers two different access modes, depending on how a customer wants to engage with the data.
The architecture is designed with the assumption that the intelligence requirements of the industry will continue to advance, and that advancing them requires a data foundation capable of supporting methods that do not yet exist at commercial scale in aquaculture.
The internal data architecture most farms built were developed over time without a clear plan. A feeding controller added here, a lice camera there, a spreadsheet stitching the gaps between them. Each solving an immediate problem, but none designed to connect with the others. Over time for every farm, the manual steps have accumulated. The questions that matter most to farm managers (however) remain unanswerable.
Every layer of Manolin's architecture reflects a decision made specifically for the way aquaculture data behaves — biologically complex, operationally fragmented, and too important to leave unstructured. We have built the foundation the industry's intelligence has always required. The result compounds with every farm connected, every production cycle completed, and every data source added to the network.
Ready to connect wherever you farm.