epanet-js is designed to give you maximum control and privacy over your project files. Unlike many web applications that automatically save your data to the cloud, epanet-js uses a local-first approach. This means your water network models are saved directly onto your own computer, similar to how traditional desktop software operates.

How local-first saving works in epanet-js

  1. Initial Save:

    When you first save a new project (by clicking Save or Save As in the toolbar), epanet-js will prompt your browser to open a standard "save" dialog. You choose a name and a location on your computer to store the project as an .inp file. This is the same process you're likely familiar with from other desktop applications.

  2. Subsequent Saves:

    Once you have saved your file to a location on your computer, epanet-js establishes a reference to that specific file. When you click Save again, epanet-js directly updates that original file on your local hard drive. You won't be asked to choose a location each time unless you use Save As.

  3. Unsaved Changes:

    The application provides indicators if you have unsaved changes. If you attempt to close the browser tab or navigate away from epanet-js with unsaved work, you will receive a warning prompt from your browser, giving you a chance to save.

    image.png

Key benefits of a local-first approach

Optional cloud storage (Future)

While local-first is the default, we plan to offer optional cloud storage and synchronization features in the future. This will be for users who want the convenience of accessing their files from multiple devices or for enhanced collaboration. However, using cloud storage will always be your choice, and the ability to work entirely locally will remain a core part of epanet-js.

The local-first approach in epanet-js ensures that you are in charge of your data, offering a secure, private, and familiar way to manage your hydraulic modeling projects directly from your web browser.