The softwareFor your teamProofSecurityAbout Watch a leak found Plan a demo
Real-time Water Intelligence

Leak found at 03:14.
Fixed by 06:40.

Three and a half hours from a joint failing on a 150 mm main to a crew closing the valve, reading sensors the utility already owned, with nothing new installed to find it. The same leak, found the old way, runs for sixty-one hours, and often for days or weeks. Guesswork ends here.

Watch a leak found (no form) See what the alarms missed
ISO 27001 certified NIS2 SC30 audited Your data stays in your region
● LEAK CONFIRMED ZONE 07-N
Detected03:14:22
Pressure Δ−0.42 bar
Est. loss18.4 m³/h
Localisedstreet level
Repaired06:40
CONFIDENCE 94%
00:00
03:14 · EVENT 24:00
1 → 9 in 10
leaks detected, before and after. Águas do Rio, controlled tests
250 × 250 m
the ground a crew has to cover. 99.4% of the mains in the zone are never walked. Nama Water Services, Ghala, Oman
95%
accurate alarms, measured across the networks we monitor over the last year
6 weeks
from contract to first confirmed detection
What we are

Leaks are the proof.
The network is the work.

We are not a leak-detection company that talks about intelligence. We are a water intelligence company that started with leaks. A leak is the one claim you can check against a hole in the ground.

Everything else a network knows is the same problem: measurement you already own, read properly, in time to act on it.

The network you can try

One morning,
step by step.

A reconstruction, built on how a real network behaves on an ordinary working morning. The hardest hour to find a leak in is the busiest one, so that is the hour this shows. Step through what the network did, what the alarms said, and what HULO did about it. Stepping through it asks nothing of you: no form, no salesperson, no booking. When a customer signs off a real event, this becomes that event.

06:00
NORMAL
The zone starts waking up.
Zone 12-W is coming off its night minimum. Inflow climbs as the first showers run, and pressure falls with it, because more flow through the same pipes costs more head. The model expects all of this. Nothing here needs a person.
Zone inflow
44.1 m³/h
Pressure vs model
0.00 bar
Alarms raised
0
Search area
n/a

That was one morning on a network we built. Ask us what it looks like on yours. We will tell you what your instrumentation can and cannot support before you sign anything.

Plan a demo

RECONSTRUCTION

One night · Zone 07-N · 14 March

Same data.
Two conclusions.

Nothing was added to this network. No new sensor. No new hardware. The only difference between the left panel and the right panel is what reads the signal. On the left is the alarm band configured in the utility's own SCADA, which is what most control rooms still run tonight.

The alarm band in your SCADA

STATUS: NORMAL

Night flow stayed inside the configured band, so nothing fired. The drift was real, but it was slower than the threshold and smaller than the noise. The leak ran for 61 hours before a customer called it in.

HULO

● DETECTED 03:14

The hydraulic model expected a pressure curve. The network delivered a different one. HULO compares measured against expected, per node, every minute, so a 0.42 bar deviation is not noise. It is a location.

To be clear about who this compares. It is not a claim that every vendor still alerts on thresholds: several of them forecast, and the good ones do it well. It is the comparison that matters to a utility deciding whether to change anything at all, because a configured alarm band is what is watching most zones tonight.

61 hours versus 40 minutes. And 61 is the good version of the old way: a leak this size is often reported days or weeks after it starts, or not at all. At 18.4 m³/h those 61 hours are 1,122 m³ of treated water, abstracted, dosed, pumped and lost. One event, one zone, one night. Multiply that by the number of zones you operate and you have your business case, before anyone mentions software.

The unused signal

A district metered area tells you water went in, and less came out.

It does not tell you where. A district metered area is measured at its boundary, so everything inside that boundary stays a single number, and the search starts from scratch, on foot, at night.

Read why we do not need your DMAs

HULO reads the pressure and flow sensors you already own, across zone boundaries and between them. Acoustic data is welcome too: we ingest it to confirm a location, not to compete with it. Most utilities are already sitting on the signal. It is simply not being read.

ZONE BOUNDARY IN OUT HERE
A METER AT THE BOUNDARY SEES ONE NUMBER.
THE SENSORS INSIDE ALREADY KNOW WHERE.
Every morning, in every control room

Six questions.
Same six, every day.

Five people run a distribution network, and between them they ask the same six questions every morning. Your utility measures more than it ever has, and still the answers come from whoever has been there longest. Experience is worth a great deal, but it does not scale, it retires, and it cannot be audited.

Show the six questions 6 questions
01
Leakage manager
Where is the leak?
Pressure and flow across the zone, compared against what the model expected, resolved to a street rather than a district.
02
IT / OT manager
Can we trust this sensor?
Every channel checked continuously for gaps, drift and impossible readings, before a bad signal costs you a night of fieldwork.
03
Control room
Is this an incident, or just noise?
One event with a confidence figure and an estimated loss rate, instead of forty alarms and a judgement call.
04
Asset manager
Which pipe matters most?
Assets ranked by what they actually carry and what fails if they go, not by installation date.
05
Leakage manager
Where should we send the crew?
Events ordered by water lost, customers affected and risk carried. The crew goes to the one that matters, not the one that shouted loudest.
06
Director
Which investment will actually improve the network?
Simulate the change before you commit the capital, against a hydraulic model that is updated from live data rather than rebuilt every five years.

