Edge and gateways
The box that runs the analytics inside your plant and talks to the cloud without depending on it.
All three, at the edge
Recording, detection and temperature reading happen inside the plant. They keep working with no internet.
An air-gapped mode
And a verifiable one: you can check that nothing leaves, instead of trusting that nothing does.
Enrolled with a code
The device provisions itself. There is no night of manual configuration per site.
It recovers by itself
A service that falls over is relaunched without anyone logging in at 3 a.m. Updates are signed.
Why it matters
“In the cloud” sounds fine until the link is cut. The question to ask any platform is not where the software lives, but what stops working when the fibre breaks.
How it works
- 01
Recording, detection and temperature reading happen at the edge. With no internet, all three keep working.
- 02
The server carries assets, alarms, protocols and work orders; the cloud, if there is one, carries multi-site and fleet.
- 03
Zero-configuration install: the box is claimed with a code and provisions itself.
- 04
It recovers on its own. A service that falls over is relaunched without anyone driving in at night.
In practice
An install with no internet at all
There are plants where an outbound connection is not an option. The platform has a no-egress mode that blocks any outward call and declares it in its own health check, so it is verifiable rather than promised.
Capabilities
- Analytics at the edge, independent of the link
- Verifiable no-egress mode
- Provisioning by code, no manual setup
- Service self-recovery
- Signed updates
- Multi-edge topology and site-to-site relay
What it does not do yet
- Heavy continuous analytics — boxes per frame across many cameras at once — needs more compute than a small edge box has. There is accelerated hardware for that; sizing it is part of the project, not a detail.