Low-earth-orbit satellite broadband providing low-latency connectivity to remote wellheads, pipelines, mines and substations that terrestrial networks never reached economically.
Cloud-native / SaaS SCADA & HMI
Control Systems — DCS · PLC · ESD · HMI
Industry Acceptance
Near-term · 2–5 yrs
Evidence E4 · Multi-site references
SCADA, HMI and historian functions hosted in a cloud region instead of on servers in the plant. Proven for monitoring distributed assets such as water networks and well pads; for closed-loop control of a process unit the local control system remains the place to be.
What moves to the cloud, and what stays
A SCADA system has layers: controllers and RTUs at the asset, communications back to a central point, servers that poll or receive data, and the HMI, alarm, historian and reporting functions that people use. "Cloud SCADA" usually means moving the upper layers, servers, historian, visualisation and reporting, into a public or private cloud, while controllers and their local logic stay on site.
That split matters. The control loop still closes in the controller, so a lost connection should cost visibility, not control. Edge gateways at each site buffer data during an outage and forward it when the link returns, a pattern known as store and forward. Where a site needs local operator screens, a small local HMI is kept as a fallback.
Suppliers offer the cloud in different forms, and the differences are easy to miss. Inductive Automation's Ignition Cloud Edition, launched on the AWS Marketplace in June 2023, is a hosted version of its platform for extending on-premises systems into the cloud; the company states explicitly that it is not SaaS, and the user remains responsible for configuration, backups and upgrades 1. AVEVA announced in July 2025 that it had validated System Platform, its SCADA platform, and its MES on AWS infrastructure, building on several years of its PI System historian running there 2. Fully managed SaaS offerings, where the supplier runs and patches everything, exist mainly for smaller and distributed systems.
| Model | Who runs the software | Typical fit |
|---|---|---|
| Self-hosted in the cloud | The owner or integrator, on cloud virtual machines | Owners with IT capacity who want hardware off site |
| Supplier-hosted edition | Supplier provides the image; owner configures and maintains | Hybrid systems extending on-premises SCADA |
| Software as a service | The supplier operates and updates the platform | Small and distributed systems, limited in-house IT |
Where it pays
The case is strongest for owners with many small, geographically spread assets: water and wastewater networks, pipelines, well pads, renewable plants and remote pumping stations. For them, a central cloud platform replaces many local servers, standardises screens and alarms across sites, and gives engineers and managers secure remote access without building a private data centre. Licensing by subscription also turns a capital project into an operating cost, which suits some utilities' budgeting better than others.
Analytics is the second driver. Once data from all sites lands in one cloud historian, fleet comparisons, energy reporting and condition monitoring become much easier than pulling data from dozens of local servers.
Where it does not
- Continuous process plants with a local DCS gain little: the operator interface is already central, and adding a cloud dependency to it adds risk without much benefit.
- Sites with weak or expensive connectivity cannot rely on it, although LEO satellite links have widened the set of sites where it is practical.
- Regulated environments may restrict where operational data is stored and who can access it; check data-residency and sector rules first.
- Operator response to alarms must not depend on the internet link. Alarm paths for safety-relevant conditions need a local or independent route.
The security question
Moving SCADA to the cloud is often presented as a security risk, but the more common real-world failure is the opposite: control equipment exposed directly to the internet for convenient remote access. In late 2023, an Iran-linked group calling itself CyberAv3ngers compromised Unitronics PLCs with built-in HMIs at US water and wastewater facilities, including one in Pennsylvania; the devices were frequently reachable from the internet, and CISA's joint advisory AA23-335A told owners to change default passwords and remove direct internet access 3.
A well-designed cloud architecture removes that exposure: field devices make outbound, authenticated connections through a gateway, nothing at the site accepts inbound connections from the internet, and remote users reach screens through the cloud platform with multi-factor authentication. A badly designed one simply moves the exposure. The architecture, not the hosting location, decides which you get.
Evidence timeline
- Jun 2023Inductive Automation releases Ignition Cloud Edition on the AWS Marketplace (not SaaS: owner maintains it). 1
- Dec 2023CISA advisory AA23-335A after Unitronics PLC/HMI compromises at US water facilities. 3
- Jul 2025AVEVA validates System Platform and MES on AWS infrastructure. 2
Why it sits at the Industry Acceptance stage
Cloud-hosted SCADA for monitoring and supervising distributed assets is in production with many owners and several suppliers, which is why it sits at the Industry Acceptance stage with evidence level E4. The remaining questions are about architecture, security practice and cost over time, not feasibility.
We do not expect the cloud to replace the local control system for process units within the horizon shown, and the placement should not be read that way.
Adoption signals to watch
- Water and energy regulators publishing explicit expectations for cloud-hosted operational systems.
- Published total-cost comparisons between subscription and on-premises SCADA over a full lifecycle.
- Supplier-run SaaS offerings certified against IEC 62443 or equivalent security standards.
Questions to ask before committing
- Which functions move to the cloud, and what keeps working locally when the link is down?
- Does any site device accept inbound connections from the internet? It should not.
- Who patches and backs up the platform: us, the integrator or the supplier?
- Where is the data stored, and does that meet our regulatory and contractual obligations?
- What does the subscription cost over fifteen years, compared with on-premises servers?
Terms used on this page
- Edge gateway
- The on-site device that collects local data and forwards it to the hosted platform.
- Store and forward
- Buffering data locally during a communications outage and sending it afterwards.
- Multi-tenant
- A hosted service in which many customers share the same platform, separated logically.
Sources
- Ignition Cloud Edition now available in AWS Marketplace
- AVEVA successfully validates its SCADA and MES software on AWS infrastructure
- CyberAv3ngers hit Unitronics PLCs at multiple US-based water facilities
- IRGC-affiliated cyber actors exploit PLCs in multiple sectors (AA23-335A)
Related technologies
See this entry on the full maturity map · All Control Systems entries · How placements are made. Stage and time-horizon placements are editorial judgements based on the public sources listed above, as of October 2026. They are not engineering, safety or investment advice; see the Terms of Use.