THE CLOUD
A record for each monitored destination, at every site you run.
Every unit watches up to six destinations you choose and name: the card processor, the lottery host, the cameras, the back office, whatever the counter actually depends on. On the unit those six are a live picture. Enrol it, and each one of them gets a history, a commitment and an alerting rule of its own.
That is the whole shape of what the cloud adds. It does not attach to a site, because a site is not up or down. The payment host is reachable and the guest network is not, and those are two different facts, with two different providers to call and two different amounts of money at stake.
6 per unit
Destinations you pick and name yourself
Own target
Each destination carries its own SLA figure and its own billing month
Own rules
Alert condition and threshold set per destination, per site
Own evidence
A report scoped to one destination, for one provider
WHAT ENROLLING ADDS
Six things, all of them attached to a destination.
Hold the payment host to something strict and the guest network to something loose. Each destination carries its own target, and its own billing day, so the processor’s month can close on the 15th while the ISP’s closes on the 1st.
Each destination keeps its own daily record, so the afternoon the card host degraded stays visible as the card host degrading, instead of being averaged into a site that was otherwise fine.
A condition and a threshold set on one destination at one site. The camera recorder is allowed to wobble at midnight. The payment host is not, and only one of them wakes anybody.
An SLA evidence report scoped to a single destination, carrying a SHA-256 of its own contents. What you attach to a ticket with that provider, rather than a site summary they can wave away as someone else’s problem.
Define the destination list once as a template and push it to selected sites or the whole fleet, so that the name means the same host at every location and the numbers are actually comparable. A unit that was offline picks the list up when it returns.
The figure across every location is weighted by the seconds actually measured against each site’s primary destination, so a unit that spent a week unplugged cannot quietly improve the average.
NO DATA IS NOT GOOD NEWS
A destination nobody measured is not a destination that was up.
The unit watches your destinations. The cloud watches the units. A sensor that stops checking in is surfaced centrally exactly as a destination going dark is surfaced locally, so a site dropping off the map is an event rather than an absence of events.
That distinction is where most monitoring quietly lies. A gap in measurement is recorded as a gap, and excluded from the availability figure rather than counted as success. Nobody’s SLA number improves because a unit lost power, and a destination that was never probed never reports a comfortable one hundred per cent.
Each operator sees only their own sites. Separation is enforced at the platform, not by which screen somebody was given.
Units join with a one-time claim code and prove who they are on every connection with a key they generated themselves and never sent us. Enrol a unit, move it to another site, or decommission it entirely, all from the same place.
IF YOU NEVER ENROL
What each destination gives you either way.
A ring per destination, its quality score, and an on-screen alert naming the one that failed, held back until the failure is confirmed rather than fired on a single dropped packet.
Each destination’s own log: every outage against it, how long it lasted, the measurements around it, and the route toward that destination at the moment it failed.
A printable dispute pack, produced by the unit, for the conversation where a provider says they saw nothing wrong.
The same destination watched at every location you run, on one list, with one set of names.
A commitment tracked against a destination across a billing month, and the evidence report for it arriving without anyone remembering to produce it.
Anything that has to reach a person who is not standing in front of the unit.
There is no licence key and nothing nags you. A unit also answers on the machine itself, so a script on your own network can ask how a given destination is doing and get a straight answer back without an account existing anywhere.
Request beta access