It runs the water so nobody has to be there. Autonomous operation inside strict safety limits, remote oversight from anywhere, and a signed record of everything it does.
AUTONOMOUS · L2 BOUNDEDUPTIME 247 DSAT LINK · 210 MS14:52:41ZREQUEST CONTROL
Delivered today41,368 L
Output flow24.2 L/min
Energy3.1 kWh/m³
Quality0.14 NTU
Storage82%
Process flowdigital twin · live
Safety envelopehard limits · deterministic
Pressure
2.9 bar
Core temp
61.8 °C
Dosing
0.4 ppm
Turbidity
0.14 NTU
Pleia OS decisionslive
14:52:07●
Recovery setpoint raised to 0.71 (heat surplus 8.2 kW)
14:47:31●
CIP cycle scheduled for 03:00 (fouling drift 2.1%/day)
14:41:12✓
Window 14:30–14:45 signed · record 9f3a…8ac6
14:38:55⏸
Dosing change outside envelope → queued for operator
14:31:04●
Tank B feed balanced · distribution pressure steady
14:24:48✓
Quality panel PASS · turbidity 0.14 NTU
14:19:33●
Genset heat capture rebalanced · 8.2 kW to core
14:12:20●
Distribution pump duty cycled · demand forecast low
14:05:41✓
Sensor trust check · 7 of 7 within calibration
Next service in 18 days · spares kit printed ✓Alarm 1 active · filter drift (advisory)Last record 14:45Z · signed · verifiable offline
01 The loop
Sense. Decide. Act. Sign.
01Sense
Custody-grade sensors on every line: intake, return, reuse, quality, energy, equipment health. Continuous, not sampled.
02Decide
The intelligence finds the best operating point and plans maintenance, always inside deterministic safety limits it cannot cross.
03Act
Setpoints, cleaning cycles, recovery scheduling, alerts. A human approves anything outside the validated envelope.
04Sign
Every window of operation is hashed, chained and signed into the Verified Water Record. What happened is provable, forever.
02 The operator problem, solved
One licensed operator. A whole fleet.
The law requires a certified operator; remote sites cannot staff one. Pleia OS inverts the model: units run themselves, and one operator supervises many sites from anywhere, approving what needs a human and proving what happened.
SITESTATEDELIVERED TODAYNEXT SERVICE
PLEIA-01 · northern communityAUTONOMOUS41,300 L18 d
Performance curves flag fouling early, so cleaning happens on schedule instead of after a failure.
CONSUMABLESSupply forecasting
Cartridges and spares are ordered by forecast, matched to the resupply windows remote sites actually have.
SERVICEPlanned windows
Maintenance lands in planned visits with printed spares waiting, not emergency flights.
04 Months, not days
Built to be left alone. And to prove it.
Pleia OS is designed around one question: how long can this plant keep delivering verified safe water before a person has to come? That is the Autonomy Horizon, the number Pleia is built to extend.
Every litre it delivers is signed into a record a funder, insurer or regulator can check themselves, and plan or pay against.
AI assists operation. It never decides the water is safe. Safety comes from deterministic limits and validated treatment barriers.
05 The guardrail
AI-assisted. Never AI-controlled.
A language model never touches the control loop. Actuation runs on deterministic safety interlocks: hard limits on pressure, dosing, temperature and quality that no model can override. The intelligence proposes; physics-checked logic decides. When Pleia OS cannot verify something, it says so instead of guessing. One licensed operator oversees many sites from the Pleione operations center, and a trained local steward is the plant's hands for the rare physical task, guided step by step by Pleia OS. Never a silent failure: if something is wrong, the community hears it from the plant first.
06 What it signs
Operations end as evidence.
Every window of operation becomes a Verified Water Record: tamper-evident, independently checkable, even with the internet switched off. Pleia OS runs the water; the record proves it.
INCOMPLETEHonest by design. It will not fake a clean pass.
STATUS
Built, and running honest.
Pleia OS is live today on real and simulated facility feeds: measurement, verification and signed records. Autonomous control expands only as each capability is validated, advisory first, bounded control after. Pre-revenue, and labeled that way.