A design-partner pilot
One process, one number, shadow mode first.
The most useful first conversation is about one process, one plant and one measurable problem. Tell us which, and we will tell you what shadow mode would need and what it would baseline.
Illustrative scenario: one municipal activated-sludge wastewater plant with a membrane train, planning the next 24 hours after a rain forecast. Not a measured run.
The form opens your mail client with the message addressed to hello@hydrira.com. Nothing is stored on this site.
One mailbox while the team is small. Named addresses follow as people join publicly.
One process, one number, shadow mode first.
OEMs, SCADA and control vendors, analyzer suppliers and engineering firms who sell into utilities.
Design posture, data flows and roadmap dates.
Perception, OT integration, simulation or water process.
Every Hydrira run is an ordered, inspectable sequence. This is run_scn_0418, an illustrative scenario: one municipal activated-sludge wastewater plant with a membrane train, planning the next 24 hours after a rain forecast. Ten steps, nine automatic, one human approval on the blower setpoint move, every action written to the shift record.
Intake-and-Screen · Flow, turbidity, ammonia and alkalinity at the headworks, and a 24-hour rain forecast that raises the expected influent by mid-afternoon.
Plant orchestrator · Simflo evaluates candidate dose, DO and flux plans over the 24-hour horizon and keeps the plans that hold permit margin through the surge.
Quality-and-Anomaly · Clarifier blanket, foam and colour from the basin cameras fused with turbidity, pH, nutrient and residual analyzers into one calibrated plant state.
Dose-and-Coagulate · Coagulant and polymer dose ramp for the surge window under turbidity, phosphorus, sludge and chemical-cost constraints, cited to the plant's dosing SOP.
Dose-and-Coagulate · A bounded setpoint move inside the declared rate and magnitude limits for the dosing pump, with the rollback value recorded first.
Aerate-and-Bio · Blower and DO setpoint schedule across the basins that meets the nitrogen and phosphorus targets at the lowest kilowatt-hours the biological state allows.
Plant orchestrator · The DO setpoint change is above the plant's threshold for this loop. The process engineer on shift reviews the predicted nutrient margin and approves.
Membrane-and-Disinfect · Flux held through the surge and the next backwash moved earlier, inside the integrity envelope; the disinfection residual minimum is untouched.
Compliance-and-Energy · Every planned setpoint checked against the discharge permit, the nutrient limits and the residual minimum, with excursion risk forecast for the horizon.
Quality-and-Conformance · Inputs, model versions, predictions, limits, the approval and every write appended to the immutable shift record the plant owns.
Gates, not dates. Each stage starts when the previous one has proven its number against your own baseline.
Land on one process with a measured baseline. Expand by process, plant, fleet site and autonomy stage. Outcome components available on energy, chemicals, compliance and reliability.
Dosing, aeration or membrane control, or quality-sensing AI, for one process. For utilities and operators validating ROI on the wedge.
Whole plant: intake and screen, dose and coagulate, settle and filter, membrane and disinfect, aerate and bio, sludge and dewater, quality and anomaly, compliance and energy, and the Simflo twin.
Multi-site utility or industrial fleet, custom process, compliance and energy models, a plant-edge fleet and SLAs. For operators standardizing on Hydrira.
A 15 to 20% discount for annual prepayment.
Per-cubic-meter, per-process or per-action metering above plan limits.
A share of measured energy, chemical, compliance or reliability improvement on the highest-value workflows, for enterprise deals.
Enterprise and utility agreements with usage ramps tied to flow and sites. Floor pricing is protected; discounts are traded for term and public-sector references.
One policy model, one audit trail and one set of energy, chemical, compliance and water-quality benchmarks across every plant in the fleet, with each site's permits, SOPs and process models kept private to that site.
Hydrira writes to control equipment in a plant that keeps a community's water safe. Every capability is scoped, every write is policy-checked, every output is cited, and every action is written to an append-only audit log the plant owns.
| Item | Scope | Status |
|---|---|---|
| SOC 2 Type I + critical-infrastructure cyber review | Cloud control plane, edge | QUEUED Roadmap, first 6 months |
| SOC 2 Type II | Cloud control plane | QUEUED Roadmap, 6 to 12 months |
| SDWA · discharge permits · EU WFD · nutrient and PFAS rules | Grounding and record-keeping | RUNNING Design basis for retrieval and the audit log |
| Per-tenant isolation | Data, memory, models | RUNNING Design rule |
| On-prem or edge-only deployment | Utilities, critical infrastructure | RUNNING Design option |
Hydrira supports your compliance records. It is not a certification, it does not replace your permit and it never removes the operator of record from a compliance decision.
The three people in a treatment plant whose week changes when the process runs itself, and what each of them needs from Hydrira.
Owns compliance, reliability, energy, chemicals and cost. Wants autonomous, compliant, lower-energy, lower-chemical treatment, and a number that justifies the spend.
Owns dosing, aeration, membrane and biological strategy, the process windows and the performance. Needs recommendations they can inspect, correct and trust before any loop is handed over.
Owns permit compliance, water quality, energy and environmental reporting and the licence to operate. Needs every action cited, logged and defensible in front of a regulator.
IT/OT and critical-infrastructure cybersecurity leads approve the deployment. There are no customer quotes on this site yet; design partners will be the first voices.
Hydrira reads and writes through the systems already in the plant. No parallel historian, no new HMI, no rip-and-replace. Connectors are built against each design partner's stack first; long-tail integrations are out of scope for the first release.
Plant SCADA, historians, PLC and DCS interfaces
Tag reads at 1 to 10 Hz, guarded setpoint writes, interlocks untouched
Coagulant, polymer, pH-adjust and disinfectant dosing controllers
Dose reads, bounded setpoint writes inside declared limits
Blower controls, DO and ammonia-based aeration control
DO and blower reads, bounded setpoint writes after approval
Membrane and RO skid PLCs, TMP, flux, conductivity, integrity monitors
Reads; flux and backwash writes inside the integrity envelope
Turbidity, pH, chlorine residual, nutrient, TOC and flow analyzers
Reads; drift and fault flags
Lab information systems, jar-test and grab-sample records
Reads for labels and calibration
Fixed cameras on clarifiers, basins, filters and membrane rooms; inspection robots
Streams fused at the edge; supervised routes
Utility MES, maintenance systems, permit and reporting systems, weather
Reads; shift record and report drafts written back
The questions operations managers, process engineers and compliance leads ask in the first meeting.
Only at the autonomy stage your plant has set, and only to an explicit allow-list of low-risk loops inside documented limits. Every design partner starts in shadow mode, where Hydrira predicts and writes nothing. Assist mode follows, where a process engineer approves each move. Bounded write-back comes last, per loop, after the accuracy gate and compliance sign-off, and can be pulled back at any time.
No. Permit-limit setpoints, disinfection residual minimums, integrity limits and discharge release decisions are read and checked, never written. Permia evaluates every planned move against the permit set and blocks anything that would thin a margin. The operator of record stays the operator of record.
The plant keeps running on its existing SCADA, PLC and DCS control and interlocks. Hydrira is supervisory, not primary. Loss of Hydrira is loss of advice, and the gap is recorded in the shift record.
Shadow mode starts with the SCADA tags, analyzer streams and lab records you already have. Accuracy is measured against your own lab and analyzer baseline, and the first-release plan converts to assist mode only when the number is proven. The design targets assume telemetry you already collect, not new instrumentation.
Telemetry, permits, SOPs and models are tenant-scoped, and an on-prem or edge-only deployment is available for utilities. Cross-plant learning is federated and IP-isolated, planned and opt-in: patterns for similar basins, membranes and influent regimes move, raw data does not.
Not yet, and the site does not claim it. SOC 2 Type I with a critical-infrastructure cyber review is on the roadmap for the first six months, Type II for the six to twelve month window. Safe Drinking Water Act, discharge permit, EU Water Framework and nutrient and PFAS rules are what the retrieval grounds on and what the audit log is aligned to; that is a design basis, not a certification.
The one with the clearest number. Aeration energy on an activated-sludge plant, coagulant cost on a dosing train or membrane run length on an RO or MBR train are the usual wedges, because kilowatt-hours, chemical invoices and cleaning counts are already measured. Turbix is the sensing wedge where visibility is the first problem.
Two to four utilities or industrial sites instrument one wedge process in shadow mode and baseline energy, chemicals and compliance from their own records. Assist mode proves accuracy and ROI with an engineer approving each move. Graduated autonomy follows on low-risk loops. Expansion adds adjacent processes, then fleet sites. Gates, not dates.
A sentence about the process and the number is enough to start.
↑↓ navigate↵ openesc close