Skip to content

Local-first, offline and your data

Network data is often confidential. This page explains, concretely, where your models go.

The SWMM engine executes in your browser tab, on your own CPU. When you press Simulate, your model is not uploaded to a server to be solved. There is no queue, no compute cost, and no copy of your network sitting in someone else’s job runner.

This has a practical consequence worth knowing: simulation speed depends on your machine, not on a plan tier. A large dynamic-wave model will take as long as your laptop takes.

Project ▸ Export SWMM model (.inp) writes a standard SWMM .inp file to your own disk. It is the same format the EPA desktop program reads, so you can open it in EPA SWMM, PCSWMM or InfoSWMM tomorrow. There is no proprietary container and no conversion step to get your work out, and exporting never asks you to sign in.

Signing in adds cloud sync, project sharing and the operational features that genuinely need a server - scheduled forecast runs, alerting. All of it is optional. Without an account you can still build, run, save, and open models.

Once the application has loaded, it keeps working with no connection:

  • The engine is already on your machine, so simulations still run.
  • Your open model is in the browser, so editing still works.
  • Saving to your own disk still works.

What needs a connection: map tiles for the basemap, generating a model from a location (it fetches street and terrain data), weather forecasts, and cloud sync.

To be precise about what leaves your machine:

ActionLeaves your machine?
Running a simulationNo
Editing, saving to diskNo
Basemap tiles, terrain, street dataYes - map and geodata providers
Cloud sync / sharing (optional, signed in)Yes - to our database
Weather forecast, CSO alerting (optional)Yes
AI Copilot (optional, your own key)Yes - to the provider whose key you supply

For the full picture, including hosting regions and security practices, see the security and deployment page.