Skip to content

epanet-js Blog

epanet-js July 2025 Progress Report

GIS Model Builds, New Languages, and More!

It’s been one month since we launched epanet-js, and the response from the community has been incredible. Sam and I have been blown away by the feedback and are thrilled that over 3,000 of you from all around the world have already used the tool.

Image title
GIS model builds are now in epanet-js!

Introducing epanet-js

Fast, local-first water modeling right in your browser

For decades, the U.S. EPA’s EPANET engine has powered almost every hydraulic modeling tool on the market. Yet most of us still wrestle with either the “classic” Windows interface — slow, dated, and held together by workarounds. Meanwhile, commercial platforms cost a fortune, lock up our data, and bury us in features we don’t need.

You deserve better.

The epanet-js interface in action

How to Compile the EPANET GUI

EPANET GUI Demo

EPANET is a widely used hydraulic and water quality modeling software that is capable of simulating water distribution systems. While the software can be run using the provided executable file, some users may want to compile the GUI themselves to make customizations or improvements. This article will walk you through the steps of compiling the Graphical User Interface (GUI) for EPANET using Delphi Community Edition.

epanet-js - the water distribution modelling engine for the web!

EPANET is a powerful hydraulic analysis software that is widely used in the water distribution industry. It allows users to model and analyze the behavior of water distribution systems, including the flow of water through pipes, the pressure at various points in the system, and water quality behaviour within the network.

EPANET has been an invaluable tool for engineers and water utilities for many years, but until recently, the programmers toolkit which allowed you to develop on top of it was only avaiable in languages focused on desktop development or scientific research. This meant that users had to install the software on their local machines in order to use it, and it was not possible to access the toolkit from a web browser.