About AquaOS
AquaOS is aquaculture production management software. It is built by the same engineering team that designs the sensors and field controllers it reads from, which is unusual in this category and is the reason the two halves fit together.
Where AquaOS comes from
AquaOS started from a hardware problem. The team builds water quality probes and the field controllers that read them and deliver data over cellular, and that hardware has been running on working farms for years. Seeing it in use is how the gap became obvious.
The gap is this. Continuous water quality data is only half of what an aquaculture operation needs, and on its own it answers almost nothing. A dissolved oxygen chart is not actionable without knowing which batch was in the tank, at what density, on what feed. Meanwhile the production side of the same farm was running on spreadsheets that stopped being accurate the first time a batch was split across two ponds.
AquaOS was built to hold both halves in one record. The production model came out of daily use at a commercial fish farm, which is why the operations that dominate a real week, splitting, sorting, co-mingling, and confirming what was actually fed, are first-class features rather than edge cases bolted on later.
AquaOS is developed by Agrinovo, a manufacturer of IoT sensors and controllers for agriculture and aquaculture. It has its own product and its own domain because a buyer evaluating a production platform should be able to evaluate it as software, not as a page inside a hardware catalogue.
Commitments that shape what ships
Only shipped features are described
Nothing on this site describes a roadmap item as though it exists. Every capability named on these pages is in the product today, and anything you ask about that is not here gets a straight answer from the team.
The data belongs to the operation
Exports and API access are part of the platform rather than an upgrade. A platform holding your production record and charging to read it back is not open, whatever its marketing says.
Estimates are labelled as estimates
Model-derived figures, such as biomass between samplings, are marked as such in the interface and in reports. A number presented with more confidence than it deserves erodes trust in every other number on the page.
Existing hardware stays in service
Sensor-agnostic is a design commitment, not a marketing line. Adopting AquaOS does not require replacing probes that already work.
See AquaOS on your operation
Bring a real production scenario. AquaOS is walked through on your operation, not a canned dataset.
Technical and commercial questions both reach the same team.
[email protected]