How Ignition's Unlimited Licensing Model Works
Updated
Ignition's licensing model is built around a single server license that removes the usual per-item limits: one Ignition server license includes an unlimited number of clients, tags, connections, and designers. That means you size the license to the server, not to how many screens, data points, or devices you add later. This model suits projects that expect to grow — more operators, more PLC connections, more tags — without returning to buy incremental capacity. It is less obviously a fit if your system will stay very small and static, since the value of "unlimited" comes from scale and change over time.
The core of the model
According to Inductive Automation's own description of Ignition, the licensing centers on the server:
- One Ignition server license is the unit of purchase.
- That license carries unlimited clients, tags, connections, and designers.
In practice, this inverts the licensing logic common in industrial software, where each of those dimensions is typically metered and priced separately. Here, the constraint you plan around is the server itself, not the count of things attached to it.
What each unlimited dimension means
| Dimension | What it covers | Why unlimited matters |
|---|---|---|
| Clients | Users or sessions connecting to the system | Adding operators or viewers doesn't trigger new license cost |
| Tags | Data points configured in the system | Tag-heavy projects don't hit a per-tag ceiling |
| Connections | Links to devices and data sources | Expanding to more PLCs or sources stays within the license |
| Designers | Development seats for building the application | More engineers can build without extra seats |
What you get from it
The stated benefit is that you can build the exact system you need, without limits. Concretely, that changes planning behavior:
- You don't have to forecast tag counts or client counts up front to avoid overage.
- Growth in users or data sources is an architecture decision, not a purchasing decision.
- Long-lived systems can expand incrementally without renegotiating license terms each time.
This is the main reason the model is associated with large-scale or long-horizon deployments: the cost of the license doesn't scale with the size of the deployment.
Where it fits — and where it may not
Good fit:
- Systems expected to grow in users, tags, or connected devices.
- Multi-site or enterprise rollouts where per-client or per-tag pricing would compound.
- Projects where the scope is still being discovered and you'd rather not cap it early.
Weaker fit:
- A small, fixed system that will never approach the limits — you'd be paying for headroom you don't use.
- Situations where the deciding factor is something other than client/tag/connection counts.
Checking the specifics before you decide
The unlimited dimensions above are the headline of the model, but the exact terms, editions, and any conditions attached to a given license are defined by Inductive Automation, not by this summary. Before committing, verify against the official sources:
- Ignition Pricing —
inductiveautomation.com/pricing/edition - Solution Suites —
inductiveautomation.com/pricing/solution-suites - Support Plans —
inductiveautomation.com/support/plans - Training Pricing —
inductiveautomation.com/pricing/training
The site also offers a free trial and a demo, which is the practical way to confirm how the licensing behaves for your specific architecture before purchase. Note that pricing figures, edition boundaries, and any login or trial conditions are not established here — check the linked pages directly, since those details change and are set by the vendor.
The short version
If your question is "will I have to pay more every time I add a client, tag, or connection?" — under Ignition's model as described, the answer is no: those are unlimited under one server license. The decision then comes down to whether your project's scale and expected growth make that structure worth it, and to confirming the current edition and pricing terms on Inductive Automation's own pages.