Should your monitoring intelligence live out in the field or up in the cloud? It is one of the most common architecture questions in modern SCADA, and the honest answer is "both, in the right proportions." This guide explains what edge and cloud each do best and why the strong pattern is hybrid.
The short answer: Edge computing processes data in the field - buffering, filtering, and running time-critical logic near the source for resilience and low latency. Cloud SCADA provides elastic storage, analytics, and access from anywhere with no infrastructure to run. The best architecture is hybrid: edge devices feeding a cloud platform.
Edge computing handles what must be immediate or must survive an outage. An edge device buffers data locally when a link drops and forwards it later, filters and reports by exception to save bandwidth and battery, and can run local alarms without a round trip. On remote oilfield sites with flaky cellular, that resilience is not optional.
Cloud SCADA removes the server room: elastic storage that scales without capacity planning, analytics and machine learning on pooled data, automatic updates, and access from any browser anywhere. For distributed operations, that means new sites onboard fast and the whole fleet is visible in one place. What the cloud is bad at is the far edge on a bad link - which is exactly what the edge covers. Our cloud vs on-premise guide covers the hosting side of this.
It is not either/or. A small, low-power edge agent does the field-side work - reads local devices, buffers, publishes by exception - and a managed cloud platform does storage, analytics, alarming, and the operator experience. Merobix uses exactly this pattern: edge buffering plus MQTT Sparkplug B into a managed cloud, so remote sites stay reliable and you run no infrastructure.
| Dimension | Edge | Cloud |
|---|---|---|
| Strength | Resilience, low latency, bandwidth savings | Storage, analytics, access anywhere |
| Weakness | Limited storage/analytics locally | Struggles on the far edge / bad links |
| Infrastructure | Small device in the field | None to run (managed service) |
| Best answer | Do field-critical work | Do everything else |
Edge processing happens in the field for resilience, low latency, and bandwidth efficiency; cloud SCADA provides elastic storage, analytics, and access from anywhere with no infrastructure to run. The strongest architecture is hybrid - edge devices feeding a cloud platform.
Cloud SCADA paired with an edge device is, because the edge buffers data through outages and forwards it when the link returns. Pure cloud with no edge struggles on marginal links; that is why the hybrid model exists.
For remote sites with unreliable connectivity, yes - an edge device provides the store-and-forward and bandwidth efficiency the cloud alone cannot. For well-connected sites, a lighter edge or gateway may suffice.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix pairs edge buffering with a managed cloud - remote sites stay reliable, and you run no servers.