Comparison
Cloud vs on-premises energy monitoring. Which one fits your plant?
Both kinds read the same meters. The difference is where the readings are kept, who controls them, and what still works when the Internet drops. This page puts the two side by side on cost, security, outages and growth, so you can choose for your own plant.
The short answer
Cloud monitoring suits sites with steady Internet, no concern about data leaving the site, and a wish to start fast. On-premises suits plants where the Internet drops, where owners want production data to stay inside, and where an alert must arrive every time. For most factories, the deciding questions are how reliable the Internet is and who should hold the data.
Cloud keeps your data on the vendor’s servers. On-premises keeps it in your plant. Choose by what must keep working when the link goes down.
What each one means
Cloud. A gateway in the panel reads the meters and sends every reading over the Internet to the vendor’s servers. The dashboard, history, alerts and reports all run there, and you open them through a website or an app.
On-premises. The gateway reads the meters and keeps the history inside the plant. The dashboard opens on the plant network. For access from outside, an encrypted link reaches the gateway, and the data itself stays inside.
Hybrid. The full history stays on site, and a copy or summary also goes to a cloud. It works locally and gives a cloud copy, with two places to secure.
The meters, CTs and RS-485 cable are the same in all three. What changes is where the software runs and where the history is kept. See what is an energy monitoring system for the parts.
Side by side
| Question | Cloud | On-premises |
|---|---|---|
| Where the history is kept | On the vendor’s servers | Inside your plant |
| When the Internet is down | Readings may wait on the gateway; alerts and the dashboard can stop | Reading, recording, alerts and the plant dashboard carry on |
| Access from outside | Through the vendor’s website or app | Through an encrypted link to the gateway |
| Getting started | Fast: connect the gateway and sign in | Set up on site, once |
| Ongoing cost | A fee, often per meter, user or site, plus the Internet link | Support and updates, often as a subscription |
| Who controls the data | The vendor’s terms | You, physically |
| If the vendor shuts down | The history can go with the servers | The history stays in the plant |
| Software updates | Done on the vendor’s servers | Sent to the gateway, remotely or on site |
| Growth | Add meters and sites through the vendor | Add gateways; sites join one dashboard |
Which is cheaper?
It depends on how far ahead you look. Cloud often costs less on day one, because there is nothing to set up on site beyond the gateway. Over five years, a fee per meter, user or site adds up, and the Internet link the system depends on becomes a cost of its own.
On-premises used to mean a server PC, a database licence and someone to look after them. That is what made it expensive. A gateway that stores its own history removes the server, so the running cost is mostly support and updates.
When you compare quotes, put the same items side by side, over the same five years:
- Hardware: gateways, any new meters and CTs, and cabling.
- Installation and setup.
- The subscription or licence, and what it covers.
- The Internet link, if the system needs one to work.
- A server PC and its upkeep, if one is needed.
- The cost of leaving: getting your full history out in a form you can use.
This page gives no prices, because every plant’s quote is different. The buying guide lists what moves the cost.
Which is more secure?
Security is about who can reach the data, and how.
- Cloud: the data sits on servers that also hold other customers’ data, reached over the Internet. The vendor secures them, so you depend on the vendor’s practices and on your users’ passwords.
- On-premises: the data sits inside your plant network. The risk to manage is remote access. It must not need open ports on your router, and only approved devices should connect.
- Both: logins with roles, encrypted links, and software updates that fix security issues.
An on-premises system reached through an open router port is less safe than a well-run cloud. Ask exactly how remote access works before you choose.
When the Internet goes down
This is where the two differ most in a factory. Take an illustrative day: the plant’s Internet drops at 10:40 and comes back at 13:10. At 11:52, two compressors and a furnace start together, and demand climbs towards Contract Demand.
- Cloud: the gateway may hold the readings and upload them later, so the history can be complete. But the warning needed the servers, so it never went out. The penalty shows up on the bill.
- On-premises: the warning is raised on site at 11:52, while someone can still hold back a load.
Ask any vendor: how long does the gateway hold readings, do alerts work with no Internet, and does the dashboard open on the plant network? See MD penalty for what one missed interval costs.
Data ownership, and leaving a vendor
Energy data shows more than energy. It shows shift patterns, running hours, when the plant is busy and when it is idle. Many owners treat that as business information. Before you choose, ask:
- Can you export all of the history at full detail, not just summaries?
- What happens to the history if you stop paying?
- What does the contract say about the vendor using your data?
With on-premises, the history is already in your plant, whatever happens to the contract.
Remote access without the cloud
On-premises does not mean you can only look at it from inside the plant. An encrypted private network links approved phones and laptops to the gateway, with no ports opened on the router. Owners and plant heads can watch live readings, Maximum Demand and alerts from anywhere. The history still never leaves the plant.
Hybrid setups
Some buyers want both: each plant keeps working on its own, and head office gets one combined view. There are two ways to get that:
- On-premises with a cloud copy. Each plant sends a copy or summary to a cloud. Simple to view, but the copy is off site and needs securing too.
- On-premises plants joined in one dashboard. Each plant keeps its own history, and the dashboard brings them together over encrypted links, with no cloud copy.
Either way, ask where each copy lives and who secures it.
Which one should you choose?
| If this is true for your plant | Lean towards |
|---|---|
| The Internet is steady, and data off site is fine | Cloud |
| You want to start in a day, with no one on site to set up | Cloud |
| The Internet drops, or the plant is far from town | On-premises |
| Owners do not want production data outside the plant | On-premises |
| Alerts must arrive every time, to avoid a penalty | On-premises |
| Customers or auditors ask where your data is stored | On-premises |
| Several plants, one combined view | Either, if it supports several plants |
Questions to ask either kind of vendor
- Where exactly is my history stored, and who can see it?
- What works, and what stops, with no Internet for a day?
- How does remote access work? Are any router ports opened?
- Can I export all of my history at full detail?
- What happens to my data if I stop paying, or you close?
- What do the fees cover over five years, and what is extra?
Where KONDUKTOR® EMS stands
KONDUKTOR® EMS is on-premises. Gateways read the multifunction meters on your panels over Modbus RTU, any brand, up to 10 meters per gateway, and keep the history inside the plant, with an encrypted backup on a plant computer. Nothing is sent to KONDUKTOR or to any cloud, and no server PC is needed.
- It keeps reading, recording and alerting with no Internet.
- Remote access over an encrypted link, with no router ports opened and only approved devices allowed. Admin, Operator and Viewer logins.
- Several plants appear in one dashboard, with one combined energy and bill report, while each plant keeps its own data.
- Excel and CSV export of every meter’s history.
- If the subscription lapses, monitoring pauses and the history stays on the gateway.
For the full detail, see on-premises energy monitoring.
Common questions
Which is better, cloud or on-premises energy monitoring?+
Neither in every case. Cloud is quick to start and easy to reach from anywhere. On-premises keeps the data in the plant and keeps alerting when the Internet is down. For a factory with patchy Internet, or owners who want production data kept inside, on-premises fits better.
Is on-premises or cloud cheaper?+
Cloud often costs less on day one. Over several years, fees per meter, user or site, and the Internet link, add up. On-premises used to need a server PC and someone to run it. A gateway that keeps its own history removes the server, so the running cost is mostly support and updates.
What is the difference between cloud and on-premises security?+
In the cloud, your data sits on the vendor’s servers and is reached over the Internet, so you rely on the vendor’s security. On-premises, it sits inside your plant network, and the risk to manage is remote access. That must not need open router ports, and only approved devices should connect.
What are the advantages of cloud over on-premises?+
A fast start, no hardware to look after on site beyond the gateway, updates handled by the vendor, and easy access from anywhere. These matter most for small sites with steady Internet and no concern about data leaving the site.
Does on-premises energy monitoring work without the Internet?+
Yes. The gateway reads the meters, records the history and raises alerts on site, and the dashboard opens on the plant network. The Internet is needed only to view it from outside the plant and for software updates.
Can I see on-premises data from outside the plant?+
Yes, over an encrypted link from approved phones and laptops to the gateway, with no router ports opened. You see the same live readings and history, while the data itself stays in the plant.
What is a hybrid energy monitoring setup?+
One that keeps the full history on site and also sends a copy, or summaries, to a cloud. It works locally and gives a cloud copy, but there are then two places to secure, and the cloud copy is still off site.
See monitoring that stays inside your plant.
Book a live demo and see live readings, alerts and history, with nothing sent to a cloud.