Continuous & event simulation
Run a single design storm or decades of recorded weather. One model, two horizons.
Computational hydrology platform
Where every drop accounts for itself.
StormwaterIQ runs your entire stormwater program in one place — inspections, records, and permits, plus the hydrology underneath them, from the first drop to the final outfall. Not another inspection binder in the cloud, and not a second tool bolted onto the one you have.
Everyone else stops at the binder. That's where we start.
01 — The gap
One job. Paid for in pieces.
A stormwater program isn't just paperwork, and it isn't just engineering — it's both, end to end. The tools you've been sold cover only the first half. The other half lives in another building, on another invoice, disconnected from the sites it describes.
// The record
What happened
- SWPPP & document storage
- Inspections & corrective actions
- Permit lockers & annual reports
Useful, and entirely necessary — but it's the record of the program, not the program.
no shared data
// The engineering
What it means
- Runoff & watershed delineation
- Flow routing & pollutant loads
- Permit judgment & design
A separate model, a spreadsheet, a six-week round-trip — billed and stored apart from the sites they describe.
So a single program ends up split across two stacks: one to remember what happened, another to figure out what it means. StormwaterIQ is one stack for the whole job.
02 — The difference
Same record. Plus everything it never told you.
Every record-only platform stops at the paperwork — and to learn what the water is actually doing, you leave it. StormwaterIQ holds the same record layer and keeps going, in one continuous system.
Record-only platforms
Stops at the record
Store documents. Route inspections. Send reminders. Generate reports from what your team already typed in. Everything they hold, you put there. The watershed is a map pin — and when you need to know what the water is doing, you leave the platform.
StormwaterIQ
Runs the whole program
Does all of that — SWPPP, inspections, permits, annual reports, the full record layer — and is built to keep going: model runoff, delineate watersheds from terrain, read inspection photos for deficiencies, verify permits, and turn it into pollutant loads, risk, and regulator-ready deliverables. The record becomes an output of the model, not a separate chore.
The whole program — record and computation — in one system, instead of scattering half of it across a modeling tool, a spreadsheet, and a six-week round-trip.
03 — One platform, not four line items
You're already paying for all of this. Separately.
StormwaterIQ isn't another subscription on top of your stack. It's the subscription that's meant to retire most of it.
What you pay for todayWhere it lives nowIn StormwaterIQ
Inspection & record-keepingA dedicated compliance platformFull inspection workflow, offline field capture, audit trail
Hydrologic & hydraulic modelingDesktop modeling software + spreadsheetsRunoff, watershed delineation, flow routing
Permit tracking & annual reportsManual, or a separate moduleAutomated verification and report generation
Engineering analysisManual setup, study by studyFaster — automation handles the prep, engineers handle the judgment
A stack of disconnected tools becomes one platform — and the analysis that once took weeks of setup takes hours, because the record and the engineering were never meant to live apart.
04 — The method
From the first drop to the final outfall.
We don't invent hydrology. We automate the parts that have always been a slog. Everything we compute is built on the same methods a stamping engineer pulls from a drainage manual — so the output is designed to survive engineering review, not just an audit.
See the methodology ↗
Rational MethodSCS / NRCS Curve NumberTR-55NOAA Atlas 14Manning's equation
05 — Use cases
Built for the work that arrives with the storm.
Whether you're planning a thirty-year capital program or filing next quarter's report, the underlying model stays the same. Only the question changes.
06 — Features
A toolkit calibrated to field reality.
Built alongside utility engineers and floodplain administrators — not abstracted away from their problems. See all features ↗
Automated watershed delineation
Drainage basins and flow paths derived from terrain — not hand-drawn.
Photo-aware inspections
Field photos read for deficiencies on the spot, so problems get flagged before they leave the site.
Automated permit verification
Coverage, deadlines, and obligations checked against the governing rules, nationwide.
Pollutant load & receiving-water context
Loads disaggregated by pollutant and attributed to the right downstream water and its impairment status.
Methodology on every number
Each computed output carries its method, inputs, and the governing citation — so it stands up when someone asks how you got it.
07 — Frequently asked
Questions worth answering directly.
If something here doesn't answer your question, get in touch. We prefer conversations to forms.
What exactly does StormwaterIQ do?
It's a computational hydrology platform. You bring your service area — terrain, infrastructure, land cover — and we build a continuously running model of how water behaves in it. From there, the same model is designed to answer questions about flooding, water quality, capital planning, climate scenarios, and compliance.
How is this different from the inspection software we already use?
The inspection software you have covers the record — documents, inspections, reports — and stops there. StormwaterIQ covers that same record layer and adds the half that currently lives outside it: runoff, watershed boundaries, pollutant loads, permit obligations. So it's not a second tool to run alongside your current one — it's meant to replace it, and the modeling work you do separately, with a single system.
Is this a replacement or an add-on?
A replacement. The record layer — SWPPP, inspections, permits, annual reports — is built in, not assumed to live elsewhere. The goal is one platform for the whole program, not one more invoice on top of the tools you have.
Do we need a fully built-out GIS to get started?
No. Most programs arrive with a partial dataset — pipes here, parcels there, elevation from the state. The platform stitches those against public elevation, soils, and land cover sources.
Will the numbers hold up in front of a regulator or a stamping engineer?
That's the design constraint. Established public-domain methods, transparent inputs, and a citation on every calculation — so a determination isn't a black box. The platform doesn't replace the engineer's judgment; it's built to give that judgment defensible numbers to stand on.