HydroCouple ↔ SWMM · 2026 Architecture Explorer

What the HydroCouple ecosystem is now — 45 repositories, interface spec 2.0.0-alpha.1, Open-Source SWMM 6.0.0-alpha.3, a Qt6 GUI, an MCP server and a 1,396-model benchmark platform — set against EPA SWMM 5.2.4. Updated 31 Aug 2026 from the live GitHub org and hydrocouple.org source.
Start hereThe April 2026 version of this app described a 36-repo org whose activity sat in a 2019 thread-safe SWMM fork. Four months later the org has a different centre of gravity. This tab is the delta; the other tabs are the detail.

What changed since April 2026

THEN → NOW
Repositioning. hydrocouple.org now leads with “Digital public water infrastructure, built in the open and ready for AI.” HydroCouple describes itself as the enabling architecture — open interface definitions, data standards, computational engines — and names Open-Source SWMM 6.0 (SWMM2D) as its flagship engine. The framing has moved from “a coupling framework that wraps SWMM” to “a SWMM initiative with a coupling standard under it.”
What this means for a SWMM5 modeller. The engine you would couple today is not the 2019 SWMMComponent wrapper around a thread-safe C fork. It is openswmm.engine: a C++20 rewrite with a reentrant handle API, a PyPI package, a Qt6 GUI, an MCP server for agents and Gymnasium environments for control. The EPA C tree is still there — preserved in src/legacy as a separate build target for side-by-side comparison.

The openswmm.* and openepanet.* family (none of it existed in April)