Water compliance has waited a decade for this tooling.
The rule is public. The data is structured. The agents are capable. Operators have been stuck with binders, consultants, or expensive enterprise suites — and they deserve better. We’re building the tool we’d want as operators.
Make drinking water compliance boring.
The fastest path to safer drinking water is making the compliance work so cheap, so fast, and so reliable that no utility skips it. Not through coercion — through ergonomics. If reporting takes an operator one afternoon instead of a two-week panic in April, more reports get filed, more violations get disclosed honestly, more consumers get accurate information, and state programs spend less time chasing paperwork.
The first deliverable is the Consumer Confidence Report. It’s the most universal annual filing under the Safe Drinking Water Act, and it’s the report every small utility operator dreads. If we can make it trivial, we can make everything else that follows trivial too.
How we build.
Regulation is source of truth, not training data.
The actual text of 40 CFR 141 Subpart O comes directly from eCFR. We don’t paraphrase it. We don’t let LLMs improvise over it. When EPA updates language, we update our cache — not our judgment.
Every number is traceable.
If a value shows up in a published CCR, you can click through to the lab PDF it came from, the page, the row, and the extracted text. A number without provenance does not reach the page. Period.
Fail closed, explain clearly.
When a rule check fails, the agent says exactly which clause, what evidence it reviewed, and what you need to fix. There’s no “acceptable variance” button to override compliance. If a rule doesn’t pass, fix the data — or talk to your primacy agency.
Tool parity between UI, API, and TUI.
Every action a user can take in the dashboard is available as a tool in the API and as a command in the terminal. Your team works where their workflow fits best.
Operators, regulators, engineers.
Small team today. Every member has either operated a water system, regulated one, or built infrastructure at that scale. We’re hiring — see careers.
Andy Yang
Building 1water.ai with the same team that ships TapWaterData.com. Previously at platform-scale infrastructure companies.
The operators and regulators who shape our roadmap.
The ppb-vs-mg/L conversion errors are the single biggest reason state review kicks reports back. Fixing that at the ingest layer is worth the license alone.
We’ve been waiting for someone to treat regulatory text as source of truth instead of training data. That’s the right posture for this market.
Provenance per contaminant value — not just a report that looks right, but a report that can be audited cell by cell. That’s the unlock.
Interested in building this with us?
60-day free trial. No credit card. Your trial becomes your first published CCR.