The license price on a SCADA quote is rarely more than a third of what you will actually spend over five years. Servers, integration engineering, support renewals, per-tag fees, upgrade projects, and downtime risk make up the rest — and they differ enormously between licensing models. This guide gives you a complete framework for comparing SCADA platforms by total cost of ownership, a cost-component comparison across the four major licensing models, and a 5-year TCO worksheet you can copy into a spreadsheet today.
SCADA total cost of ownership (TCO) is the sum of eight cost categories over the life of the system: software licensing or subscription, servers and infrastructure, integration and configuration engineering, add-on fees (per-tag, per-client, per-protocol), version upgrades, maintenance and support contracts, training, and downtime risk. On traditional platforms the software license itself is typically only a quarter to a third of the 5-year total — which is why comparing platforms on sticker price alone consistently picks the wrong winner.
To compare SCADA platforms by TCO, build the same 5-year cost model for every candidate: quote each platform at your actual tag count, user count, and site count, then add servers, integration, support renewals, upgrades, training, and downtime exposure. Never compare a perpetual license price to a subscription price directly — compare the 5-year totals, because that is the only point where the two models are measured in the same units.
Almost every SCADA platform on the market prices its software in one of four ways. Each model concentrates cost in a different place — which is exactly why sticker-price comparisons mislead.
The traditional model: a large upfront license purchase followed by an annual support and maintenance contract. A mid-size AVEVA deployment typically runs $30,000–$80,000 in upfront licenses plus $8,000–$20,000 per year in maintenance; FactoryTalk View pricing is commonly cited at $20,000–$60,000 depending on configuration; large enterprise deployments can exceed $200,000. Annual support renewals commonly cited at 15–20% of the license price mean you effectively re-buy the software every 5–7 years. The model's genuine advantage: the license is a capital asset with no ongoing subscription obligation, which some finance departments prefer. See our AVEVA alternatives guide for the full cost breakdown.
Inductive Automation publishes Ignition pricing publicly: roughly $10,800–$30,000 one-time per server depending on modules, with unlimited tags, clients, and connections on that server. This is a real strength and the best on-premise licensing value in the industry — for a single facility with in-house SCADA engineers, it is hard to beat on the software line. The TCO caveat is that the license is only one line: you still buy and maintain the servers, a redundant pair requires a second license, and multi-site architectures need either a gateway per site or reliable WAN links back to a central server. Our Merobix vs Ignition comparison works through the full 5-year math.
No upfront license, no servers, no support contract — one flat subscription that includes the software, hosting, historian, alarming, mobile access, upgrades, and support. Merobix pricing is custom-quoted for your operation, with no per-tag, per-client, or per-protocol fees; the only hardware is a $300–$800 gateway per site, and cloud deployments go live in 3–5 days. The trade-off to weigh honestly: you are paying a subscription indefinitely, so the model wins on TCO by deleting the infrastructure, maintenance, and upgrade lines — not by being free.
The newest model: subscription-priced software running on your own servers or VMs. Merobix offers the full platform on-premise — air-gapped compatible, with full data residency on your infrastructure — under the same flat, all-inclusive plan structure. You keep infrastructure control for policy or compliance reasons, while still avoiding perpetual-license upgrade projects and per-tag fees. For operators whose IT or regulatory posture rules out cloud, this model captures most of the SaaS TCO advantage; see the Merobix security page for the deployment details.
| Cost Component | Perpetual + Support | Server License (Ignition) | SaaS (Merobix Cloud) | On-Prem Subscription (Merobix) |
|---|---|---|---|---|
| Upfront software | $30K–$80K+ typical | $10.8K–$30K per server | $0 | $0 |
| Recurring software | Support at 15–20%/yr of license | Optional support plan | Flat subscription, custom-quoted | Flat subscription, custom-quoted |
| Server hardware | $15K–$50K per site | $15K–$50K per server site | None — $300–$800 gateway/site | Your existing servers/VMs |
| Per-tag / per-client fees | Common, varies by config | None — unlimited on server | None | None |
| Version upgrades | Paid projects + integrator time | Included with support plan | Automatic, included | Included in subscription |
| IT maintenance | $5K–$20K/yr per site | $5K–$20K/yr per site | Included | Your IT, reduced scope |
| Cost to add a site | New licenses + new server | New server or edge gateway | $300–$800 gateway only | No added software fees |
| Redundancy | Extra licenses + hardware | Second license + hardware | Cloud-managed, 99.9% SLA | Hot standby on Enterprise plan |
The fastest way to blow up a SCADA budget is a licensing model that meters growth. Three fee structures deserve special scrutiny, because each one converts normal operational expansion into a software invoice.
Per-tag fees charge for every data point you monitor. They look harmless at quote time — you scope 500 tags and the price is fine. Then you add flow computers, vibration sensors, and a new pad, and at 5,000 tags the annual software bill has grown tenfold while your operation grew fivefold. Per-tag models effectively tax instrumentation improvements: the better you monitor, the more you pay.
Per-client and per-seat fees charge for every operator screen, engineering workstation, or mobile user. The practical result is rationed visibility — operations managers decide who "deserves" a login instead of giving everyone who touches production a dashboard. When an on-call tech cannot check an alarm from a phone because the mobile add-on was not licensed, the fee trap has become an operational risk.
Per-protocol and per-driver fees charge separately for each PLC family you connect — one fee for Modbus, another for EtherNet/IP, another for DNP3. Mixed-vendor sites (an Allen-Bradley compressor next to a Modbus flow computer next to a DNP3 RTU) pay repeatedly for what should be table stakes. Merobix includes all 20 protocol drivers across 7 protocol families in every plan — the plan matrix shows exactly what each tier includes, and none of the tiers meter tags, clients, or protocols.
SaaS SCADA usually wins the 5-year TCO comparison for distributed operations, because it deletes entire cost categories rather than discounting them: no server hardware, no OS and database licensing, no backup infrastructure, no IT maintenance labor, and no version-upgrade projects. What remains is a predictable subscription plus gateway hardware — and predictability is itself worth money at budgeting time.
On-premise can still win in specific circumstances, and an honest TCO comparison admits them: a single large facility that already owns virtualization infrastructure and employs SCADA engineers can run a one-time Ignition license very economically; a plant with thousands of control loops and deep MES integration may justify AVEVA's cost structure. The pattern in the numbers is consistent: on-premise TCO scales with site count and IT labor, SaaS TCO scales gently with scope. For operations with more than 2–3 remote sites, the crossover typically arrives within the first 12–18 months. And if policy requires your data on your servers, an on-premise subscription captures most of the SaaS economics without the cloud — our cloud vs on-premise SCADA guide covers the architecture trade-offs in depth.
Copy this worksheet into a spreadsheet, create one column per candidate platform, and fill every line for each. The formula at the bottom is the only number that matters: 5-year TCO = one-time costs + (annual costs × 5) + upgrade projects + downtime expectation.
| Line Item | One-Time (Year 0) | Recurring (Per Year) | What to Ask the Vendor |
|---|---|---|---|
| Software license / subscription | Perpetual license price | Subscription or renewal | All-in quote at your exact tag, user, site counts |
| Support & maintenance contract | — | % of license or included | Renewal rate history for the last 5 years |
| Server hardware + OS/DB licenses | $15K–$50K per site (on-prem) | Refresh reserve | Exact server spec required, incl. redundant pair |
| Backup, UPS, virtualization | Site-dependent | Maintenance | What fails if the server room loses power? |
| Gateway / comms hardware | $300–$800 per site (cloud) | Cellular data plan | Who configures and supports the gateway? |
| Integration & configuration | Integrator or vendor hours | Change requests | Fixed-price deployment or time & materials? |
| Protocol drivers / connectors | Per driver on some platforms | Per driver on some platforms | Are all my protocol families included? |
| Client / mobile access | Per seat on some platforms | Per seat on some platforms | What does user #20 cost? User #50? |
| Redundancy / hot standby | Second license + hardware | Maintenance | Is failover licensed, and who tests it? |
| Training | Initial operator training | Retraining after upgrades | Is training included or billed per class? |
| Version upgrade projects | — | Amortized project cost | What did the last major upgrade cost customers? |
| Downtime risk | — | Outage hours × cost/hour | Uptime SLA in writing? Alert delivery time? |
Two of these lines deserve extra attention because vendors never volunteer them. First, upgrade projects: ask reference customers what their last major version migration actually cost in integrator hours and downtime — on legacy platforms this line alone can rival the original license. Second, downtime risk: a platform that delivers SMS and email alerts in under 30 seconds with a 99.9% uptime SLA has a structurally smaller downtime line than one where alerting is an add-on module on a single unpatched server. If you are replacing a legacy system, our SCADA migration guide shows how to keep the transition itself off this worksheet.
TCO shortcut: Two questions expose most of a platform's 5-year cost curve: "What does this exact system cost at double the tags and double the sites?" and "What is annual, and what has the renewal increase been historically?" Then run your own numbers through the Merobix ROI calculator — it compares your current monitoring costs against a flat, all-inclusive plan — or request a guided demo and ask us the same two questions. We like our answers.
Merobix competes on total cost of ownership by deleting line items rather than discounting them. There is no upfront license, no server purchase for cloud deployments, no per-tag, per-client, or per-protocol fees, no paid upgrade projects, and no separate support contract — every plan is flat and all-inclusive, custom-quoted for your operation. Cloud deployments go live in 3–5 days, alerts reach your phone in under 30 seconds, and the platform carries a 99.9% uptime SLA. For operators who need data residency, the same plans run on-premise on your servers or VMs, air-gapped compatible. The why-Merobix page walks through the comparison, and the Enterprise tier folds in what elsewhere shows up as separate invoices: hot standby redundancy, LDAP/SAML single sign-on, SIEM integration, and connectors for SAP, Maximo, ServiceNow, and PagerDuty.
To be fair to the alternatives: a single plant with existing servers and in-house engineers can run Ignition's one-time license very cost-effectively, and enterprises with deep MES and batch requirements may rationally choose AVEVA despite the cost structure. Merobix wins the TCO comparison most decisively where operations are distributed, IT resources are thin, and growth would otherwise trigger per-something fees — which describes most oil and gas, water, and remote industrial operations we serve. For the broader spend picture, our oil and gas automation cost guide puts SCADA TCO in the context of the full automation budget.
Compare SCADA platforms by building the same 5-year cost model for every candidate: software license or subscription, annual support contracts, server hardware and IT maintenance, integration and configuration engineering, per-tag or per-client add-on fees, version upgrades, training, and downtime risk. Request written quotes at your actual tag count, site count, and user count — then again at double those numbers to expose how each licensing model scales. The platform with the lowest sticker price is frequently not the one with the lowest 5-year total once servers, integrators, and support renewals are counted.
SCADA license prices vary by licensing model. Ignition publicly lists server-based licensing at roughly $10,800–$30,000 one-time per server depending on modules, with unlimited tags and clients. A mid-size AVEVA deployment typically runs $30,000–$80,000 in upfront licenses plus $8,000–$20,000 per year in support, and large enterprise deployments can exceed $200,000. Cloud platforms like Merobix replace the license with a flat subscription — custom-quoted for your operation, all features included, with no per-tag, per-client, or per-protocol fees.
A complete SCADA system costs far more than the software license. An on-premise deployment typically adds $15,000–$50,000 per site in server hardware and software, $5,000–$20,000 per year per site in IT maintenance, plus integration engineering, training, and periodic upgrade projects — a 10-site on-premise operation can exceed $500,000 over five years. A cloud deployment replaces most of those lines with a flat subscription (custom-quoted for Merobix) plus one-time gateway hardware of $300–$800 per site, so total system cost depends more on architecture than on any single line item.
For most distributed operations, yes. SaaS SCADA eliminates the largest on-premise TCO lines — server hardware, OS and database licenses, IT maintenance labor, backups, and version-upgrade projects — leaving a predictable subscription plus $300–$800 gateway hardware per site. On-premise can still win for a single large facility with existing servers, in-house SCADA engineers, and a one-time server license like Ignition's. The economics tilt toward SaaS as site count grows: for operations with more than 2–3 remote sites, SaaS is typically cheaper within the first 12–18 months.
The most common hidden fees are per-tag charges that grow as you add monitoring points, per-client or per-seat fees for each operator screen and mobile user, per-protocol driver fees for each PLC family you connect, historian capacity tiers, redundancy licenses, and annual support renewals commonly cited at 15–20% of the original license price. Individually each looks small; together they can double a platform's effective price over five years. Ask every vendor for a written all-in quote at your real tag, user, and site counts. Merobix plans are flat and all-inclusive — no per-tag, per-client, or per-protocol fees.
One flat, all-inclusive plan — custom-quoted for your operation, with no per-tag, per-client, or per-protocol fees.