Ignition vs Wonderware (AVEVA): SCADA Platform Comparison for 2026
Ignition vs Wonderware/AVEVA compared — licensing model, architecture, historian, HMI, and PLC connectivity — to help controls engineers choose a SCADA platform.
Quick Answer
Ignition (Inductive Automation) uses a flat, server-based licensing model with no per-tag or per-client fees, runs on any OS with a Java runtime, and deploys HMI clients via a web browser. Wonderware — now AVEVA InTouch — is a Windows-native platform with a per-tag and per-client pricing structure, a deep integration with the ArchestrA/System Platform object model, and a 30-year installed base in process industries.
For a new greenfield project with a mixed PLC fleet, budget certainty requirements, or a small integration team, Ignition typically wins on total cost of ownership and deployment flexibility. For brownfield expansions of an existing AVEVA System Platform estate, or sites that have standardized on the OSIsoft PI ecosystem, staying within the AVEVA stack usually makes more business sense than a rip-and-replace.
The comparison below goes deeper on every dimension that matters when you are writing a SCADA specification or defending a platform choice to management.
At a Glance: Ignition vs AVEVA InTouch
| Factor | Ignition (Inductive Automation) | AVEVA InTouch (formerly Wonderware) |
|---|---|---|
| Licensing model | Per-server (unlimited tags, unlimited clients) | Per-tag tier + per-client (quote-only) |
| Price transparency | Published list pricing, try-before-buy | Quote-only; no public pricing |
| OS support | Windows, Linux, macOS, Docker | Windows only (server and client) |
| HMI delivery | Browser-based (Perspective) or Java-based (Vision) | Windows thick client; limited web options |
| Historian | Built-in SQL-backed historian | Separate AVEVA Historian product required |
| PLC drivers | Native Allen-Bradley, Siemens, Modbus, OPC UA, 300+ devices | OI Servers / DAServers (licensed separately) |
| Scripting | Python (Jython) | QuickScript NG (VB-like) |
| Sparkplug B / MQTT | Native, built-in broker | Third-party integration required |
| Development IDE | Ignition Designer (free, web-launched) | InTouch WindowMaker / Archestra IDE |
| Free trial | Ignition Maker Edition (non-commercial, fully featured) | Trial available with partner registration |
| Primary strength | Flexible deployment, cost-at-scale, IT/OT convergence | Deep process object model, large installed base |
Introduction
When a controls engineer starts specifying a SCADA platform, "Ignition vs Wonderware" is one of the first comparisons that surfaces — even though Wonderware was formally renamed to AVEVA InTouch HMI in 2020. The legacy brand is still the mental shorthand for a whole category of Windows-native, per-tag licensed HMI/SCADA software that dominated plant floors for three decades.
This comparison focuses on what actually differentiates the two platforms from the perspective of a PLC programmer or controls engineer who will live with the platform every day: how it connects to the PLC, how the licensing math works at scale, what the development experience looks like, and what a migration really costs if you need to move between them.
For a broader overview of the AVEVA rebrand timeline and product name mapping, see the Wonderware / AVEVA name guide. For context on where both platforms sit in the full SCADA market, the best SCADA software 2026 review covers 10 platforms side by side.
Licensing and Cost Model
This is the most consequential difference between the two platforms, and it compounds in a way that catches engineers off guard the first time they spec out a mid-to-large project.
Ignition: Server-based, unlimited everything
Inductive Automation publishes its pricing. The base Ignition gateway license covers unlimited tags, unlimited clients, and unlimited historical data storage on a single server. Additional modules — Perspective (browser HMI), Reporting, SQL Bridge, MQTT Engine, Alarm Notification — are licensed per-module per-server, not per-tag or per-seat.
This means a 1,000-tag project and a 100,000-tag project on the same server pay the same gateway fee. Add a second server for redundancy or geographic distribution and you pay a second gateway license — that is the only scale variable in the licensing equation.
For non-commercial use, Ignition Maker Edition is free and fully featured. For evaluation, the commercial edition runs for two hours in trial mode before requiring a license, and the trial resets on demand — meaning you can develop an entire application before committing to a purchase.
AVEVA InTouch: Per-tag, per-client, quote-only
AVEVA does not publish list pricing. Licensing for InTouch HMI is structured around tag count tiers and concurrent client connections, with additional licensing required for the Historian, for System Platform (the object-based supervision layer above InTouch), and for each OI Server or DAServer driver package.
Exact figures depend on territory, reseller, and volume — quoting AVEVA pricing here would mean fabricating numbers. What is consistent across third-party integrator accounts and public procurement records is that the per-tag model means costs scale with project size in a way that Ignition's model does not. Projects above roughly 10,000 tags frequently find that Ignition's total licensing cost is substantially lower, and the gap widens with tag count.
Cost-at-scale worked example
To illustrate the structural difference without fabricating specific prices, consider a hypothetical mid-size project:
- Scope: 5,000 I/O tags, 25 concurrent operator clients, 3 years of historian retention
- Ignition: One gateway license + Perspective module + Historian module. Tag count and client count do not add to the license cost. A redundant standby server doubles the server-side cost but does not change the tag or client bill.
- AVEVA InTouch: A 5,000-tag tier license + 25 client seats + AVEVA Historian license + OI Server licenses for each PLC family on the network. The four line items compound. Redundancy adds a second node at the server tier but the tag and client licenses are typically shared (verify this with your reseller for your specific contract).
The AVEVA System Platform (formerly Wonderware System Platform) adds a further license layer for the object model and galaxy repository — this is the product that unlocks true cross-site object inheritance and the ArchestrA automation objects that give AVEVA its strong position in large-scale, multi-site process plants. If you need that capability, the cost is the cost. If your project does not need enterprise-scale object hierarchies, you are paying for architecture you will not use.
Architecture
Ignition: Cross-platform, web-first, gateway-centric
Ignition's architecture is built around a central Gateway — a Java application that runs on Windows, Linux, or macOS and exposes a web interface for administration, development, and client delivery. Every Ignition client, including the development Designer, is downloaded and launched from the Gateway via a web browser. There is nothing to install on an operator workstation beyond a browser for Perspective clients, or a Java runtime for legacy Vision clients.
The Gateway manages all OPC connections, the historian, alarm state, scripting execution, and user authentication. In a redundant configuration, a standby Gateway takes over automatically if the primary fails, with clients reconnecting transparently.
This architecture makes Ignition well-suited for:
- Thin-client deployments where operator PCs cannot have software installed
- Remote access and multi-site architectures (browser + VPN or Ignition Cloud Edition)
- Linux-based industrial servers and containerized (Docker) deployments
- IT/OT convergence projects where the SCADA server sits in a virtualized data center
AVEVA InTouch: Windows-native, ArchestrA object model
AVEVA InTouch runs on Windows. The development environment (WindowMaker), the runtime (WindowViewer), and the Historian are all Windows applications. The System Platform layer adds a Galaxy Repository — a centralized object store running on a dedicated Windows server — that manages application objects, templates, and deployment across multiple InTouch nodes.
The ArchestrA object model is a genuine architectural differentiator. It lets engineers define an equipment template once (a pump, a reactor, a PID loop) and instantiate it hundreds of times across a plant, with changes to the template propagating to all instances. For complex process plants with thousands of similar equipment items, this approach reduces engineering time and standardizes alarming, trending, and faceplates in a way that Ignition's tag-based model handles differently (through tag groups, named queries, and Perspective component inheritance rather than a formal object hierarchy).
For a single-site discrete manufacturing or water/wastewater application, the ArchestrA layer is often over-engineered. For a multi-site chemical or oil-and-gas operation where the same P&ID appears at 20 plants, the object model pays for itself.
PLC Connectivity: The Controls Engineer's View
How each platform talks to the PLC is where the day-to-day experience diverges most sharply for a controls engineer.
Ignition: Native drivers, OPC UA server built-in
Ignition ships with native device drivers for the most common PLC families in a standard installation:
- Allen-Bradley / Rockwell: EtherNet/IP (ControlLogix, CompactLogix, MicroLogix, PLC-5, SLC-500) — connects directly to the PLC without a third-party OPC server
- Siemens: S7-300/400 (ISO-on-TCP) and S7-1200/1500 (via OPC UA or the native S7 driver)
- Modbus TCP/RTU: Generic Modbus for any compatible device
- MQTT/Sparkplug B: Native MQTT Engine module for publish-subscribe architectures
- OPC UA: Built-in OPC UA client (connect to any OPC UA server) and OPC UA server (expose Ignition tags to other OPC UA clients)
- DNP3 and IEC 61850: Available via third-party modules for utilities
For Allen-Bradley systems specifically, Ignition can import tag definitions directly from a Studio 5000 .ACD or .L5X export file — a massive time saver on projects with hundreds or thousands of tags already engineered in the PLC program. You map the exported tag database into Ignition rather than retyping every tag by hand.
Ignition also functions as an OPC UA server, meaning other systems — historians, MES platforms, cloud connectors — can subscribe to Ignition tag data over the standard OPC UA protocol without any additional middleware.
AVEVA InTouch: OI Servers and DAServers
AVEVA's connectivity architecture separates the SCADA layer from the device layer via OI Servers (Object Interface Servers) and the older DAServers (Direct Access Servers). These are separate software components — often licensed separately — that act as the protocol translators between the PLC network and the InTouch/System Platform layer.
Common OI Servers include:
- OI Server for Allen-Bradley (ControlLogix, CompactLogix via EtherNet/IP)
- OI Server for Siemens (S7 family)
- Modbus OI Server
- OPC DA/UA wrapper servers for third-party devices
The OI Server architecture provides a level of abstraction that integrates well with the ArchestrA object model — OI Server items map cleanly to object attributes — but it adds a software layer with its own installation, configuration, and licensing requirements. For a project with three or four different PLC families, you may need three or four separate OI Server licenses.
Tag import from PLC programs is possible but less standardized than Ignition's Studio 5000 import. AVEVA supports CSV-based tag import and some vendor-specific import utilities, but the experience is more manual.
For a deeper look at OPC UA connectivity across both platforms, see the OPC UA complete guide.
Historian and Data Storage
Ignition: SQL-backed, built-in
Ignition's historian stores tag data directly in a SQL database — typically MySQL, Microsoft SQL Server, or PostgreSQL — which you provide or which Ignition can manage internally. This means historical data is immediately accessible via standard SQL queries from any reporting tool, MES system, or custom application. No proprietary API or query language is required to extract data.
The Transaction Manager module handles buffering during network outages, and data compression settings are configurable per-tag. The Reporting module can query historical data directly in report templates using named queries — the data and the reporting layer live in the same Ignition project.
AVEVA: Dedicated Historian product
AVEVA Historian (formerly Wonderware Historian, before that IndustrialSQL Server) is a separate product from InTouch. It uses a proprietary compressed storage format optimized for time-series data, with a SQL Server front end that exposes standard SQL access via a set of special system tables and the eDNA query dialect.
AVEVA Historian is a genuinely capable time-series store — it handles very high-frequency data and large-scale enterprise historian replication better than Ignition's SQL-backed store at the extremes of scale. The Historian also integrates tightly with AVEVA Insight (cloud analytics) and the PI System historian (OSIsoft PI, also AVEVA-owned since 2021) for plants that need both real-time trending and long-term asset performance management.
The trade-off is licensing complexity and the need to manage a separate application stack. For most mid-market projects below 50,000 tags at high-frequency, Ignition's SQL historian is sufficient and simpler to maintain.
HMI and Visualization
Ignition Perspective vs InTouch WindowViewer
Ignition's current HMI framework is Perspective — a web-based, responsive HMI that renders in any modern browser on any device, including mobile. Perspective uses a component-based design model with CSS styling, binding expressions, and Python scripting. The older Vision module produces Java thick-client HMIs that run as downloaded applications.
For the detailed breakdown of Perspective versus Vision, see Ignition Perspective vs Vision.
AVEVA InTouch WindowViewer is a Windows thick client. A web-based option (InTouch OMI and the newer AVEVA Unified Engineering client) has been added in recent releases, but the majority of deployed InTouch systems run the traditional thick client. The Windows-only constraint is a genuine limitation for organizations moving toward thin-client or BYOD operator interfaces.
Both platforms support vector graphics, animated process graphics, faceplates, trends, and alarm displays. Ignition's component library is broader in its default install; AVEVA's graphics library benefits from decades of process industry-specific symbols and faceplate templates developed by the integrator community.
Scripting and Custom Logic
Ignition: Python everywhere
Ignition uses Jython (Python 2.7 syntax, with Python 3 support in the Ignition 8.x roadmap) as its scripting language. Python scripts run in Gateway event scripts, tag change scripts, component event handlers, Timer scripts, and message handlers. The same language and the same system.* API functions are available everywhere — there is no context switching between scripting environments.
Python is widely taught, has a massive library ecosystem, and is the dominant language in data science and industrial analytics tooling. Controls engineers who have never scripted before generally find Python more approachable than VB-style languages.
AVEVA InTouch: QuickScript NG
InTouch scripting uses QuickScript NG, a proprietary language with Visual Basic-style syntax. QuickScript has been the InTouch scripting language since the 1990s. It is functional and familiar to engineers who have lived in the AVEVA ecosystem, but it is not a general-purpose language — there is no package manager, no community library ecosystem, and porting QuickScript logic to any other platform requires a rewrite.
AVEVA System Platform also supports ArchestrA scripting (an evolution of QuickScript used within automation objects) and, in newer releases, limited integration with external Python environments for analytics workloads.
Support, Community, and Ecosystem
Ignition: Large open community, active forums
Inductive Automation runs the Ignition Community Forum — an active, indexed forum where most common problems have documented solutions. The Maker Edition and the free trial mean there are tens of thousands of engineers with hands-on Ignition experience, including many who started as hobbyists and moved into professional deployment. Third-party modules from the Ignition Exchange extend the platform in areas like advanced charting, PDF generation, and equipment monitoring.
Inductive Automation's annual ICC (Ignition Community Conference) is a useful barometer of where the platform is heading and what the integrator community is building.
AVEVA: Large installed base, partner network
AVEVA's support model runs through a network of System Integrators (the AVEVA Select partner program) and direct support contracts. The community forum (AVEVA Community) is active but smaller relative to the installed base, and many solutions are gated behind support contracts. The sheer size of the AVEVA installed base means that most problems have been encountered before — finding the solution may require a support call rather than a forum search.
For SCADA best practices and design patterns, both platforms have mature integrator communities that have documented production-proven approaches.
Which Platform Should You Choose?
Choose Ignition if:
- Budget certainty matters. The unlimited-tag, unlimited-client model means your licensing cost is fixed at specification time and does not grow with scope creep.
- Your PLC fleet is mixed. Native Allen-Bradley, Siemens, and Modbus drivers without separate OI Server licensing simplify the connectivity story.
- You need Linux or containerized deployment. Docker/Linux Ignition deployments are production-proven and well-documented.
- Your team knows Python or you want a scripting language with a future beyond the SCADA platform.
- You are building a new SCADA system from scratch without an existing AVEVA asset hierarchy to protect.
- Mobile operator interfaces or remote access are in scope — Perspective's browser-based delivery is a genuine advantage here.
Choose AVEVA InTouch / System Platform if:
- You have an existing AVEVA / Wonderware installation that you are expanding. Migrating a working galaxy to Ignition is a significant engineering project; extending it is not.
- Your plant has thousands of similar equipment items (reactors, vessels, pump sets) where ArchestrA object inheritance and template propagation save engineering time at scale.
- You operate in a multi-site enterprise that has standardized on AVEVA System Platform for cross-site historian replication and unified alarming.
- The PI System (OSIsoft PI) is your corporate historian. AVEVA Historian and PI System are now both AVEVA products and their integration is tighter than any third-party connection.
- Your SIs and operators are already trained on InTouch. Retraining cost is real and should be in the TCO calculation.
For HMI design guidance that applies regardless of platform, see HMI design best practices.
Migrating from Wonderware to Ignition: The Reality
Migration projects are common, and vendors on both sides tend to understate the effort. Here is what the migration actually involves for a controls engineer:
Tag database: Ignition can import tags from CSV. Exporting tags from an AVEVA InTouch application to CSV is straightforward, but the tag naming conventions in InTouch (dot-notation access names, I/O names, and memory tags as separate constructs) do not map cleanly to Ignition's hierarchical tag structure. Budget time for tag restructuring, not just import.
Graphics: InTouch graphics (.WIN files) do not import into Ignition. Every screen must be rebuilt. This is the largest effort item on most migration projects — a complex process plant with 200+ graphic windows is a multi-month rebuild. Ignition's component model is different enough from InTouch's symbol library that copying is not possible; the screens need to be redrawn from the P&ID.
Scripting: QuickScript NG logic must be rewritten in Python. The syntax is different enough that automated conversion tools produce unreliable results — manual rewrite with functional testing is the safe approach.
Historian: If you are moving historical data from AVEVA Historian to Ignition's SQL historian, AVEVA provides export utilities to standard formats. Migrating years of compressed process data to a new SQL schema is a data engineering project in its own right and is often deferred — many migrations run both historians in parallel for a period.
What does not change: PLC programs do not need to change. The Ignition native drivers will connect to the same ControlLogix or Siemens PLCs that the AVEVA OI Servers were talking to. If you have OPC UA connectivity at the PLC level, the migration is even cleaner.
A realistic estimate for a mid-size InTouch application (2,000–5,000 tags, 30–50 screens, moderate scripting) is 3–6 months of engineering effort for a competent Ignition integrator, not including historian migration.
Frequently Asked Questions
Is Ignition better than Wonderware?
Neither platform is categorically better — they suit different contexts. Ignition is generally better for new projects where licensing cost, OS flexibility, and Python scripting are priorities. Wonderware (AVEVA InTouch / System Platform) is generally better for large-scale process plants with existing AVEVA infrastructure, complex equipment object hierarchies, or deep integration requirements with the AVEVA Historian and PI System ecosystem. The "better" platform is the one that fits your specific project scope, existing infrastructure, and team skills.
How much does Ignition cost vs Wonderware?
Ignition publishes list pricing and the base platform plus common modules is accessible to a wide range of project budgets. AVEVA does not publish pricing publicly — costs are quote-only through resellers and vary by tag count tier, client count, and module selection. Independent assessments and public procurement records consistently show that for projects above a few thousand tags with multiple concurrent clients, Ignition's total licensing cost is lower. The gap narrows for very small tag counts where AVEVA's entry-level tiers are competitive, and widens significantly for large-scale deployments where Ignition's unlimited model eliminates per-unit scaling costs. Always request a formal quote from an AVEVA reseller for accurate project-specific pricing.
Can you migrate from Wonderware to Ignition?
Yes, and it is done regularly. The migration is a real engineering project — tag databases can be imported via CSV after restructuring, but graphics must be rebuilt and QuickScript logic must be rewritten in Python. The PLC programs and wiring do not change. A typical mid-size application (2,000–5,000 tags, 30–50 screens) requires 3–6 months of integrator effort. Projects with complex ArchestrA object models or large historian archives require additional planning. The business case usually rests on licensing cost savings at scale, Linux/cloud deployment requirements, or organizational standardization on Python.
What is Wonderware called now?
Wonderware was rebranded to AVEVA following the merger of Schneider Electric's industrial software business with AVEVA Group in 2018. The main products were renamed: Wonderware InTouch is now AVEVA InTouch HMI, Wonderware System Platform is now AVEVA System Platform, and Wonderware Historian is now AVEVA Historian. In January 2023, Schneider Electric completed its full acquisition of AVEVA, taking the company private. The software products continue to be developed and supported under the AVEVA brand. See the full Wonderware to AVEVA name guide for the complete product mapping.
