Two cities get the same two inches of rain. One spends the afternoon fighting flash floods, sending a brown torrent down its storm drains and out to sea, and is measurably hotter by evening. The other lets much of it sink into the ground, eases the load on its drains, and stays cool. Same storm. Opposite outcomes. The only difference is what the ground is made of.
Most cities are built to get rid of water as fast as possible. A sponge city is built to drink it. And the shift between the two is one of the highest-return moves in urban infrastructure — because it fixes flooding, heat, and water supply in a single stroke.
A sponge city is an urban area designed to absorb, store, and reuse rainfall where it lands — using permeable pavement, rain gardens, bioswales, green roofs, restored urban wetlands, and depaving — instead of channeling every drop into pipes and out of town. The goal is to let the city work like a healthy landscape: catch the rain, sink it in, and release it slowly.
If you're new to why that matters, start with the pillar: the water cycle, broken and how to put it back.
the design flaw: cities are built to shed water
Pavement is the problem hiding in plain sight. Roofs, roads, and parking lots are impervious — water can't pass through them — so rain that would soak into open ground instead sheets off, picks up speed and pollution, overwhelms storm drains, and floods the low spots. Almost none of it recharges the groundwater below.
The contrast is stark. On natural ground, roughly half of a rainfall soaks in and only about a tenth runs off. In highly developed areas — 75–100% covered by impervious surfaces — the numbers flip: more than half runs off and only about 15% infiltrates (U.S. EPA). A single inch of rain on one acre is about 27,000 gallons — much of which a healthy landscape soaks in and reuses, and a paved one flushes to the nearest drain as a flash flood.
So a paved city manufactures both of its own water problems at once: too much water in the wrong place during a storm, and too little in the ground the rest of the year. Then it pays, twice, to manage each separately — bigger storm drains for the flood, imported supply for the shortage.
the sponge-city toolkit
Turning a city into a sponge doesn't mean tearing it down. It means changing surfaces and low spots, piece by piece, so water has somewhere to go but the drain:
- depaving — pulling up pavement that no longer needs to be there and returning it to soil and plants
- permeable pavement — surfaces you can still drive and walk on that let water pass through into the ground below
- rain gardens and bioswales — planted low areas that catch street and roof runoff and let it soak in
- green roofs — roofs that hold and slow rainfall instead of dumping it
- urban wetlands and daylighted streams — bringing buried creeks back to the surface to store and clean water
- street trees — canopy that intercepts rain, cools the air, and breathes water back out
None of it is speculative. It's the same "slow it, spread it, sink it" logic that restores any landscape — applied between the buildings. Cities from Wuhan to Rotterdam to Philadelphia are already building this way, at very different scales.
depaving refills the aquifer — where the ground allows
Here's the move that ties the city back to the water cycle: every square foot of pavement you remove is a square foot where rain can sink in instead of becoming runoff — and where soils and the water table allow, some of that infiltration recharges the groundwater below. In many places that aquifer is dropping (the problem behind why your well is running dry), so turning parts of the city into a recharge zone matters.
How much actually reaches the aquifer depends on local geology: clay, shallow bedrock, or a high or already-contaminated water table all limit it. And urban runoff carries road salt, hydrocarbons, and metals, so infiltration usually needs vegetated pretreatment first — which is exactly what rain gardens and bioswales provide. Where deep recharge isn't viable, the same surfaces still earn their keep on flooding and heat. The city's water cycle doesn't have to be perfect to be worth repairing.
A sponge city treats stormwater not as waste to flush away but as the cheapest water it will ever get — free, delivered from the sky, and rejected only because the ground was sealed shut.
one move, three wins
This is where the economics get interesting. A conventional city buys flood control, cooling, and water supply as three separate, expensive programs. A sponge retrofit delivers all three from the same square foot:
| the problem | the gray fix (one purpose) | the sponge fix (three at once) |
|---|---|---|
| flooding | bigger pipes and detention tanks | rain soaks in where it falls |
| urban heat | more air conditioning | wet ground and canopy cool by evaporation |
| water supply | imported or deeper-pumped water | recharged local groundwater |
The flood buffering is obvious after the first storm. The cooling is real physics — wet, planted ground runs far cooler than baking asphalt, which is why sponge design is also heat-island mitigation (how to cool a city block). And the recharge quietly rebuilds the supply. It's the one repair, many payoffs cascade, rebuilt inside the city.
why it's still underbuilt
If sponge infrastructure pays off three ways, why isn't every city doing it? Because stormwater is the least-funded corner of urban water. Drinking water and sewage have rate bases and decades of financing behind them; stormwater is often an afterthought, funded by scraps and one-off grants — even as the storms get bigger. That gap is also the opportunity: the returns are large precisely because the work is so far behind. It's the same logic laid out in nature-based solutions for urban flooding and MS4 compliance through green infrastructure.
how a city funds the sponge
The catch is timing and coordination: the buildout costs money now, the payoff shows up over decades, and the beneficiaries — the flooded neighborhood, the utility, the campus, the businesses that lose days to heat and water — are scattered.
Ensurance is built for exactly that. It prices the full stack of returns from sponge infrastructure — flood reduction, cooling, recharge — using a natural-capital accounting method, and lets the beneficiaries fund the buildout upfront. What they hold in return is concrete: a certificate tied to a specific restored site, or a coin that funds sponge and watershed work broadly — a priced claim on the natural asset and its returns, with proceeds routed to whoever does the work.
That's a different instrument from the usual three. A green bond is debt the city has to repay; a stormwater fee is a charge on ratepayers; an environmental impact bond is pay-for-success debt — all liabilities on someone's books. An ensurance certificate is an asset the beneficiaries hold, tied to the natural capital itself. A city treating its rivers and streets like infrastructure is exactly the shift the city that treats its rivers like infrastructure describes.
picture it in fifteen years
Walk the same downtown after a decade of this. The summer cloudburst that used to close the underpass now disappears into a chain of rain gardens. The July afternoon that used to hit 105°F on the asphalt sits several degrees cooler under canopy and over damp ground. Where the ground allows, the wells and springs the city half-forgot are steadier, because the streets have been quietly recharging them the whole time. None of it looks like heavy infrastructure. That's the point — the infrastructure is the city itself, finally allowed to drink.
where to start
- cities, counties, and utilities — the beneficiaries of a drier, cooler city are scattered across departments and budgets; the first move is to price the sponge retrofit as one asset and convene who pays. Talk to someone who can help →
- infrastructure investors and corporations — sponge capacity is real, improving infrastructure that markets have barely priced. See how the funding works →
- onchain participants — general ensurance coins fund this kind of restoration across many places at once.
frequently asked questions
what is a sponge city?
A sponge city is an urban area designed to absorb and store rainfall where it falls — through permeable pavement, rain gardens, bioswales, green roofs, urban wetlands, and depaving — instead of piping it all away. It reduces flooding, cools the city, and recharges groundwater by letting the built environment behave more like a natural, absorbent landscape. The term was popularized by China's national Sponge City program launched in 2013.
how does depaving help with flooding and water supply?
Pavement forces rain to run off instead of soaking in, which causes flash flooding and starves the aquifer. Removing pavement (or replacing it with permeable surfaces) lets rain infiltrate where it lands — cutting the runoff that floods streets and recharging the groundwater that feeds local supply. The same square foot solves both problems at once.
does sponge-city infrastructure actually reduce urban heat?
Yes. Paved surfaces absorb and radiate heat, driving the urban heat-island effect; wet soil, vegetation, and tree canopy cool the air through evaporation and shade. Because sponge design adds exactly those wet, planted surfaces, it lowers local temperatures as a co-benefit of managing stormwater.
how do cities pay for sponge infrastructure?
Traditionally through stormwater fees and grants, which is why it's chronically underfunded. The alternative is to price the full stack of returns — flood reduction, cooling, and groundwater recharge — and fund the buildout upfront as an infrastructure investment beneficiaries hold, rather than a cost. That upfront-and-held model is the approach behind ensurance.