Answering these with evidence instead of experience is the whole job. That is what Real-time Water Intelligence means.

You do not need more structure to understand your network.
You need the right insight, at the right moment.
Operational proof

Live networks.
Named utilities.

Production deployments, not pilots that were quietly parked. People whose names you can ask for at the next conference.

Open the results from four networks 4 utilities
Portsmouth Water
Binsted Ford & Yapton, UK · 10 controlled flushes
9 of 10
flushes landed inside the search area Portsmouth agreed beforehand
1.4%
tightest localisation achieved
May 2026
phase 3 of a five-phase programme
Aegea / Águas do Rio
Rio de Janeiro, Brazil · no DMAs
9 in 10
leaks detected, up from 1 in 10 (controlled tests)
2 km
search area, down from 500 km
300 → 100
sensors used, fewer, not more
Nama Water Services
Ghala, Oman · with Witteveen+Bos & BlueGold
250 × 250 m
the ground a crew has to cover: 99.4% of the mains in the zone are never walked
15 min
from activation to first detection
1 of 5
pressure sensors were working when we started
WML Limburg
The Netherlands · public utility
A public utility does not endorse vendors. What their process operator will say is that the analysis “can support operational awareness and help teams investigate events more effectively”, and no figure appears here, because none has been measured and agreed.
The Proofroom

Every claim,
with its receipt.

No proof means no claim. For every number we publish, you get what it means, how it was measured, at which utility, and what it does not cover. Including the parts that are inconvenient for us.

Open two claims, with their receipts 2 claims
Claim
9 in 10 detected
How it was measured
Controlled hydrant tests through a programme of sensor repositioning and data-quality work. The same tests found 1 in 10 at the start.
Where
Aegea / Águas do Rio, Rio de Janeiro, 2025–2026.
What it does not cover
Controlled tests, not real leaks. Moving to live events is the next phase, and the figure may move with it.
Claim
1.4% search area
How it was measured
Hydrant flush at an undisclosed location, expressed as a percentage of the main area, against a 25% target agreed with the utility.
Where
Portsmouth Water, Binsted Ford, 7–8 May 2026.
What it does not cover
Post-event analysis. In real time, four back-to-back flushes were captured as one event. One of the ten came in at 27%, outside target.
See all ten flush results
Security & compliance

Security built for
critical infrastructure.

Water supply is an essential entity under NIS2, and from 2026 that is enforced rather than discussed. Your suppliers are now part of your attack surface and your reporting duty, so a vendor's security posture stopped being a procurement formality.

Security & compliance in detail Request our certificate pack
ISO/IEC
27001:2022
Certified · information security management
Certificate K-0222779 · issued by Kiwa · certified since 2025
NIS2 QUALITY MARK
SC30
Independently audited · listed in a public registry you can check
Audited 18 March 2026 · valid to 18 March 2029
  • No hardware installed in your OT network
  • Read-only integration with SCADA and historian
  • Your data stays in your region
  • Supplier security questionnaire answered before you ask
Price, in public

€29,000 a year.
No call first.

Most vendors make you sit through two calls and a discovery workshop before they name a number. Essential is €29,000 a year, with 500 km of network included, and you did not have to ask for it.

Compare the three packages 3 packages · Essential €29,000 / year
Essential
Detection. Network visibility and daily leak insights: an alarm that a leak exists, once it has run for a day. It does not tell you where.
€29,000 / year
500 km of network included. Every kilometre above that is quoted with the network.
  • Continuous software updates
  • Daily leak detection
  • Unlimited users. We do not charge by the seat
  • Multilingual interface
  • Minimum night flow analysis
  • Integration with existing hydraulic models
  • Visualisation of sensor data
  • Export of leak events
  • Dashboards, analytics and reports
  • Access levels per person: full, read-only, or one area only
Professional
Localisation. Everything in Essential, and HULO tells you where: real time, to a search area a crew can walk.
On request
Quoted on your network, because what it costs depends on how much of it you run and on what you connect to it.
  • Everything in Essential
  • Real-time leak detection, localisation and leak volume estimation
  • Real-time leak prioritisation
  • Live pressure mapping
  • Live operational network view
  • Recommended operator actions
  • Sensor health monitoring
  • Security and compliance: ISO 27001, 2FA and NIS2
  • Unifying all data sources
