AquaOS pricing
AquaOS is quoted per operation rather than sold from a price list. This page explains exactly what drives the number, what is included, and what a quote looks like, so you can size it before you talk to anyone.
- Quoted per operation
- Priced on sites, units and devices
- Software works without hardware
- No implementation fee to start
What the price is based on
Four things move the number. Nothing else does.
Number of sites
A site is a physical location with its own growing units and, usually, its own team.
A single farm is one site. An operation with a hatchery in one place and grow-out ponds in another is two. Multi-site operations pay more because they use the rollup, role and reporting layers that a single site does not.
Number of growing units
Ponds, tanks, raceways, cages and incubators.
This is the main driver, because it tracks how much production the platform is actually carrying. A pilot on three tanks and a farm with two hundred ponds are not the same product usage, and are not priced as though they were.
Connected devices
Controllers and the sensors attached to them, if you use the hardware layer.
Devices carry a per-device cost covering cellular connectivity and the ingest and storage of continuous readings. Operations running AquaOS on manually entered data alone have none of this.
Users and roles
Included rather than metered in most cases.
Field staff who only confirm feeding and log mortality are not charged as full users, because charging per seat pushes farms to share logins, which destroys the audit trail the platform exists to keep.
How a quote is put together
-
Describe the operation
Sites, roughly how many growing units, which species, and whether you want sensors now or later. Ten minutes on a call is usually enough.
-
Demo on your scenario
The platform is walked through on your production model rather than a sample dataset, so the scope of what you actually need is clear before anything is quoted.
-
Written quote
A fixed annual figure for the software, and a separate itemised list for any hardware. No bundling of the two, so you can see what each part costs.
-
Start where it is useful
Most operations start on one site or a subset of units and widen once the daily workflow has stuck. The quote is re-based when you widen, not charged upfront for capacity you are not using.
What is not charged separately
Setup and configuration
Defining sites, growing units, species, cultivation phases and the feed matrix is part of onboarding, not a professional services line item.
API access
The REST API and outbound webhooks are part of the platform. There is no enterprise tier that unlocks your own data.
Updates and support
Platform updates and support are included. There is no version you have to be migrated onto later at cost.
Frequently asked questions
Why is pricing not published as a table?
Because the same figure would be wrong for most readers. A three-tank pilot and a twelve-site operation with two hundred instrumented ponds are the same product but not the same deployment, and a published tier would either overprice the first or underprice the second. What is published here is the model, so the number is predictable before you ask for it.
Is there a minimum contract length?
AquaOS is quoted annually. There is no multi-year lock-in requirement to get a normal price, which is a common condition elsewhere in this category.
Do we have to buy hardware?
No. The platform works fully on manually entered production data, and many operations start that way. Sensors are quoted separately and can be added later, on the units where continuous monitoring actually changes a decision.
Is there an implementation or onboarding fee?
No. Defining sites, units, species, phases and the feed matrix is part of getting started. If an operation needs data migrated from an existing system, that is scoped separately and quoted before any work begins.
What happens to the price if we grow?
The quote is re-based at renewal against the sites, growing units and devices actually in use. Adding units mid-year does not trigger an immediate charge, and shrinking is reflected at renewal too.
See AquaOS on your operation
Bring a real production scenario. AquaOS is walked through on your operation, not a canned dataset.