Technology

One system, from the sensor to the cloud

The device decides. The cloud and the app advise. That one rule shapes every layer we build.

The device is the authority

A connection can drop, a phone can be wrong, a command can be a mistake. The equipment still has to be protected. So the rules that protect it run on the device itself.

Sense

Sensors read the machine's own behaviour at the equipment: pressure, temperature and other signals, sampled locally.

Decide

Firmware learns what normal looks like for each unit and flags the quiet failures that a fixed threshold or a calendar would miss.

Act

Relays and interlocks switch equipment and refuse commands that would harm it. The app can ask. Only the device can allow.

Remember

When the network is down the device keeps its own record.

Close-up of a populated electronic circuit board

Hardware and firmware

Boards and code written for each other

We design our sensor and control boards ourselves and write the firmware that runs on them. Hardware limits and software limits are chosen together, so the protection does not depend on any single layer.

Enclosures are sealed against the weather, and radios use pre-certified modules.

Cloud and identity

Security starts at the device

Trust in a connected product is only as good as the identity of the thing connecting. We begin there.

A certificate per device

Each unit holds its own certificate and enrols itself. Nothing on the wire is shared between units.

Encrypted in both directions

Telemetry comes in and commands go out over encrypted connections.

Built to scale with the fleet

Our cloud runs in a Canadian Amazon Web Services region and is designed so that adding units, and new kinds of units, does not mean starting over.

Tools for the trades

The people who install and service the equipment get their own view of their customers' systems, with their own access.

One platform, more than one product

The pool monitor is our first product. The platform behind it is built to carry others.