The hardware E-stop always wins
If someone cuts the machine with the wall switch or the emergency stop, that wins over any remote command. Local industrial safety is never overridden.
The app reads what every machine is doing (when it starts, how much it processed) and commands operations: pump X litres, start the bottling line, change the chiller setpoint. Always with dual approval and QR-verified physical presence.
Compatibility
Five integration tiers, from the manufacturer's cloud down to manual logging. No machine is left out of the book.
| Tier | How it connects | What you get |
|---|---|---|
| A | Manufacturer's native API (cloud, OAuth) | Read + direct commands, ~500 ms latency |
| B | Modbus TCP / OPC-UA via local gateway | Read + commands to the PLC, ~3-5 s |
| C | Relay + flow-meter retrofit | Start/stop and volume cut-off on machines without a PLC |
| D | Read-only (telemetry) | Live status and counters, no commands |
| E | Manual operator logging | The operation enters the book just as complete |
Safety
If someone cuts the machine with the wall switch or the emergency stop, that wins over any remote command. Local industrial safety is never overridden.
Starting a pump or a line requires a second admin to approve. You cannot approve your own command, even as the owner: there are always two sets of eyes before liquid moves.
For operations that move wine, someone must scan the machine's QR code on the floor. It confirms a person is watching the hose before the pump starts.
You ask for X litres and the flow meter cuts off at the target volume. If the machine stops responding, the command expires and the pump stops: nothing keeps retrying in the background.
The differentiator
Dedicated automation systems record "the pump started at 14:30" and nobody knows which batch it was. In Cepaos, every commanded operation is automatically written to your cellar book and compliance records:
Yes. You can start, stop and request pumping X litres from your phone. Critical commands require a second admin's approval and QR-verified physical presence on the floor — you cannot approve your own command.
Pumps, presses, chillers, bottling lines, CIP systems, boilers, bench scales, in-line sensors, irrigation and more. There are five integration tiers: the manufacturer's native API, Modbus/OPC-UA via gateway, relay + flow-meter retrofit, read-only, and manual logging. No machine stays out of the book.
The plant's hardware E-stop always wins over any remote command. On top of that: dual approval on critical commands, QR-verified presence, volume cut-off via flow meter, and automatic expiry — if the machine does not respond within 10 minutes, the command expires and nothing retries on its own.
Connected Winery is a monthly add-on on top of your Cepaos plan, at list price for your market and currency. Available from the Domaine plan; included in Estate and in custom plans. Check the pricing page or talk to us about your case.
No. The integration uses what your machine already offers: the manufacturer's API or the existing PLC via Modbus/OPC-UA. For machines without a PLC, a relay + flow-meter retrofit is enough, and you can always start read-only or with manual logging without touching anything.
The machine stays under its local control — plant safety never depends on the cloud. Unacknowledged commands expire after 10 minutes and never re-execute on their own; when the connection returns, telemetry syncs and the book stays complete.
Start with read-only (tier D) and enable commands when your team is ready.