Enterprise
Everything, plus the network itself. Simulation, sensor placement, model conversion and the integrations.
On request
Quoted the same way, on the network you actually operate.
  • Everything in Professional
  • Real-time what-if simulations
  • Sensor coverage blind spot indicator
  • Sensor placement optimisation
  • GIS-to-hydraulic model conversion
  • Anomaly detection and event triage
  • Fast-start onboarding: automated import of GIS, sensor, model, SCADA and network data
  • SDK for custom integrations
  • API integrations

No trenching, and no per-sensor licence. HULO reads the sensors you already own, which is why an entry package can carry a published price at all. Most utilities do add sensors once they see what each one buys them, and none of that is a licence cost here. The two above it are quoted rather than hidden: ask, and you get the figure, without a workshop first.

Build it, or buy it
Build it
A team, not a hire
Nobody builds this with one engineer. It is a data pipeline, a model, and the people to keep both running, and leak detection is the part that team gets to last. In Western Europe one of those engineers is on the order of €90,000 to €100,000 a year, all in. Where you are it may be a great deal less. That figure is an estimate, and yours is the one that counts.
Buy it
€29,000 / year, to start
Essential, on 500 km, at the same price wherever you are. The comparison worth making is not the euros, because salaries differ by country and ours do not. It is the shape: several people, indefinitely, against one line in a budget.
And the part that is not money
What you build is what you have. What you buy keeps arriving. Every network we read teaches the models something, and the improvement lands on your screen without a project to pay for it.
The clock runs differently. A team building this starts with the data pipeline, and detection is a long way down the plan. The first leak here is found in weeks.
Your engineers are worth more elsewhere. The people who could build it are the people who understand your network, and a utility has a queue of work only they can do.
Your rates are not ours, and the honest version of this sum uses yours: put your own salary line in and the comparison holds or it does not.
What one leak is worth
€6,700 / month
A single leak of 15 m³/h that nobody has found loses 360 m³ a day. At a production cost of €0.62/m³ that is €223 a day, or roughly €6,700 a month, from one leak. Your production cost and your leak sizes are not ours, which is why we run this on your data before you sign anything. Open Run it on your numbers below and see what a year of them comes to.
Run it on your numbers 6 sliders · your network

That is what it costs. This is what it is worth on your own network: your length, your teams, your leaks, your production cost. Nothing here is sent anywhere.

Your network, roughly:

Taking a team as covering 2 km a day over 200 working days, which is 400 km each a year. Change the numbers above to your own.

Today, five teams on the rota
1.0×

times you cover the whole network in a year. A leak that starts the day after a team leaves an area waits for the next pass.

And the backlog gets an end date
15 months

and the other teams have walked the whole network once, clearing the 20% that was already in the ground. It ends because the team on the alarms stops new leaks taking their place.

What the one team changes

How long a new leak runs, from the day it starts.

Waiting for the survey to arrive 183 days
Pre-located the day it starts 2 days

91× shorter, and it is the same crew doing it.

What one leak costs while it runs
A day
€214
A week
€1,500
A month
€6,500
Until the survey finds it
€39,000

One leak, at 4 l/s. That is 346 m³ a day into the ground, every day nobody knows it is there.

What the change is worth, in a year
€14.1 million

of water that never leaves the network, from moving one team and hiring nobody. That is 66,000 leak-days removed and 22.8 million m³ kept, if every one of those leaks ran at the rate you set. They will not: yours will be a spread, and the small ones run longest. Put your own average in and the shape of the answer holds.

Run the numbers on your network
Feasibility scan

Send us one week
of your data.

We run the scan on your own network, your SCADA export, your model, your zones. You get back a map of where your losses are and what HULO would have caught. No hardware. No commitment. If the answer is that you do not need us, we will say so, in writing.

Start a feasibility scan Watch a leak found first
01 You send one week of data. A standard SCADA export and your network model. Two hours of your engineer's time.
02 We run the scan. Ten working days. Nothing installed, nothing connected to production.
03 You decide. A loss map, the events we would have raised, and an honest read on what your data can support. No auto-renewal into a pilot.

Sign up for our newsletter

What we found, on which network, and what it cost to find it. Roughly monthly, and never a figure we cannot show you the working for.

Kiwa certified, ISO/IEC 27001 NIS2 Quality Mark, Supply Chain
ISO 27001 certified NIS2 SC30 audited See the evidence

Backed by our partners

  • LUMO Labs
  • NEW, Netherlands Enabling Watertechnology
  • Vanagon
  • VP Capital
  • FOM, Friese Ontwikkelings Maatschappij
  • Co-financed by the European Union

Part of the ecosystem

  • SWAN Asia-Pacific Alliance
  • Water Alliance
  • Isle
  • Partners for Water
  • NWP, Netherlands Water Partnership
  • Water Positive
  • BMW Foundation Herbert Quandt

HULO’s project Lekker (tegen lekken) is co-financed by the European Union, by SNN and by the Dutch Ministry of Economic Affairs.

Medegefinancierd door de Europese Unie SNN, Samenwerkingsverband Noord-Nederland Ministerie van Economische Zaken, the Dutch Ministry of Economic Affairs