Opinionated workflow
Upload a file, validate it, and let the queue handle concurrency. No hidden reruns—jobs read from stored binaries only.
About WaterMap
EPANET simulations without the busywork
WaterMap packages EPANET in a cloud workflow so you can upload network models, queue simulations, and pull the hydraulic reports you need—no local installs, no brittle scripts.
FastAPI + EPANET
What you upload
- Validated EPANET
.inpmodel - Queued job with per-user isolation
- Downloadable
report.rptandoutput.bin
Workers persist through restarts, so you never lose a run.
Why teams choose WaterMap
Purpose-built for water engineers who need trustworthy, repeatable EPANET results.
Secure by default
Every upload sits in a dedicated job directory, tied to your account when authenticated. Downloads require the same bearer token you used to submit.
Observable runs
Job states survive API restarts thanks to the MySQL-backed queue. Poll progress, reopen finished jobs, or re-download artifacts anytime.
How it works
Transparent stages so you always know what happens to your model.
-
Validate. POST your
.inpvia the UI or API to check parser errors before you spend compute. -
Simulate. Dedicated workers call the EPANET toolkit
(
ENsolveH,ENsolveQ, and more) inside isolated job folders. - Collect results. Download the zip, plain-text report, or binary output. When S3 is enabled, artifacts are mirrored for durability.
Get started
Ready to move EPANET to the cloud?
Upload a network, monitor the queue, and keep a durable record of every simulation you run with WaterMap.