What Is a
SCADA Server?
Cloud vs On-Premise (2026)
A SCADA server is the computing hardware that runs traditional on-premise SCADA software - collecting data from field devices, running the historian database, serving the HMI interface, and processing alarms. For decades, a SCADA server was an unavoidable part of any industrial monitoring system. Cloud SCADA has changed that. This guide explains what a SCADA server is, what it costs, the problems it creates, and how cloud SCADA eliminates the need for one entirely.
What Is a SCADA Server?
A SCADA server is a dedicated computer - typically an industrial-grade rack-mount or tower server - that runs the core SCADA software applications for an industrial monitoring system. In traditional SCADA architecture, the server sits between the field devices (PLCs, RTUs, flow computers) and the operator workstations (HMI screens), handling all data collection, processing, storage, and distribution.
Role in Traditional SCADA
The SCADA server performs several critical functions in a traditional on-premise system. The data acquisition service polls field devices via Modbus, EtherNet/IP, OPC, or other protocols and writes tag values to the server memory. The historian service archives tag data at configured intervals to a database - typically SQL Server, MySQL, or a purpose-built time-series historian. The alarm service evaluates tag values against configured setpoints and generates alarm events. The HMI service serves the graphical interface to operator workstations over the local network. All of these functions run on the same server, or on redundant pairs of servers in critical applications.
Hardware Requirements
A SCADA server is not a standard desktop PC. Industrial SCADA servers require high-reliability hardware: ECC memory, redundant power supplies, RAID storage arrays, and sometimes redundant network cards. For critical applications, two servers in a hot-standby redundancy configuration are required, along with a UPS and an environmental monitoring system for the server room. The hardware alone for a properly specified SCADA server installation runs $10,000–$50,000 depending on scale and redundancy requirements.
Software That Runs on a SCADA Server
- SCADA application - the HMI and supervisory software that runs the monitoring system
- Historian software - a dedicated time-series historian or an embedded historian for archiving tag data
- Database engine - SQL Server or Oracle for configuration data storage
- OPC server - For protocol conversion between PLCs and the SCADA application
- Operating system - Windows Server (most SCADA applications do not support Linux)
- Remote access software - RDP, VPN, or SCADA-specific remote viewer
Traditional SCADA Server Setup Costs
Server Hardware: $10,000–$50,000
Industrial-grade server hardware for a SCADA installation includes the primary server, redundant server (for critical applications), UPS, rack enclosure, KVM switch, and environmental monitoring. Entry-level single-server configurations start around $10,000 for hardware. Redundant hot-standby configurations with proper UPS backup and server room environmental monitoring run $30,000–$50,000 and up.
Operating System and Licensing
Windows Server licensing for a SCADA server runs $1,000–$5,000 per server depending on edition and client access licenses. SQL Server licensing - required by most SCADA historians - adds $1,500–$15,000 depending on edition. Microsoft maintenance contracts add 15–25% of license cost per year. Total OS and database licensing over a 5-year lifecycle easily reaches $10,000–$40,000.
Redundancy Requirements
Any SCADA system supporting safety-critical operations or high-value production equipment requires server redundancy. Hot standby configurations require duplicating the server hardware, synchronizing configuration, and implementing automatic failover - adding 70–100% to hardware cost and significant engineering time to implement and test correctly.
IT Maintenance Burden
A SCADA server requires ongoing IT maintenance: operating system patching (carefully coordinated to avoid SCADA application incompatibilities), antivirus management, backup verification, hardware health monitoring, and periodic hardware upgrades. For most oil and gas operators without an in-house IT department, this maintenance is either ignored (creating security and reliability risk) or outsourced at $150–$250/hour for qualified SCADA IT support.
Hardware Refresh Cycles
Industrial servers have a 5–7 year lifecycle before hardware failure rates increase significantly. A SCADA server refresh project involves new hardware procurement, operating system migration, SCADA application reinstallation and configuration verification, historian data migration, and end-to-end testing - typically 40–120 hours of engineering time. At 5–7 year intervals, hardware refresh adds $15,000–$50,000 to the true lifetime cost of an on-premise SCADA system.
Problems with On-Premise SCADA Servers
High Upfront Cost
The capital expenditure required for a proper on-premise SCADA server installation - hardware, software, implementation, and integration - typically runs $50,000–$300,000 before you see a single live data point from the field. This cost structure puts professional SCADA monitoring out of reach for small and mid-size operators who could benefit most from real-time visibility.
Requires IT Staff
Running an on-premise SCADA server is fundamentally an IT operations task. Without qualified IT staff to manage patching, backups, and hardware health, on-premise SCADA systems degrade over time - running outdated OS versions, accumulating configuration drift, and eventually failing at the worst possible moment. Oil and gas operators who hire for field expertise, not IT expertise, are poorly positioned to maintain on-premise SCADA infrastructure.
Single Point of Failure
A non-redundant SCADA server is a single point of failure for the entire monitoring system. When the server fails - due to hardware fault, software crash, or power loss - all visibility, alarms, and historian recording stops simultaneously. For operators relying on SCADA alarms for safety and production monitoring, a server failure is not just an IT problem - it is an operational emergency.
Physical Access Required
On-premise SCADA servers require physical access for hardware maintenance, operating system changes, and major SCADA application updates. This means someone with the appropriate IT skills must physically travel to the server location - often a field office or operations center - whenever significant maintenance is required. For operators in the Permian Basin, this may mean a multi-hour drive round trip for what amounts to an IT task.
Cybersecurity Vulnerabilities
The industrial SCADA world has a significant cybersecurity problem, and on-premise servers are at the center of it. SCADA servers frequently run outdated Windows versions (Windows Server 2008, 2012) because SCADA vendors certify their software against specific OS versions and are slow to certify new releases. These outdated servers often sit directly connected to both the control network (where PLCs live) and the corporate network (where internet access exists) - creating exactly the bridged architecture that attackers exploit. Cloud SCADA eliminates this exposure by moving the SCADA server entirely out of your network. See our security overview for how Merobix protects your data.
Cloud SCADA vs On-Premise Server
How Cloud Eliminates the Server
Cloud SCADA replaces the on-premise server with managed cloud infrastructure. A small gateway device at each field site - typically a cellular RTU or a software gateway running on an existing device - collects data from your PLCs and RTUs and transmits it to the cloud platform over an encrypted cellular or internet connection. All data collection, processing, storage, historian recording, alarm management, and user interface serving happens in the cloud. Your operators access everything through a browser or mobile app, with no server in the loop.
Where Data Is Stored
In the Merobix platform, all time-series data is stored in a purpose-built time-series database - a highly scalable cloud data store with enterprise-grade reliability, automatic replication, and multi-region redundancy. Configuration data is stored in a separate managed cloud database. Neither database requires any operator maintenance - backups, patches, scaling, and availability are handled by the platform.
How Reliability Is Achieved
Cloud SCADA reliability comes from the cloud infrastructure itself - data centers with redundant power, cooling, network connections, and hardware, maintained by teams dedicated to 99.9%+ availability. This is fundamentally different from a single server in a field office running on a single power feed. Merobix provides availability commitments set out in the applicable service agreement for the cloud platform, which exceeds the practical uptime of most on-premise SCADA servers when hardware failures, planned maintenance, and power events are counted honestly.
Cost Comparison
| Cost Category | On-Premise Server | Merobix Cloud |
|---|---|---|
| Hardware | $10,000–$50,000 | $0 |
| Software Licensing | $10,000–$50,000 | Included |
| Implementation | $30,000–$200,000 | Custom-quoted subscription |
| Annual Maintenance | $8,000–$30,000/yr | Included |
| IT Staff | Required | Not required |
| Hardware Refresh (5yr) | $10,000–$50,000 | $0 |
Security Comparison
Cloud SCADA is more secure than on-premise for most oil and gas operators. Merobix encrypts all data in transit (TLS 1.3) and at rest, enforces multi-factor authentication for user access, applies security patches continuously without requiring operator action, and does not expose any on-premise network infrastructure to internet-facing connections. On-premise SCADA servers often run unpatched, have inconsistent backup practices, and may be accessible from the internet through poorly configured VPN or RDP configurations. The security advantage of cloud SCADA is particularly significant for small operators without dedicated cybersecurity staff.
Do You Still Need a SCADA Server with Merobix?
No. Merobix's standard deployment is fully cloud-hosted. There is no server to purchase, configure, or maintain. The complete list of infrastructure you need to deploy Merobix:
- A cellular modem or existing RTU with cellular connectivity at each field site
- Internet-accessible browser or mobile device for your operators
- Existing field sensors and PLCs (or new instrumentation we can help you select and install)
All data storage, alarm processing, historian management, user authentication, report generation, and dashboard serving happens in Merobix cloud infrastructure with no on-premise server component. The availability commitments set out in the applicable service agreement cover the cloud platform; field connectivity (cellular) is not part of the platform SLA but is managed through gateway redundancy configuration options.
Migrating from SCADA Server to Cloud
What Stays the Same
When migrating from on-premise SCADA to Merobix, your field infrastructure stays unchanged. PLCs, RTUs, flow computers, sensors, and field wiring all remain exactly as they are. Your PLC programs are not modified. Your existing alarm setpoints from field RTU configuration carry over into Merobix. Your operators learn a new interface, but the underlying process data is the same data they were seeing before.
What Changes
The SCADA server is decommissioned. Local HMI workstations that accessed the on-premise SCADA system transition to browser-based or mobile access to the Merobix dashboard. Alarm notifications that previously required local acknowledgement at an operator workstation shift to SMS and email delivery to any phone or device. Historical data from the old system can be preserved in CSV export format, though it will not be imported into the Merobix historian.
How Long Migration Takes
For most oil and gas operators, the migration from on-premise SCADA to Merobix takes 1–2 weeks from contract to live data. This includes gateway device installation at field sites, protocol configuration to your existing RTUs, tag mapping, alarm setpoint configuration, user account setup, and dashboard customization. The migration timeline depends primarily on the number of field sites and the diversity of communication protocols in your existing installation.
Data Migration Process
Historical data from an on-premise SCADA historian can be exported to CSV or another portable format before the old system is decommissioned. Merobix does not import historical data from other platforms into its historian - the Merobix historian begins recording from the moment connectivity is established. Operators who require access to pre-migration historical data typically retain access to the old system (read-only) or export the historical data to a spreadsheet format for archiving. Regulatory records are preserved in the export format required by the applicable agency.
Related reading: See how cloud SCADA compares to on-premise SCADA across cost, security, and deployment speed. View our services for complete migration support.
Frequently Asked Questions
Do I need a server for SCADA?
With traditional on-premise SCADA software, yes - you need a dedicated server to run the SCADA application and historian database. With cloud SCADA platforms like Merobix, no server is required. All data collection, processing, storage, and visualization runs in the cloud. You only need cellular connectivity at each field site and a browser or mobile app to view your data.
How much does a SCADA server cost?
A SCADA server hardware purchase typically costs $5,000–$20,000 for an industrial-grade server with appropriate redundancy. Add $10,000–$50,000 for SCADA software licensing, $5,000–$15,000 for OS and database licensing, and $3,000–$8,000 per year for maintenance contracts. The fully loaded cost of a SCADA server infrastructure over 5 years is typically $50,000–$150,000, not including IT staff time.
Can I replace my SCADA server with cloud?
Yes. Merobix can replace an existing on-premise SCADA server for most oil and gas monitoring applications. The migration involves connecting your existing field RTUs or PLCs to the Merobix cloud platform via cellular or ethernet, configuring tag mapping, and verifying alarm setpoints. Existing control logic in field PLCs is not affected - Merobix monitors and reports without modifying your PLC programs. Most migrations complete within 1–2 weeks.
Is cloud SCADA more secure than on-premise server?
For most oil and gas operators, cloud SCADA is more secure than an on-premise server. On-premise SCADA servers are often running outdated Windows versions, lack regular security patching, and are connected to corporate networks without proper segmentation. Cloud SCADA platforms are maintained by dedicated security teams, receive continuous security updates, and implement encryption and access controls as a core product feature rather than an afterthought.
What is a SCADA server?
A SCADA server is a dedicated computer - typically an industrial-grade rack-mount or tower server - that runs the core SCADA software for an industrial monitoring system. It sits between field devices (PLCs, RTUs, flow computers) and operator workstations, handling data acquisition, historian storage, alarm processing, and HMI serving. In cloud SCADA architectures, these functions run in managed cloud infrastructure instead, eliminating the on-premise server entirely.
More in the Merobix Automation Fundamentals.
Sources and verification
This page references the standards, specifications, and official documentation published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
- Modbus Application Protocol Specification - Modbus Organization
Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Spotted something out of date or inaccurate? Please tell us through our corrections process and we will review it.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.