Two SCADA quotes for the same 20-site operation can differ by a factor of ten — not because the software is ten times better, but because the licensing models are built differently. Per-tag, per-client, per-server, perpetual-plus-support, SaaS subscription, OEM runtime: each model rewards a different kind of buyer and quietly punishes the rest. This guide explains how every model works, which hidden fees to check before you sign, and which structures actually scale as your operation grows.
Every SCADA quote you will ever receive is built on one of six licensing models — or, more often, a combination of two or three. Understanding the model behind the quote matters more than the sticker price, because the model determines what happens to your cost when you add a site, hire an operator, double your tag count, or build a redundant server. The table below summarizes all six; the sections that follow explain each one and where it wins or fails.
| Model | How You Pay | Typical Platforms | Scales Best For | Watch Out For |
|---|---|---|---|---|
| Per-tag | Price tiers by monitored point count | VTScada, OSIsoft PI (historian) | Small, stable point counts | Tier jumps; historian tags counted separately |
| Per-client / per-seat | Each workstation or concurrent user licensed | FactoryTalk View, WinCC, iFIX | Few operators, one control room | Client audits; mobile and web users may count |
| Per-server unlimited | One price per server, unlimited tags and clients | Ignition | Single busy facilities | Redundancy needs a second license; one license per site |
| Perpetual + support | Large upfront license + 18–22%/yr support | AVEVA, FactoryTalk | Long-lived, static systems | Upgrade repurchases; support-lapse penalties |
| SaaS subscription | Flat recurring fee: software, hosting, updates | Merobix, other cloud SCADA | Multi-site, growing operations | Verify what is bundled vs. sold as add-ons |
| OEM / embedded | Volume runtime licenses resold with machines | Vendor OEM programs | Machine builders shipping many units | Royalty terms; end-user upgrade path |
Per-tag licensing prices the software by the number of data points (tags) the system monitors, usually in tiers — for example 500, 2,500, 25,000, or unlimited tags. It looks cheap at the entry tier, and for a small pump station monitoring 80 points it genuinely is. The problem is tier jumps: crossing from one tier to the next can double the license cost overnight, and modern instrumentation grows tag counts fast. A single VFD can expose 50+ readable parameters; a 30-well field at 40 tags per well is already 1,200 tags. Ask whether calculated tags, historian tags, and alarm tags count against the tier — on some platforms they all do.
Per-client licensing charges for each operator workstation or concurrent user session, on top of the server license. This model dates from the era when a SCADA system had two or three dedicated control-room consoles, and it still works acceptably in that setting. It works badly for modern distributed operations, where a pumper, two supervisors, an on-call engineer, and an operations manager all want dashboard access from trucks and phones. Every one of those sessions can be a billable client, and vendors commonly reserve the right to audit client counts at renewal — the true-up invoice that follows is an unpleasant surprise.
Per-server unlimited licensing — the model Inductive Automation made famous with Ignition — charges one price per server and includes unlimited tags, unlimited clients, and unlimited designer seats on that server. For a single large facility with many screens and many operators, it is a genuinely liberating model, and its publicly listed pricing removed a great deal of quoting friction from the industry. The costs it does not remove: each site or server instance needs its own license, a redundant backup server requires its own license, and you still own the hardware, operating system, patching, and backup burden for every server you deploy. See our full Merobix vs Ignition comparison for a head-to-head breakdown.
The classic enterprise model, used by AVEVA (Wonderware), FactoryTalk, and most legacy platforms: a large upfront perpetual license — commonly tiered by tags, clients, and options — plus an annual support and maintenance contract typically priced at 18–22% of the license value. Over a 5-year life, the support stream alone often equals the original license. The traps are well known: major version upgrades are sometimes treated as new purchases, letting the support contract lapse can trigger reinstatement penalties, and options you assumed were included (historian, web clients, redundancy) are frequently separate line items. Budget the full stack, not the headline license.
SaaS subscription licensing replaces upfront licenses, servers, and support contracts with a single recurring fee that covers the software, the hosting infrastructure, updates, and support. There are no version upgrades to buy because the platform is continuously updated, and no server hardware to depreciate. This is the model Merobix uses: flat all-inclusive Starter, Professional, and Enterprise plans with no per-tag, per-client, or per-protocol fees — and it is also available on-premise for operators who need the software running on their own servers or air-gapped networks (see cloud vs on-premise SCADA). The evaluation question for any SaaS platform is bundling: confirm exactly which features, protocols, and user counts the subscription includes, so the flat fee is actually flat.
OEM licensing is designed for machine builders, skid packagers, and panel shops that ship SCADA or HMI runtime as part of their product. Instead of the end user buying a license, the OEM buys volume runtime licenses at a discount and resells them embedded in the equipment. Several major vendors operate published OEM programs. The economics hinge on three contract terms: the per-unit runtime cost at your volume, who owns the end-user relationship when the customer wants changes or upgrades, and whether the embedded license can be expanded later without repurchasing.
Ignition licenses by the server rather than by tag or client: one server license includes unlimited tags, clients, and designers, with publicly listed pricing. Compared with the per-client model of FactoryTalk View or the tag-tier model of platforms like VTScada, that is dramatically simpler and usually cheaper for a single busy facility — it is the main reason Ignition became the integrator favorite of the last decade.
The comparison shifts for distributed operations. Because the license is per server, a 15-site operation architected with a gateway at each site carries 15 licenses — and if any of those servers needs hot-standby redundancy, the backup server carries its own license too. Ignition remains self-hosted either way: you supply and maintain the server hardware, OS, patching, and backups at every location. Against perpetual-plus-support platforms, Ignition generally wins on transparency and total cost. Against flat SaaS platforms like Merobix, the trade is different: Merobix bundles hosting, redundancy, updates, and support into one custom-quoted subscription with no server licenses at all, which typically favors multi-site operators — while Ignition's unlimited scripting and on-premise depth favor complex single facilities with in-house SCADA engineering.
The two most growth-flexible structures are per-server unlimited licensing and flat SaaS subscription; per-tag and per-client models are the least flexible because every expansion — more points, more people — triggers a licensing event. If your five-year plan involves adding sites, adding instrumentation, or giving more staff dashboard access, the licensing model matters more than the year-one price.
Within the flexible pair, the growth axis differs. Per-server unlimited flexes on density: on an existing Ignition server you can add tags and clients freely, but each new site or redundant server is a new license. Flat SaaS flexes on footprint: on Merobix, adding a site means shipping a $300–$800 gateway and configuring tags — the subscription does not change, no matter how many sites, users, or protocols you add. All 20 protocol drivers across 7 protocol families are included in every plan, so connecting a new vendor's hardware never triggers a driver purchase. A new cloud deployment is typically live in 3–5 days. For a full picture of how that changes multi-site economics, see our multi-site SCADA guide and run your own numbers in the ROI calculator.
For OEMs and packagers, the most cost-effective structure is usually volume runtime licensing with published tiers — or, increasingly, a subscription arrangement where monitoring is quoted as a predictable per-deployment line item instead of an embedded license. The right choice depends on whether your customers expect to own the software outright or expect monitoring as a service alongside the equipment.
Evaluate any OEM licensing offer on four terms: the per-unit runtime cost at your realistic annual volume, the royalty or discount schedule as volume grows, who supports the end user after commissioning, and the upgrade path when an end user outgrows the embedded runtime. A cheap embedded license that strands your customer at 500 tags creates a support problem you will own. Merobix works with machine builders and panel shops directly — we fabricate UL 508A panels and program Siemens and Allen-Bradley PLCs in-house — and because Merobix platform pricing is custom-quoted, a packager can get a bundled quote that covers the panel, the PLC program, and flat-rate monitoring for the end customer in one line item. Our SCADA-as-a-Service guide covers this delivery model in depth.
Most SCADA budget overruns are not caused by the headline license price — they are caused by line items that never appeared in the first quote. Put these eight questions to every vendor in writing:
The practical alternatives to a traditional bundled license-plus-support quote are per-server unlimited licensing, flat SaaS subscription, and — for teams with serious engineering capacity — assembling an open-source stack. Each unbundles a different part of the traditional quote.
Per-server unlimited unbundles the tag and client counts: you stop paying for density and pay only for server instances. Flat SaaS unbundles the most: the subscription replaces the license, the support contract, the redundancy license, the server hardware, and the IT maintenance labor in one fee. Open-source stacks (an OPC UA collector, a time-series database, a dashboard layer) carry zero license cost but shift the entire integration, hardening, alerting, and maintenance burden onto your team — a real cost that usually exceeds a commercial subscription for any operation without dedicated developers. Merobix sits deliberately at the flat-SaaS end: one custom-quoted plan covers the platform, all protocol drivers, sub-30-second SMS and email alerting, hosting with a 99.9% uptime SLA (or an on-premise install on your own VMs), and support — the structure is explained on our Why Merobix page, and the security architecture behind it on the security page.
Fastest way to compare quotes: Force every vendor onto the same denominator — the all-in 5-year cost for your real site count, tag count, user count, and redundancy requirement, in writing. Per-tag and per-client quotes shrink when scoped small and balloon at real-world scale; flat quotes stay flat. The Merobix plan matrix shows exactly what each plan includes, and a guided demo gets you a custom quote scoped to your operation.
Published SCADA license prices span from a few thousand dollars for an entry per-server or per-client package to well past $100,000 for enterprise perpetual deployments with redundancy and full options. A fully unlimited Ignition server is publicly listed in the low five figures; AVEVA and FactoryTalk projects commonly start around $40,000–$50,000 once tiers, clients, support, and integration are included; and annual support on perpetual licenses typically runs 18–22% of license value, every year.
| Cost Item | Perpetual + Support | Per-Server Unlimited | Merobix Flat SaaS |
|---|---|---|---|
| Upfront license | $10K–$100K+ by tier | Low five figures per server | None — subscription only |
| Annual support | 18–22% of license/yr | Optional care plan | Included |
| Redundant server | Second license | Second license | Hot standby included (Enterprise) |
| Adding 500 tags | Possible tier jump | Included | Included — no per-tag fees |
| Adding a client/user | Per-seat fee (typical) | Included | Included — no per-client fees |
| Protocol drivers | Often per driver | Module-based | All 20 drivers included |
| Servers & IT labor | Yours to buy and maintain | Yours to buy and maintain | Cloud-hosted, or your VMs on-premise |
| New site | New license stack | New server license | $300–$800 gateway, one-time |
Merobix does not publish per-unit prices because there are no per-unit prices to publish: plans are custom-quoted as a flat all-inclusive subscription for your operation — every tag, every user, every protocol, every alert included, cloud-hosted or on your own servers. The only per-site cost is one-time gateway hardware at $300–$800. Request a demo and you will have a scoped quote instead of a price sheet — and a cloud deployment can be live in 3–5 days.
There are six main SCADA licensing models: per-tag (price tiers based on the number of monitored data points), per-client or per-seat (each operator workstation or concurrent user is licensed), per-server unlimited (one price per server with unlimited tags and clients, the model Ignition uses), perpetual license plus annual support (a large upfront purchase plus a yearly support contract, common with AVEVA and FactoryTalk), SaaS subscription (a flat recurring fee covering software, hosting, and updates, the model Merobix uses), and OEM or embedded licensing (volume runtime licenses resold by machine builders). Most traditional vendors combine two or more of these in a single quote.
Ignition licenses by the server rather than by tag or client: one server license includes unlimited tags, clients, and designers, with publicly listed pricing. That is simpler than the per-client model used by FactoryTalk View or the tag-tier model used by platforms like VTScada, and it is a major reason Ignition is popular with integrators. Costs still scale with server count, however — each site typically needs its own gateway license, and a redundant backup server requires its own license. Flat SaaS platforms like Merobix differ by bundling hosting, redundancy, and updates into one subscription with no server licenses to buy.
Published SCADA license prices vary enormously by model. Traditional per-server or per-client packages commonly start in the low thousands of dollars per server or seat and climb with tag tiers, while a fully unlimited Ignition server is publicly listed in the low five figures, and enterprise platforms like AVEVA commonly reach $50,000 or more once support and integration are included. Annual support contracts typically add 18–22% of the license price every year. Merobix pricing is custom-quoted: a flat all-inclusive subscription with no per-tag, per-client, or per-protocol fees, plus one-time gateway hardware of $300–$800 per site.
The most growth-flexible licensing structures are per-server unlimited and flat SaaS subscription. Per-server unlimited platforms like Ignition let you add tags and operator clients on an existing server at no additional license cost, though each new site or redundant server adds a license. Flat SaaS platforms like Merobix let you add sites, tags, users, and protocols without changing the subscription — new sites need only $300–$800 in one-time gateway hardware. Per-tag and per-client models are the least flexible because every expansion of monitoring density or staffing triggers a licensing event and often a re-quote.
On most traditionally licensed platforms, yes. A hot-standby or redundant backup server is typically treated as a second installation and requires its own license, commonly at full price or a published redundancy price — effectively doubling the software cost of a high-availability deployment. This is one of the most frequently missed line items in SCADA budgets, so ask every vendor directly how redundancy is licensed. With Merobix, hot standby redundancy is included in the Enterprise plan rather than sold as a second license, and cloud deployments include the 99.9% uptime SLA without extra redundancy licensing.
No per-tag fees, no per-client fees, no redundancy licenses — a custom-quoted subscription that covers your whole operation, cloud or on-premise.