Ignition and Wonderware InTouch (now AVEVA InTouch HMI) are two of the most common shortlist finalists for industrial HMI/SCADA — and they represent two completely different eras of the industry. One was the original Windows HMI of 1989; the other rewrote the licensing rulebook in 2010. This guide compares them honestly on licensing, web deployment, tag scalability, and integrator ecosystems — and covers a third option for manufacturers and utilities that don't have an integrator budget for either.
Ignition wins for industrial manufacturers who need flexible, web-deployed SCADA with unlimited tags and flat-rate server licensing; Wonderware InTouch wins for plants standardized on AVEVA System Platform with an existing base of InTouch applications and integrators. Ignition's one-server license covers unlimited tags, clients, and device connections; InTouch's traditional model licenses by tag tier and per runtime client, which grows more expensive as screens and users multiply.
That is the economic headline, but it is not the whole decision. InTouch remains one of the most widely installed HMI products in the world, with a distributor and integrator network built over three and a half decades. Ripping out working InTouch screens purely to change licensing models rarely pays back. And both platforms share one assumption worth flagging early: someone — an integrator or an in-house controls engineer — has to build and maintain the application. If that person doesn't exist in your budget, skip ahead to the managed-platform alternative discussed below.
| Dimension | Ignition | Wonderware (AVEVA InTouch) |
|---|---|---|
| Vendor | Inductive Automation (independent) | AVEVA (Schneider Electric group) |
| First released | 2010 (roots in FactoryPMI/FactorySQL) | 1989 — a pioneering Windows HMI |
| Licensing | Per server; unlimited tags, clients, connections | Tag-count tiers; development + runtime licenses per seat |
| Web clients | Native HTML5 via Perspective module | InTouch Web Client / Access Anywhere; OMI via System Platform |
| Operating systems | Windows, Linux, macOS (Java-based server) | Windows |
| Typical buyer | Greenfield or mixed-vendor plants with engineering resources | Plants invested in AVEVA System Platform and legacy InTouch apps |
Wonderware was founded in 1987 and shipped InTouch in 1989 — commonly credited as the first widely adopted Windows-based HMI. For a generation of plants, "the Wonderware screen" simply meant the operator interface. The company passed through Siebe, Invensys, and Schneider Electric before landing in AVEVA's portfolio in 2018, where InTouch now lives alongside System Platform, the AVEVA Historian, and the OMI visualization layer. That lineage is InTouch's greatest strength and its greatest weakness: an enormous installed base and integrator network, carried on an architecture and licensing model designed decades ago.
Inductive Automation was founded in 2003 by a systems integrator frustrated with exactly that model, and released Ignition in 2010. Ignition's break with tradition was total: a Java-based, cross-platform server you download and trial for free, priced per server with unlimited tags, unlimited clients, and unlimited device connections. Training is free through Inductive University, and pricing is published on the vendor's website — both rarities in industrial software. Ignition grew by winning the projects where per-client and per-tag licensing hurt most: plants with many screens, many users, and growing tag counts.
Licensing is the single biggest practical difference between these platforms. Ignition licenses by the server — publicly listed pricing commonly runs $10,800–$30,000 one-time depending on which modules you add — and that license includes unlimited tags, unlimited concurrent clients, and unlimited device connections. Adding a tenth operator screen or a thousandth tag costs nothing in software.
InTouch follows the traditional model: licenses are quoted through AVEVA distributors, commonly cited in tag-count tiers (500, 1,000, 3,000, up to 60,000+ tags), with development licenses and runtime licenses sold per seat. A plant that grows from three operator stations to ten, or from 900 tags to 3,500, crosses licensing thresholds that trigger new purchases. Annual support contracts (customer-first support agreements) add a recurring percentage on top. None of this is unusual — Siemens and Rockwell license similarly — but it is the model Ignition was explicitly built to disrupt.
The honest caveats cut both ways. Ignition's "unlimited" applies per server: a large multi-site architecture may need multiple gateways, edge licenses, and redundancy licenses, so real projects are rarely one $10,800 line item. And for a genuinely small application — one panel PC running a 400-tag machine HMI — a small InTouch runtime tier can be perfectly cost-competitive. The gap opens as tag counts and client counts grow. If licensing math is the core of your evaluation, our ROI calculator is built for exactly this comparison.
Ignition has the cleaner web story. The Perspective module delivers true HTML5 clients — screens built once run in any browser and in native iOS/Android apps, with no client installation and no per-session fee, because sessions fall under the unlimited-client server license. For manufacturers and utilities that want engineers, supervisors, and managers viewing live data from laptops and phones, this is Ignition's signature capability.
AVEVA's web options are real but more layered. InTouch Access Anywhere publishes existing InTouch applications to a browser via an HTML5 remote-desktop-style session — effective for reusing legacy screens without rebuilding them, but it is screen sharing rather than a responsive web app. AVEVA OMI, delivered through System Platform, is the modern multi-display visualization layer and is genuinely strong in large control-room environments — but it presumes a System Platform investment, which is a bigger architectural and financial commitment than a standalone InTouch node. Teams evaluating pure browser-first deployment usually find Perspective the more direct path; teams already running System Platform get OMI's strengths as part of the ecosystem they own.
Ignition imposes no license limit on tag count — practical ceilings come from server hardware and architecture, and large deployments scale out with multiple gateways, the gateway network, and Ignition Edge at remote sites. This makes tag growth an engineering question rather than a procurement question, which operations teams tend to appreciate when instrumentation grows faster than budgets.
InTouch scales differently. Standalone InTouch applications live within their licensed tag tier; large distributed systems move up to AVEVA System Platform, whose galaxy architecture is proven at very large scale in refineries, power plants, and food and beverage networks. The scalability is real — some of the largest SCADA estates in the world run on AVEVA — but it arrives bundled with System Platform's complexity and licensing, and typically an integrator-led architecture project. For a broader look at how the major platforms stack up on scale, see our top 10 SCADA platforms comparison.
This is Wonderware's strongest card. Thirty-five-plus years of installations built one of the deepest integrator and distributor networks in industrial automation; in most industrial regions you can find several firms with certified InTouch and System Platform experience, and plant technicians who grew up on InTouch screens. If your maintenance strategy depends on locally available talent for a legacy-heavy plant, that bench depth matters.
Ignition's ecosystem is younger but expanding quickly: a large certified-integrator program, an unusually active community forum, and free self-paced training that lets in-house engineers become productive without a certification course. The practical difference: InTouch talent is easier to find for maintaining what exists; Ignition talent is increasingly what new-build projects request. Either way, both platforms are toolkits — budget for the build, not just the license.
If your shortlist is wider than two, the pattern across the big four is ecosystem-driven. Ignition is the cross-platform, licensing-flexible generalist; the other three are strongest inside their own vendor stacks.
| Criterion | Ignition | Wonderware / AVEVA | Siemens WinCC | FactoryTalk View |
|---|---|---|---|---|
| Best fit | Mixed-vendor or greenfield plants | AVEVA System Platform estates | Siemens-standardized plants | Allen-Bradley shops |
| Licensing model | Per server, unlimited tags/clients | Tag tiers + per-seat runtimes | Tag tiers + client licenses | Per server + per client |
| Web deployment | Native HTML5 (Perspective) | Access Anywhere / OMI | WinCC Unified web clients | ViewPoint web (limited) |
| PLC ecosystem tie-in | Vendor-neutral | Vendor-neutral, AVEVA historian tie-in | Deep TIA Portal integration | Deep Logix/Studio 5000 integration |
| Cross-platform server | Windows, Linux, macOS | Windows | Windows | Windows |
The rule of thumb: single-vendor Siemens plants rarely regret WinCC, single-vendor Rockwell plants rarely regret FactoryTalk (see our FactoryTalk vs AVEVA comparison for that matchup), and everyone else — mixed hardware, greenfield, or licensing-sensitive — should have Ignition on the shortlist alongside the incumbent.
Both Ignition and InTouch are development platforms — powerful ones — and both assume a funded build: integrator engineering or an in-house developer, screen development, alarm configuration, historian setup, and ongoing maintenance. For many manufacturers, utilities, and oil and gas operators, that project is the real barrier, not the license price.
Merobix takes the managed-platform path instead. The Merobix team connects to your existing PLCs — 20 protocol drivers across 7 protocol families, from Modbus to EtherNet/IP to OPC-UA — and configures dashboards, alarms, and reporting for you. Cloud deployments go live in 3–5 days with a 99.9% uptime SLA and SMS/email alerts delivered in under 30 seconds. Prefer to keep everything inside your firewall? Merobix also installs on your own servers and VMs, including fully air-gapped networks, with complete data residency. Enterprise plans add hot standby redundancy, LDAP/SAML single sign-on, SIEM integration, and connectors for SAP, Maximo, ServiceNow, and Kafka — see the full plan feature matrix.
Pricing follows the same philosophy Ignition made popular, taken further: flat all-inclusive plans, custom-quoted for your operation, with no per-tag, per-client, or per-protocol fees — and no integrator invoice, because configuration is included. To be equally honest in the other direction: Merobix is not a custom HMI development toolkit. If you need pixel-precise P&ID screens for a refinery control room, Ignition or InTouch with a good integrator is the right tool. If you need reliable monitoring, alarming, and reporting across your operation without staffing a SCADA project, that gap is exactly what Merobix was built for.
Evaluation tip: Before shortlisting any platform, price the whole project — license, server hardware, integrator engineering, and annual support — not just the license line. An Ignition license at publicly listed pricing plus $30k–$120k of integrator engineering is a different decision than the license alone. Then ask each vendor two questions: "What does adding ten more clients cost?" and "Who builds and maintains the application?" Our SCADA migration guide covers how to run that evaluation, and a guided Merobix demo shows what the managed alternative looks like on your own use case.
Neither is universally better — they serve different priorities. Ignition (Inductive Automation) wins on licensing economics and modern web deployment: one server license includes unlimited tags, clients, and device connections, and the Perspective module delivers true HTML5 clients to any browser. Wonderware InTouch (now AVEVA InTouch HMI) wins on installed base, integrator availability, and continuity for plants with decades of existing InTouch applications. Teams building new systems generally favor Ignition; plants standardized on AVEVA System Platform with existing InTouch screens often stay. A third path — managed SCADA platforms like Merobix — suits operators who lack integrator budgets for either.
Yes. Ignition's server-based license includes unlimited clients, so manufacturers and utilities can run as many operator screens, browser sessions, and mobile users as one server supports without per-client fees — and it deploys on-premise on Windows or Linux, or in the cloud, including Ignition Cloud Edition on the AWS and Azure marketplaces. The caveat is engineering: Ignition is a toolkit, and most deployments require an integrator or in-house developer to build screens, alarming, and historian configuration. If you want unlimited-client economics without the build project, a managed platform like Merobix offers flat all-inclusive plans, cloud-hosted or installed on your own servers.
Ignition publishes its pricing: a server license commonly runs $10,800–$30,000 one-time depending on modules, with unlimited tags and clients included. AVEVA InTouch pricing is quoted through distributors and is commonly cited in tag-count tiers (500, 1,000, 3,000, up to 60,000+ tags) with separate development and runtime licenses per seat — so cost grows with both tag count and client count. For a plant with many operator stations, Ignition's per-server model is usually cheaper; for a single small HMI panel, InTouch can be competitive. Merobix pricing is custom-quoted — flat all-inclusive plans with no per-tag, per-client, or per-protocol fees.
Ignition is the flexibility and licensing leader: cross-platform, unlimited tags and clients per server, and web-deployed via Perspective. Wonderware (AVEVA InTouch/System Platform) has the largest legacy installed base and deep integration with the AVEVA historian and OMI. Siemens WinCC is the default in Siemens-standardized plants and integrates tightly with TIA Portal. Rockwell FactoryTalk View is the default for Allen-Bradley shops. In practice the decision is usually ecosystem-driven: mixed-vendor or greenfield plants favor Ignition; single-vendor Siemens or Rockwell plants favor their native HMI; AVEVA plants with existing System Platform investment stay on InTouch and OMI.
Consider a managed SCADA platform. Merobix delivers monitoring, alarming with SMS and email alerts in under 30 seconds, a historian, and reporting as flat all-inclusive plans — cloud-hosted and live in 3–5 days, or installed on your own servers and VMs, including air-gapped networks with full data residency. There are no per-tag, per-client, or per-protocol fees, 20 protocol drivers across 7 protocol families are included, and the Merobix team does the configuration, so no integrator project is required. Pricing is custom-quoted, and guided demos and pilots are available.
Managed SCADA — cloud-hosted or on your own servers — with flat, custom-quoted, all-inclusive plans.