Every plant manager who has ever gotten a tag-count invoice from a legacy SCADA vendor has, at some point, heard about Ignition and asked why they’re still paying by the point. It’s a fair question. Inductive Automation built Ignition’s entire commercial model around the idea that charging by tag, client, or seat is the wrong way to price industrial software, and a lot of mid-market manufacturers have quietly agreed with them over the past decade. With Ignition 8.3 now in general release and plants working through 2026/2027 renewal cycles, it’s worth actually running the numbers instead of just repeating the “unlimited tags” pitch.
The short version: the licensing model is genuinely different, and for a lot of shops it’s genuinely cheaper. But “unlimited tags” doesn’t mean “unlimited cost,” and the places where money reappears — Sepasoft MES module fees, gateway redundancy, and integration labor — are exactly the line items that don’t show up in a vendor’s headline pricing slide.
What Ignition actually is, and what changed in 8.3
Ignition is a server-based SCADA/industrial application platform from Inductive Automation, licensed per-server (per “Gateway”) rather than per tag, per client, or per named user. A single Gateway license covers unlimited tags, unlimited screens, and — depending on module selection — unlimited Perspective web clients accessing the system from browsers or mobile devices. That’s the core pitch that’s made it a fixture in mid-market plants over the last several years: you buy the platform once per server, then add modules for the functionality you need.
Ignition 8.3 carries that model forward while modernizing the Perspective module (the web-based visualization layer that’s largely superseded the older Vision client for new projects) and refreshing how Sepasoft’s MES modules — OEE Downtime Tracker, Track & Trace, SPC, and the rest — integrate with the platform. Sepasoft is a separate, Ignition-native MES suite built by a different company on top of Inductive Automation’s platform, and its modules are licensed and priced independently of the core Ignition Gateway license. That distinction matters enormously for TCO modeling, and it’s the part that gets glossed over in a lot of “switch to Ignition and pay nothing per tag” conversations.
The traditional alternative: named-tag and seat licensing
Legacy SCADA and MES stacks — think the established named-tag SCADA platforms and the traditional MES suites that plants have run for two decades — typically price on some combination of tag count, client seat, and module. Add more I/O points, add more cost. Add a client workstation for a supervisor, add more cost. Add MES functionality like genealogy, scheduling, or OEE, and you’re often licensing a separate product with its own tag or transaction pricing on top of the SCADA layer underneath it. This is the model Ignition was explicitly designed to disrupt, and in high tag-count environments the math genuinely favors the unlimited approach.
The tradeoff is that traditional vendors have had decades to build out validated, prebuilt MES functionality, deep integration with specific automation ecosystems, and established professional services networks. That maturity has real value for plants that want a more turnkey path and are willing to pay for it in license and support fees rather than in-house integration hours.
Modeling TCO across 50, 200, and 1000 tags
Here’s where the comparison gets honest. At roughly 50 tags — a single line, a pilot cell, a small standalone machine — the licensing delta between models is often modest in absolute terms, and the deciding factor is usually which platform your integrator already knows, not raw license cost. Traditional named-tag pricing at this scale isn’t punishing yet.
At 200 tags — a typical single-line plant or a small multi-line facility — the gap starts to widen. Named-tag models start charging meaningfully more as you cross their pricing tiers, while an Ignition Gateway license stays flat regardless of whether you’re at 200 tags or 2,000. This is the range where “unlimited tags” starts to look like real savings rather than a marketing line.
At 1000+ tags across multiple lines, the per-tag model usually becomes the most expensive option by a wide margin, and it’s also where Ignition’s advantage is most visible on paper. But this is also exactly where the hidden costs show up hardest. A single-Gateway architecture serving a 1000-tag plant needs real redundancy planning — a warm or hot backup Gateway, proper licensing for failover, and someone who understands how Ignition’s redundancy actually behaves during a failover event rather than assuming it’s automatic and invisible. That’s infrastructure and configuration labor that a lot of initial cost comparisons simply don’t account for.
Where the “unlimited” savings actually go
The tag license isn’t where Ignition deployments end up spending money — it’s everywhere around it. Sepasoft’s MES modules are licensed and priced on their own schedule, separately from the Ignition Gateway, and a plant moving from SCADA-only to full SCADA-to-MES convergence needs to budget for those modules as a distinct line item, not assume MES functionality rides in for free because the tag count did. Redundant Gateway architecture — often treated as optional at the 50-tag pilot stage — becomes close to mandatory once a plant depends on Ignition for production visibility across a full facility, and that means a second server license, matched hardware, and a failover strategy that has to be built and tested, not just switched on.
The largest and least predictable line item is integration labor. Ignition’s flexibility is a genuine strength — it’s a true application platform, not a fixed-function SCADA package — but that flexibility means the prebuilt screens, workflows, and MES logic that a traditional vendor might ship out of the box often have to be built by an integrator or in-house team. For shops without existing Ignition expertise, that labor cost, spread across a 3–5 year TCO window, can rival or exceed what they saved on licensing. Traditional MES vendors bake more of that cost into the license and support contract up front; Ignition shops pay it later, in project hours.
Who this actually fits
In our assessment, Ignition’s model fits plants best when tag counts are high, growth is expected, and there’s either in-house SCADA/integration talent or a strong system-integrator relationship already in place. It also fits organizations doing multi-site rollouts, where a flat per-server model scales far better than paying per tag at every site. It may suit less well shops that want a fully validated, prebuilt MES experience out of the box with minimal internal configuration — regulated environments with heavy validation documentation requirements, for instance, where a traditional vendor’s established MES product and support apparatus may reduce risk even at a higher license cost.
The practical move for anyone mid-cycle on a renewal decision right now: build the 3–5 year model with four line items, not one — Gateway/module license, Sepasoft or MES module fees, redundancy hardware and licensing, and estimated integration hours — and price all four for both approaches before assuming the unlimited-tag number tells the whole story. It usually doesn’t, and the gap between “unlimited tags” and “unlimited cost” is exactly where budgets go sideways.
This article was written with the assistance of artificial intelligence. While we aim for accuracy, the information may be incomplete, out of date, or incorrect, and should be independently verified before you rely on it for any decision. It is provided for general information only and does not constitute professional advice.
