Heat Sink
Your electricity bill is drinking the river. We show you how much comes back hot.
Channel: Heat Sink
Tagline: Your electricity bill is drinking the river. We show you how much comes back hot.
Niche: Consumer-facing power plant water-use and thermal-pollution intelligence — an automated, opinionated site that turns EIA plant operations data, cooling-system filings, EPA discharge violations, drought maps, and weather stress into plant-by-plant water scorecards, river-risk maps, utility report cards, and brutally clear weekly dispatches about which power plants are sucking down freshwater, which ones are heating local waterways, and where grid growth is colliding with water scarcity.
Target audience: Water-stressed communities near big power plants, anglers and river users, environmental journalists, energy nerds, climate-concerned homeowners, utility watchdogs, local activists, policy staff, and normal people who have never once been told that the grid has a water footprint. Also: investors and infrastructure nerds trying to understand what heat waves and drought actually do to generation risk.
Why now: USGS still classifies thermoelectric generation as one of the largest water users in the United States. Global electricity demand is projected by the IEA to grow an average of 3.4% annually through 2026, while electricity use from data centres, AI, and crypto could exceed 1,000 TWh by 2026. Translation: more power demand, more cooling stress, more fights over rivers, reservoirs, and discharge temperatures. Meanwhile, the EIA is already publishing plant-level operations data and bulk filings containing cooling-system and water-use details, but nobody is translating the spreadsheets into consumer-grade accountability journalism.
Content Example:
The Tennessee River Is Cooling Your Lights — And Paying For It
The TVA didn’t send your air conditioner a thank-you note, but the river got the bill.
At Barry, Browns Ferry, and dozens of other large thermoelectric plants across the U.S., electricity does not just burn fuel or split atoms. It also borrows a shocking amount of water to keep turbines and condensers from cooking themselves. The public usually hears about megawatts. The fish get introduced to the other side of the story: withdrawal volumes, warmer discharge, and lower dissolved oxygen when summer heat is already pushing the river to its limits.
This week’s filings show the usual ugly pattern. The grid looks clean and abstract from your phone charger. On the ground, it looks like intake pipes, warm outflows, and a utility trying to make physics someone else’s problem. Once-through cooling can move staggering quantities of water in exchange for cheap thermal management. Recirculating systems withdraw less but consume more through evaporation. Dry cooling saves water but costs efficiency. None of that is visible on your power bill. Heat Sink makes it visible.
When a county enters drought and a nearby plant still ranks in the top decile for water intensity, that is not just an engineering detail. That is a local resilience story. It affects fishing, municipal supplies, permitting fights, insurance assumptions, and whether the next heat wave becomes a reliability problem. The point of this channel is not to make people afraid of electricity. It is to stop pretending electricity arrives without a hydrology tab.
Data Sources:
- EIA API v2 – Electric Power Operations for Individual Power Plants —
https://api.eia.gov/v2/electricity/facility-fuel/— per-plant monthly and annual generation/fuel data; good for ranking plants, estimating intensity, and tracking operational shifts. - EIA API v2 – Operating Generator Capacity —
https://api.eia.gov/v2/electricity/operating-generator-capacity/— plant/generator coordinates, technology, capacity, retirement and uprate plans. - EIA-860 bulk files —
https://www.eia.gov/electricity/data/eia860/— cooling-system characteristics, water source, plant configuration. - EIA-923 bulk files —
https://www.eia.gov/electricity/data/eia923/— operational data and water-use/cooling detail by plant. - EPA ECHO / NPDES compliance data —
https://echo.epa.gov/tools/web-services— discharge permits, effluent and enforcement history, including facilities with thermal-discharge issues. - USGS thermoelectric water-use pages + national water-use datasets —
https://www.usgs.gov/water-science-school/science/thermoelectric-power-water-use— context, state/county water-use baselines. - U.S. Drought Monitor —
https://droughtmonitor.unl.edu/— weekly drought overlays for plant stress maps. - Open-Meteo / NOAA climate data — weather anomalies, heat-wave context, river/air-temperature stress framing.
- Hydrography layers (USGS/NHD/OpenStreetMap) — to map rivers, reservoirs, and downstream communities.
Automation Pipeline:
- Schedule:
- Daily GitHub Action for weather/drought overlays and new EPA compliance events
- Weekly GitHub Action for full story generation and scorecard refresh
- Monthly deep rebuild when EIA monthly plant files update
- Collect:
- Pull plant operations from EIA API
- Ingest fresh EIA bulk files for cooling-system and water-use detail
- Pull EPA ECHO permit/enforcement updates
- Pull drought layers, temperature anomalies, and hydrology context
- Geocode/join plants to watersheds, counties, utilities, and nearby population centers
- Process:
- Standardize plant identities across EIA/EPA datasets
- Compute gallons-per-MWh, withdrawal-vs-consumption profiles, and “river stress” indices
- Detect outliers: high-water plants in drought zones, repeat permit violators, plants with poor cooling profiles in hotter climates
- Generate local narratives with structured prompts: what changed, why it matters, who is affected, and what physics is doing behind the scenes
- Generate:
- Plant report cards
- Utility leaderboards
- Basin maps showing clustered thermal-pressure risk
- Explain-it-like-I’m-not-an-engineer diagrams of once-through vs recirculating vs dry cooling
- AI-assisted hero art for feature stories: glowing condensers, evaporative towers, river cross-sections, utility “mugshot” cards
- Publish:
- Build static TypeScript site from JSON content bundles
- Regenerate landing pages, state pages, basin pages, plant pages, and weekly briefs
- Deploy to GitHub Pages or Cloudflare Pages automatically after CI passes
Tech Stack:
- Static site: TypeScript + Next.js (static export) or Astro
- Data collection: Node.js scripts, EIA/EPA APIs, bulk CSV parsers, lightweight geospatial joins with DuckDB + GDAL or Turf
- Storage: Versioned JSON/Parquet in repo releases or object storage
- Charts/maps: D3.js, MapLibre GL, Observable Plot
- Image generation: AI hero illustrations + scripted SVG/PNG infographics
- CI/CD: GitHub Actions on daily/weekly/monthly cron schedules
- Hosting: GitHub Pages or Cloudflare Pages
Monetization Model:
- Channel 1: Donations/tips — this is classic public-interest infrastructure journalism; people donate when it helps them understand a hidden local risk.
- Channel 2: Premium local alerts — paid email alerts for “plants near my county,” drought-risk changes, or utility score drops.
- Channel 3: Sponsor slots — environmental consulting firms, water-monitoring hardware, climate-risk tools, legal/newsletter sponsors.
- Channel 4: Data products — CSV/API access for researchers, local journalists, NGOs, and litigators.
- Projected month-1 revenue: $250-$500 (early donations + a few paid subscribers)
- Projected month-6 revenue: $3,000-$6,000/month (SEO pages for every major plant/utility/state, plus sponsorship and premium alerts)
Launch Complexity: 4/5 — moderate-to-high. The data exists, but identity matching across EIA and EPA records plus cooling/water normalization takes real setup. Estimate: 4-6 focused days for MVP, 2 weeks for a strong version. Content Quality Score: 5/5 — hidden infrastructure, real local relevance, strong explainers, powerful visuals, excellent “wait, seriously?” factor. Automation Score: 5/5 — once the ingestion and entity-matching pipeline is stable, the site can run mostly hands-off. Revenue Potential: 4/5 — public-interest sites monetize more slowly than consumer shopping sites, but the niche has authority, backlinks, sponsorship potential, and premium local intelligence upside. Total: 18/20
Why This Will Work: People love accountability journalism when it reveals a cost they were never shown. Heat Sink exposes the invisible physical bargain inside electricity: the grid is not just wires and fuels, it is also rivers, evaporating reservoirs, and communities living beside industrial cooling systems. That makes the content inherently shareable. It also has binge structure: users can go from “my state” to “my utility” to “the plant near my lake” to “how once-through cooling works” in one session. SEO is strong because existing coverage is fragmented, stale, or academic. This channel wins by translating spreadsheet sludge into sharp, visual, local truth.
Risk & Mitigation:
- Risk: Water-use data can be messy and lagged.
Mitigation: Be explicit about data freshness; separate “latest reported” from “live risk overlays.” - Risk: Thermal-discharge data may be inconsistent across permit systems.
Mitigation: Use EPA compliance history for accountability framing, and avoid claiming direct causality without permit/temperature support. - Risk: Could drift into generic anti-power content.
Mitigation: Stay evidence-first and comparative. Praise efficient plants. Criticize bad design and bad disclosure, not electrons themselves. - Risk: The niche sounds technical.
Mitigation: Build every article around a human frame: river, drought, fish, billpayer, county, outage risk.
Full idea file: https://github.com/bullwinkle/HustleIdeas/blob/master/ideas/2026-04-09-1500.md