Choose the plan that works for you
Individual named license
Base cost
User
Have questions? Send us an email or book a call.
Everything that's included in each plan.
| Feature | |||
|---|---|---|---|
| Platform | |||
| Web-based — no install, any OS/browser | |||
| Local-first — data stays on your machine | |||
| Works offline after first load | |||
| No limits on model size | |||
| No account required to start | |||
| Multi-language interface | |||
| Simulation engine | |||
| EPANET Toolkit 2.3.5 engine | |||
| Steady-state and Extended Period Simulation (EPS) | |||
| Pressure-Dependent Demands (PDD) | |||
| Simple and rule-based controls | |||
| Water quality analysis (age, trace, chemical) | |||
| Energy consumption analysis | |||
| Headloss formulas (H-W, D-W, C-M) | |||
| Simulation time and options | |||
| Input data pre-check | Coming soon | Coming soon | |
| Network editing | |||
| Asset drawing in the map | |||
| Snap-to-node and pipe splitting | |||
| Node merging and replacement | |||
| Redraw and reverse links | |||
| Pipe drawing defaults | |||
| Active topology – deactivate / reactivate assets | |||
| Batch attribute editing | |||
| Asset search | |||
| Zone polygons – import and visualize | |||
| Element properties | |||
| Pump definitions and curves (1 / 3 / multi-point) | |||
| Tank capacity (diameter or volume curve) | |||
| Pump controls (level or time-based) | |||
| Pipe material and installation year | |||
| Custom data fields | |||
| Demand management | |||
| Customer points | |||
| Add, edit, move, remove customer points | |||
| Import from Shapefile or GeoJSON | |||
| Customer points data table | |||
| Allocation | |||
| Demand allocation | |||
| Rules-based allocation | |||
| Allocate per zone | |||
| Data libraries | |||
| Curve library manager | |||
| Patterns library (time-series patterns) | |||
| Pipe definition library | |||
| Assign roughness by material and age | |||
| Saved selection sets | Coming soon | Coming soon | |
| Data exchange | |||
| INP import and export | |||
| epanet-js project format (.ejsdb) | |||
| Custom coordinate systems and projections | |||
| Simple X-Y grid (non-georeferenced models) | |||
| Third-party model import and export | Coming soon | Coming soon | |
| Elevation data | |||
| Automated elevations (Mapbox Terrain DTM) | |||
| Custom elevation source (GeoTIFF) | |||
| Model building | |||
| GIS model import — legacy builder | |||
| GIS model import — Pro builder | |||
| Source projection preserved | |||
| Attribute search in field mapping | |||
| Model build in your language | |||
| Results & visualization | |||
| Map & layers | |||
| Map visualization | |||
| Basemap selection (satellite, streets, outdoors) | |||
| Custom tile server (XYZ, Mapbox, TileJSON) | |||
| Custom vector file layers (GeoJSON, Shapefile) | |||
| Local background layers | Coming soon | Coming soon | |
| Symbology | |||
| Map symbology (pressure, flow, demand, head, …) | |||
| Flow direction arrows | |||
| Node size and visibility settings | |||
| Charts & tables | |||
| Quick graph in the asset panel | |||
| Custom graphs with multiple elements | |||
| Graphing time-series data | |||
| Asset data tables | |||
| Hydraulic Grade Line (HGL) profile | |||
| Advanced analysis & operations | |||
| Network review (checks) | |||
| Orphan assets | |||
| Asset proximity | |||
| Crossing pipes | |||
| Connectivity trace | |||
| Missing or invalid attribute checks | |||
| Pipe roughness check | |||
| Tank levels check | |||
| Pump curves check | |||
| Unallocated customer points | |||
| Tracing | |||
| Boundary and selection trace | |||
| Upstream and downstream trace | |||
| Criticality | |||
| Valve criticality analysis | Coming soon | Coming soon | |
| Scenario management | |||
| Create and switch scenarios | |||
| Compare scenario differences (changed attributes highlighted) | |||
| Compare simulation results between scenarios | |||
| Scenarios, versioning and model history | Coming soon | Coming soon | |
| Save scenarios in model / cloud | Coming soon | Coming soon | |
| Reporting & exports | |||
| Export asset data (Shapefile, CSV, XLSX, GeoJSON) | |||
| Export simulation results (CSV, XLSX) | |||
| Cloud & collaboration | |||
| Multiple team members | |||
| Organization management | |||
| Guest user access and privacy settings | Coming soon | ||
| Cloud storage | Coming soon | Coming soon | |
| Team storage | Coming soon | ||
| Point-in-time restore (30 days Pro / 90 days Teams) | Coming soon | Coming soon | |
| Sharing models | Coming soon | ||
| Support & licensing | |||
| Community support | |||
| Professional support | |||
| Priority support | |||
| Self-service seat management | |||
| Pay by invoice | |||
| Individual named license | |||
| Feature | |||
Available for non-commercial projects, learning, and student work.
Try it out yourself.
Free for students and teachers.
Find answers to common questions about epanet-js
We work directly with Enterprise customers to complete vendor onboarding paperwork and support custom Purchase Order (PO) workflows.
Our Pro plan is designed to be completely self-service. By eliminating the administrative overhead associated with traditional, sales-driven procurement, we are able to pass those savings directly to you through lower subscription pricing. For Teams plans, we can assist with vendor forms and PO requirements depending on a minimum commitment of seats or contract years.
If you want to check your plan's eligibility or need standard company billing details to help fill out your internal forms quickly, email us or book a call.
epanet-js is a modern, web-based water network modeling tool based on the EPANET engine. It allows you to build, simulate, and analyze water distribution networks directly in your browser without installing any software.
Yes! epanet-js uses a local-first approach, meaning your project data is saved directly to your computer, not to our servers. This ensures your sensitive network data remains private and under your control. Learn more about the Local-First Approach.
No, you can start using epanet-js immediately without creating an account or logging in. Simply visit our website and launch the application to begin modeling.
Yes, epanet-js supports importing .inp files from desktop EPANET. You can seamlessly transition your existing projects to our web-based platform.
Yes! epanet-js works on all modern browsers including Chrome, Firefox, Safari, and Edge. Since it runs in a web browser, epanet-js works great on macOS, Windows, and Linux. This makes it a great option if you've had trouble installing traditional EPANET on a Mac. For the best experience, we recommend using the latest version of your preferred browser.
Yes, our source code is public from day one, but there's a two-year delay from the time we release a new version to when it becomes fully open source. This is how we drive sustainable open-source development for epanet-js, and, by extension, EPANET. You can learn more about why we're doing this and how the FSL license works here.
We offer different support options depending on your plan. Free users can access our community forums and documentation, while paid users receive priority email support. Educational users have access to specialized resources for classroom use.
We complete security questionnaires for our Enterprise customers.
Free, Pro, and Teams plans are self-service, and we expect your team to run its own internal security review. To make that as easy as possible, review our generic security questionnaire, with answers to the questions utilities and engineering firms have put to us before, so you can fill out your own internal forms quickly. If a question isn't covered, email us or book a call.
For a full overview of how we handle security and data privacy, see our security page.
epanet-js is built local-first. The browser acts as a secure runtime, much like a desktop operating system: when you load the app over HTTPS, the entire application, including the EPANET simulation engine compiled to WebAssembly, downloads to your browser cache and runs on your machine's own CPU and memory inside the browser sandbox, at near-native desktop performance.
Project files are read from and written to your hard drive or network drive through the browser's local file access APIs, and simulation results are saved locally. Neither your infrastructure data nor your customer data leaves your computer. It also saves bandwidth, since heavy model files are never streamed, uploaded, or downloaded. Once the page has loaded, you can disconnect from the internet entirely and keep working.
For a full overview of how we handle security and data privacy, see our security page.