epanet-js vs. Autodesk InfoWorks WS Pro

A fast, browser-based modeling workspace built on EPANET 2.3. Open InfoWorks WS Pro models directly, eliminate database administration bottlenecks, and give your broader team direct access to the model.

Why consider epanet-js alongside InfoWorks WS Pro?

InfoWorks WS Pro is built for large-scale enterprise water modeling. Its centralized workgroup data server, version control branching, and specialized solver make it a powerful platform for large utilities maintaining unified master models across dedicated modeling departments.

However, that enterprise database architecture carries significant operational friction. The multi-step checkout, commit, and validation process—combined with a steep learning curve—makes everyday tasks like testing a valve shutdown, evaluating a development connection, or checking fire flow needlessly slow. As a result, routine modeling requests frequently bottleneck behind the few staff members trained to manage the master database.

epanet-js provides a fast, accessible workspace for everyday distribution modeling. It runs local-first in any modern web browser, imports native InfoWorks WS Pro files directly, and lets engineers build, edit, and simulate networks without checking out database locks or configuring complex workgroup servers. You get immediate simulation feedback on standard EPANET 2.3 hydraulics at a fraction of the licensing cost.

Side-by-side comparison

A practical breakdown of software architecture, hydraulic engines, and licensing costs.

Feature and pricing comparison between epanet-js and Autodesk InfoWorks WS Pro
Category epanet-js InfoWorks WS Pro
Platform & OS Cross-platform (Browser) Mac, Windows, Linux Windows desktop only workstation installation
Collaboration & storage Local-first files opt-in cloud workspaces or on-prem Workgroup database server cloud or on-prem master DB
Hydraulic engine Standard EPANET 2.3 official Toolkit 2.3.5 Proprietary Wallingford / Innovyze lineage
Native project format Open .ejsdb / .inp transparent, portable file format Proprietary database commit-based master container
Opens InfoWorks WS Pro models Direct import retains custom asset attributes Native
Standard EPANET .inp support Native open & export Import & export subject to translation rules
Extended period simulation (EPS)
Water quality analysis
Scenario management
GIS import formats Shapefile, GeoJSON, CAD Shapefile, MapInfo, CSV, ODBC Geodatabase requires licensed ArcGIS
Free access tier Full simulation engine no network size limits Read-only viewer no simulation or editing
Open-source codebase
Starting cost Free tier Pro from $950/yr ~$10,000/seat/yr or $1,250/month

Core advantages of epanet-js

Direct InfoWorks WS Pro import

Open InfoWorks WS Pro models directly with custom asset attributes preserved. You can review layouts, test operational options, and inspect results without setting up an export project.

Open, portable model files

Your model is a standalone file on your machine—not trapped inside a proprietary database. Work natively with EPANET .inp and open formats that any tool in the water industry can read.

Accessible team-wide pricing

The free tier includes the complete EPANET 2.3 engine with no node or pipe caps. Pro is $950 per year—letting you roll out modeling beyond a single specialist.

Interoperability without vendor lock-in

Adopting epanet-js doesn't require dismantling your established master model workflow. You can import your InfoWorks WS Pro model directly, bringing over network geometry, boundary conditions, and custom asset attributes into a lightweight workspace. Because the free plan has no model size caps, you can verify your actual network performance immediately.

Moving data back is equally practical. epanet-js exports standard EPANET files that InfoWorks WS Pro reads through its standard import tools—including support for importing files directly as scenarios in modern WS Pro releases. You can perform rapid design iterations and operational checks in epanet-js, then merge approved modifications back into your enterprise model when required.

Frequently asked questions

Frequently asked questions about moving between epanet-js and InfoWorks WS Pro.

Is epanet-js a viable alternative to InfoWorks WS Pro?
For day-to-day distribution modeling, scenario evaluation, and operational checks, yes. While WS Pro is tailored for managing massive enterprise master models via centralized database servers, epanet-js provides a faster, lighter environment for routine engineering tasks using the EPANET 2.3 engine. Because models move between both tools, utilities often keep WS Pro for enterprise master planning while using epanet-js for team-wide design reviews and scenario runs.
Can epanet-js open InfoWorks WS Pro models directly?
Yes. epanet-js reads InfoWorks WS Pro network files directly, extracting network geometry, pipe properties, boundary heads, and custom attributes without requiring an intermediate export step.
Can I move a model from epanet-js back into InfoWorks WS Pro?
Yes. epanet-js exports standard EPANET .inp files that InfoWorks WS Pro imports directly. Since WS Pro 2025.1, multiple .inp files can also be imported directly into a single network as distinct scenarios. We provide step-by-step guides to ensure clean round-trip handoffs.
How much does InfoWorks WS Pro cost?
Autodesk lists InfoWorks WS Pro at approximately $10,000 per user per year (or $1,250 per month). epanet-js provides a fully functional free tier with no model size caps, and paid Pro plans start at $950 per year.
How do the simulation engines compare?
WS Pro runs Autodesk's proprietary solver derived from the Wallingford lineage, while epanet-js runs the standard EPANET 2.3 engine. Both solve fundamental hydraulic mass balance and energy equations reliably. Minor numerical variations can occur due to differing default friction formulations, convergence tolerances, and unit conversions under extreme flow regimes. Additionally, highly specialized elements (such as proprietary complex valve arrays) unique to WS Pro are translated into equivalent standard EPANET control assemblies.
Do I need a server to collaborate in epanet-js?
No. WS Pro relies on a centralized workgroup database server to manage concurrent edits. epanet-js is local-first by default: projects run and save on each modeler's machine. For team collaboration, the Ultimate plan offers optional cloud workspace sharing with role management and regional data storage, while Enterprise plans support self-hosted, on-premises deployments.

Compare with other modeling tools

Test your InfoWorks model in epanet-js

Import an existing WS Pro network and experience a fast, responsive modeling environment—free, local-first, and without database overhead.