MAYAUPS CLOUD - LIMITED BETA

Every site on one screen, and nothing gains control of your equipment.

Most remote monitoring asks you to accept a trade: you get the overview, and in exchange a vendor platform sits somewhere in your power chain. MayaUPS Cloud refuses that trade. Each site keeps its own MayaUPS, which stays the only thing that polls your equipment, evaluates alarms and decides on shutdown. The portal is a read-only view of what those sites report. It is in limited beta and open to named pilot sites.

The rule

The portal can look. It cannot touch.

There is no command channel. When a site posts its status, a successful answer from the portal is empty, so there is nothing for an instruction to travel in. That is a property of the design, not a setting you have to keep an eye on.

No remote shutdown, restart or equipment write of any kind
No remote change to shutdown thresholds, targets, arming or the kill switch
No remote change to write credentials or to the trust an agent relies on
If the portal is unreachable, or compromised, your sites carry on exactly as before

What is sent

A short status summary, and nothing else

This is the complete list of what leaves a site. It is worth reading in full, because what is missing from it matters as much as what is on it.

Device identity: serial number, make, model and the label you gave it
Whether the device is reachable
Named conditions with their severity and the time they appeared
The time the device was last observed, and the version of the software reporting
No measurements: no voltage, no load, no runtime, no temperature, no history

Off by default

Three settings to turn it on, one to stop it

Nothing is sent until an operator sets all three of the required values on that site. Until then the site holds its data and says nothing. Removing any one of the three stops it again, immediately and locally.

Outbound only, over HTTPS, from the site to the portal
A site that never turns it on is invisible to the portal and works normally
There is no product telemetry anywhere else in MayaUPS

Freshness

An alarm does not wait for the next heartbeat

A condition that changes is sent within about a minute, damped so a flapping device cannot flood anything. Separately, a heartbeat proves the site is still alive: hourly by default, and every fifteen minutes for pilot sites. The two jobs are deliberately different.

The portal shows how old each reading is, per site and per device
A site that goes quiet is shown as quiet, not as healthy
Gaps are shown as gaps; missing data is never drawn as a zero or a green light

Where it lives

Hosted in Quebec

The portal runs on a server in Beauharnois, Quebec. For files that ask where data physically sits, that is a short and checkable answer. Note the ownership question separately: the hosting provider is a French company operating on Quebec soil, outside the reach of the United States CLOUD Act, which is not the same claim as Canadian ownership.

Detailed history stays on your own server, at your own site
MayaUPS on its own is self-hosted software with no cloud dependency at all
Sites that must never talk outward simply leave the portal switched off

Honest limits

What this beta is not

A short list of things the portal does not do today. If one of them is what you need, say so and it goes on the record rather than into a sales promise.

Not a complete central history: the portal holds current state, not your archive
Not a place to administer users, organisations or partners
Not a staffed watch service; it is software, and support terms are quoted separately
Not a replacement for the local interface, which remains the detailed one

Frequently asked questions

If the portal goes down, do my sites stop being protected?

No. Every site polls, alarms and shuts down on its own. The portal is a view of what sites report, never a link in the chain that protects them. A site that cannot reach the portal keeps working and keeps its data until it can.

Can someone with access to the portal shut down my equipment?

No. There is no path for a command to travel from the portal to a site. The successful response to a status post is empty. Safety-critical settings such as thresholds, targets, arming and the kill switch can only be changed on the site itself.

Do I have to use the Cloud portal?

No, and it is off until you turn it on. MayaUPS was designed to work with no Internet access at all, and many sites run it that way on purpose. The portal exists because operators running several buildings asked for one screen.

What does the portal do with old or missing data?

It shows it as old or missing. A site that stops reporting appears as stale with the age of its last reading, rather than holding its last good state and looking healthy. Presenting an unknown as normal is the failure we most wanted to avoid.