SCADA licensing models in 2026 cluster into two economic shapes: per-server unlimited (Ignition by Inductive Automation, one server license with unlimited tags, clients, connections, and designers) and per-tag or per-seat tiers (VTScada, AVEVA Plant SCADA, Wonderware), where each additional 1,000 tags or runtime seat moves the quote [S1][S2][S8].
Process engineers running plants above roughly 5,000 I/O points, or any site where the tag list grows after commissioning, will find per-tag pricing punitive. Per-server unlimited decouples software cost from I/O count, while hardware (server class, redundancy pair) becomes the real scaling constraint [S1].
Per-server unlimited: what $3,280 actually buys
Ignition's per-server model is sold as one license per gateway/server with no cap on tags, clients, screens, designer seats, or device connections, with a published starting price of $3,280 for a single-server entry configuration [S7]. Independent comparisons cite roughly $500 per additional server license once the first is in place, and a fully-loaded 100-tag, 1-client Ignition + Tag Historian bundle has been priced at $21,460 including unlimited clients [S3][S4].
Critically, the unlimited model covers OPC UA and SQL bridges, MQTT publish/subscribe, and unlimited concurrent designer seats, so a four-person integrator team can develop on the same project without per-seat fees, which is where conventional SCADA stacks accumulate line items [S1][S2]. Performance is bounded only by the host hardware: tag count, scan class rate, and historian depth all push CPU and RAM; a saturated gateway is a configuration problem, not a licensing problem [S1].
Per-tag and per-seat tiering: VTScada, AVEVA, Wonderware
VTScada is licensed per seat: each PC, laptop, or panel PC running the application needs at least one Runtime or Development Runtime license, with separate line items for development environments versus operator HMI seats [S8]. A 100,000-tag AVEVA Plant SCADA deployment is commonly quoted in five-figure increments per 1,000-tag tier, and the same vendor's list separates 10,000-tag, 100,000-tag, and unlimited-tag SKUs as distinct commercial products [S6].
For small fixed-scope jobs, per-tag pricing can look attractive on the front page of the quote: 500 tags, 2 clients, single server, no growth expected, and the total cost of ownership stays predictable. The downside is structural: every PLC added during a phase-2 expansion reopens the license negotiation, and integrator-side effort to model tag counts into a quote is non-trivial compared to a flat per-server number [S4][S6].
Decision matrix: four criteria, two camps
Compare the two models on (1) tag-count sensitivity, (2) client/designer seat scaling, (3) multi-site roll-out cost, and (4) integrator development overhead. Per-server unlimited wins decisively on (1) and (2): no marginal cost per 1,000 tags, and no per-client runtime fees regardless of operator panel count [S1][S2]. Per-tag tiers win on (3) only when the site count is one and the tag count is small enough that a single-server unlimited license is harder to amortize than the entry tier.
On (4), per-server unlimited reduces integrator quoting effort: one server, named clearly, covers the whole scope. Per-tag tiers force the integrator to maintain a tag database throughout the project lifecycle and reconcile it against the license entitlement at every change order [S4].
Where the unlimited model still hurts
Per-server unlimited is not free. The $3,280 starting price assumes a single-server deployment and entry-tier modules; redundant gateway pairs, the Tag Historian module, and the Perspective web client module each carry their own line item, and the published historian module is roughly $2,365 as an add-on [S4][S7]. For a one-line machine with 200 tags and two HMI panels, the per-server minimum can cost more than a 500-tag per-seat tier, so the break-even is real, not theoretical.
Operationally, an "unlimited" gateway that is undersized for the scan class load becomes a bottleneck. Independent commentary notes that a server can be overloaded if pushed too hard, and that architects should plan for horizontal scale-out across multiple servers rather than expecting one box to absorb an entire plant's worth of 100 ms polling [S1]. The unlimited in "unlimited tags" refers to licensing, not to throughput.
Use cases: who each model is FOR
It is also the right call for system integrators who want developers, not just runtime operators, to be able to log into the same project without license juggling [S2][S7].
Per-tag tiering is the right call for: skid-mounted OEM machines with a fixed I/O list and a single operator panel, regulated batch processes where the validated tag count must not change, and brownfield retrofits where the incumbent SCADA license is already paid up and the migration cost dominates the variable cost. For a 300-tag machine HMI, the simpler compliance story of a fixed tier can outweigh the per-tag premium [S6][S8].
Standards, sourcing, and what to verify in the quote
Neither licensing model is governed by a specific IEC/ISA standard; the constraints that matter sit in the cyber-security and historian layers (ISA/IEC 62443 zones for the gateway host, and the customer's own data-retention policy for the historian module). The verifiable items in any quote are: the number of server licenses, the modules included (Tag Historian, Perspective, OPC UA, MQTT, Alarming), whether redundant gateways are priced separately, and whether the third-party historian add-on is bound by tag count or by server count [S1][S4].
For a $/tag comparison, ask each vendor for a written quote at three tag counts (1,000, 10,000, 100,000) and the same three client counts (2, 10, 50). The vendor that refuses to break out a per-server line item, or that refuses to publish a public starting price, is the vendor whose TCO will drift the most over a 5-year horizon [S3][S7].
What to track next
Two signals worth watching through Q4 2026: whether AVEVA publishes a unified unlimited-tag SKU for Plant SCADA at the entry tier, and whether VTScada introduces a per-site unlimited option for its integrator channel. Both would compress the per-tag tier's remaining advantage in the small-machine segment and tilt default procurement toward per-server licensing for new builds above ~2,000 tags. [S2]
For a related cost-shape comparison outside SCADA, the FRP pultruded cost breakdown in this per-ton vs per-shape pricing analysis uses the same per-unit-vs-flat-fee decision logic, and the motor-protection relay decision guide walks through a parallel per-point licensing question at the protection-relay layer.
Component reference pages worth checking: hmi scada, scada software, and pressure transmitter.