Professional intelligence
The public site and the professional layer share one data model. Pro is not a separate product built later on different foundations — it is the same entities, observations and sources, with depth and access that a professional user needs.
What the data model already supports
Utility intelligence
Ownership, regulation, service area, sources, performance and enforcement history, with every figure sourced.
Infrastructure
Treatment works, wastewater plants, desalination, dams and transfer schemes as first-class entities with capacity, operator and location.
Project tracking
Built entirely from open procurement notices, planning applications, environmental permits and regulatory determinations — lawfully, and independently of any proprietary market intelligence product.
Tariffs and bills
Structured tariff components with the jurisdiction and charging model recorded, so cross-country comparison is possible without being misleading.
Benchmarking
Comparable metrics with their comparability rules attached, so a benchmark cannot silently compare two different definitions.
Incidents and enforcement
A structured ledger linking events to geography, utility, contaminant and water body, with cause, response and outcome.
Sector water use
Withdrawal and consumption held separately throughout, including the data centre and AI layer with disclosure basis recorded.
API access
The static API already exposes the full model. A commercial tier would add history, higher-resolution data and support rather than a different model.
The first thing that will need an account
Hydrionis has no accounts, and adding them to look commercial would be the wrong reason. Almost everything a professional user wants can be served without one: the data is static files, so there is nothing to throttle; a saved comparison can live in the browser; and the licences are open, so a commercial user needs permission from nobody. Each of those would be authentication in search of a purpose.
One feature genuinely cannot work without it. An alert has to reach a person — a reservoir crossing a threshold, a gauge reading outside its own historical range, a drinking-water determinand moving — and a notification needs somewhere to go and someone who chose to receive it. That is a real user boundary rather than a commercial one, and it is the point at which accounts stop being decoration.
Private organisation datasets are the second, for the same structural reason: data that belongs to one organisation cannot be served from a public file. Neither exists yet, and neither will be built before the thing it exists for does.
Whether the data is timely enough to alert on
Assessed rather than assumed, because an alert built on a stale feed is worse than no alert. Most of what Hydrionis holds cannot support one and never will: a statutory annual return published a year in arrears is a historical record, and there is no threshold worth notifying anyone about a year after it was crossed.
Two sources changed that in Sprint 5. The German federal gauges and the Dutch national network both publish continuously, at fifteen- and ten-minute resolution, and Hydrionis stores daily means from both. That is genuinely timely enough for a threshold alert on river level or discharge — the first data in the platform that is.
What Hydrionis will not do
Hydrionis does not and will not replicate proprietary market intelligence products. Where a commercial source is the recognised reference for an area — desalination market data being the clearest example — Hydrionis records that it exists, does not purchase or ingest it, and builds equivalent factual coverage independently from lawful open sources. That distinction is recorded on the relevant source pages.
If you need data now
The public data layer is free and open, and data enquiries are welcome from journalists, researchers, developers, businesses, utilities, consultancies, NGOs and public bodies.