Voltrus vs Wonderware (AVEVA): Cost, Complexity, and What Integrators Actually Need

By Dzulfikar Ats Tsauri, founder of Voltrus / JoyoDigitama. He builds the protocol tools covered in these posts. Updated October 28, 2026.

Wonderware was the SCADA system everyone grew up with. InTouch, Wonderware's flagship visualization product, was one of the most widely used HMI packages from the 1990s on. The brand carried weight. Engineers trusted it. Procurement departments had it on approved vendor lists. Then the ownership changed: Schneider Electric acquired Invensys, the owner of the Wonderware brand, in 2014, and Schneider's software business merged into AVEVA in 2018. The products were later renamed under the AVEVA brand: AVEVA System Platform, AVEVA InTouch HMI and AVEVA Historian.

This comparison is not about knocking Wonderware. AVEVA System Platform is legitimately powerful software that runs some of the largest manufacturing facilities on the planet. The question this article answers is different: does it make sense for the kind of projects most system integrators actually work on? Because there is a massive difference between what runs a 10,000-tag automotive plant and what runs a 200-tag water treatment skid.

What Wonderware (AVEVA System Platform) Actually Is

Let's be precise about what we are comparing. AVEVA has retired the Wonderware name: its own site lists AVEVA System Platform as "formerly Wonderware", with AVEVA InTouch HMI and AVEVA Historian as the former Wonderware InTouch and Wonderware Historian. System Platform is built on the ArchestrA architecture (Galaxy Repository, Application Server, IDE). In this article, "Wonderware" means AVEVA System Platform, usually together with InTouch for visualization.

AVEVA System Platform is enterprise SCADA software designed for large-scale manufacturing. Here is what a typical deployment involves:

• Windows platform. AVEVA's System Platform 2020 readme lists Windows 10 as supported for components such as the Galaxy Repository and the IDE, and says a Windows Server operating system is required for large installations (more than 50,000 I/O per node). Larger or multi-node systems typically run on Windows Server, which adds Windows Server licensing.
• Microsoft SQL Server. The Galaxy Repository and the Historian use SQL Server, which is a separate licence cost beyond the free Express edition (AVEVA does not support Express above 25,000 I/O per node). Microsoft lists SQL Server 2022 Standard at $3,945 per 2-core pack, or $989 per server plus $230 per CAL (Microsoft SQL Server 2022 pricing page, checked October 2026).
• Engineering workstation. Development and configuration happens in the AVEVA System Platform IDE, a Windows desktop application, typically on a dedicated engineering workstation.
• Multi-node planning. Larger deployments spread roles such as the Galaxy Repository, application servers, I/O servers and clients across several nodes, which needs network and domain planning.
• Training. AVEVA offers certified training courses, and the ArchestrA object model has a learning curve for engineers new to it.

AVEVA sells System Platform on quotes rather than a public price list, so the total cost depends on a quote from AVEVA or a distributor: software licences sized to your system, Windows and SQL Server licences, server hardware, training, and the engineering hours to configure it. For small monitoring projects that software and infrastructure cost can be a large share of the project budget, so get quotes before assuming either way.

What Voltrus Actually Is

Voltrus is SCADA software built for projects where an enterprise platform is more than the job needs. Single binary, runs on small hardware. Raspberry Pi, a Linux VPS, a Windows desktop, an ARM-based industrial gateway. No installer wizard. No prerequisites. Download the binary, run it, open a browser.

The design philosophy is different from AVEVA in every possible way:

• Light platform requirements. Voltrus runs on Linux (x86_64 and ARM64) and Windows (x86_64). No Windows Server, no SQL Server, no .NET Framework, no IIS.
• No database server. Voltrus has built-in data retention. It stores trend data and events locally without requiring an external database.
• No engineering workstation. Configuration happens in the web browser. Open the dashboard builder, drag widgets, connect to devices, save. The configuration interface is the same whether you are on a laptop or a tablet.
• No certified training. If you can configure a Modbus TCP device, you can configure Voltrus. The learning curve is measured in hours rather than days.
• Cold start under one second. From process start to web interface available. No services to wait for, no databases to spin up, no JVM warmup.

Pricing: Core is free (open source, AGPL-3.0), Integrator $249 lifetime per site, Enterprise $999 lifetime per site, with Integrator and Enterprise also available per site per month. No per-tag pricing. No module marketplace. The lifetime license versus SaaS subscription model makes a significant difference over a five-year deployment horizon.

Voltrus vs Wonderware: Side-by-Side Comparison

When Wonderware (AVEVA) Is the Right Choice

This section exists because honesty matters. AVEVA System Platform is the right tool for certain jobs. Here is where it wins:

Fortune 500 Manufacturing

If your client is a large manufacturer with an existing AVEVA deployment, you will usually use AVEVA. These plants often standardize on AVEVA across the organization: maintenance teams are trained on it, IT departments have hardening playbooks for it, and procurement has agreements with AVEVA. Proposing an alternative can be a political fight, regardless of technical merit.

Existing AVEVA Ecosystem

Plants that already run AVEVA System Platform have the infrastructure in place: Windows servers, SQL Server, trained operators, established backup procedures, and integration with other AVEVA products such as AVEVA MES and AVEVA Historian. Adding another AVEVA node is incremental. Replacing it with something different is a transformation project.

MES and Enterprise Integration

AVEVA's real strength is not the SCADA layer. It is the integration between SCADA, MES, historian, and enterprise systems. If your project needs to feed production data into SAP, track OEE across multiple plants, and maintain an audit trail for FDA 21 CFR Part 11 workflows, AVEVA's ecosystem is built for this. That integration is a large part of what its licensing buys you.

When Voltrus Is the Right Choice

Now for the projects AVEVA cannot see, will not quote, and has no interest in.

Small to Mid-Size Projects (50-5,000 Tags)

A water treatment skid with 80 sensors. A boiler monitoring system with 200 tags. A solar farm with 50 Modbus TCP meters and a dashboard for the operations team. These are real projects with real budgets, and for many of them the software and infrastructure cost of an enterprise platform is a large share of the total budget. Ask for an AVEVA quote for your own scope and compare it against the project budget.

Fast Deployment Requirements

Sometimes you do not have weeks to deploy infrastructure. A client needs a monitoring dashboard operational by Friday. The PLCs are already talking Modbus TCP. The sensors are wired. You need SCADA software that goes from download to live dashboard in hours rather than weeks. Download the binary, run it, configure your Modbus TCP connections in the web UI, build your dashboard, done. No server provisioning, no SQL Server setup, no Windows licensing.

Limited IT Infrastructure

Not every facility has a server room. Many small industrial sites, remote pump stations, offshore platforms, and agricultural facilities run their monitoring on whatever hardware they have available. A Raspberry Pi, an old desktop, a thin client. Voltrus runs on Linux (x86_64 and ARM64) and Windows. AVEVA System Platform runs on supported Windows and Windows Server versions and is not designed for Raspberry Pi class hardware. If your deployment target is a Raspberry Pi sitting in a NEMA enclosure next to a pump, AVEVA is not an option. Voltrus is.

Budget Constraints

The uncomfortable reality of system integration is that most projects have tighter budgets than anyone wants to admit. The client wants monitoring, alerts, and trend charts. The integrator wants to deliver a professional system without eating their own margin on software licensing. When the total project budget is $10,000 to $30,000 and the software component needs to come in under $1,000, an enterprise platform is hard to justify. Voltrus, with a free core and licensed features at $249 to $999 per site, fits.

The Honest Take: They Are Not Competing

Here is the thing about Voltrus vs Wonderware comparisons. They are not competing for the same projects. AVEVA System Platform and Voltrus solve different problems at different scales for different buyers. Pretending otherwise is dishonest marketing, and dishonest marketing wastes system integrators' time.

AVEVA System Platform is for large plants with dedicated IT departments, established vendor relationships, and compliance requirements that demand enterprise-grade audit trails and redundancy. The buyers are typically large enterprises with formal procurement processes. Many of the integrators who deploy AVEVA are larger firms with AVEVA-certified engineers on staff. Many of these deployments run on-premise with air-gapped networks, which a Windows-server-based architecture can accommodate.

Voltrus is for small and mid-size projects where the integrator needs to deliver a professional SCADA system on a tight budget with minimal infrastructure. The buyers are independent system integrators, small automation firms, and plant engineers who need monitoring without enterprise overhead. The projects are real and billable, but they do not justify an enterprise software budget.

If you are an integrator deciding between Voltrus and AVEVA for a specific project, the decision tree is straightforward:

• Does the plant already use AVEVA? Use AVEVA.
• Is the project 10,000+ tags? Use AVEVA.
• Does the client require MES integration? Use AVEVA.
• Does the project need FDA or ISA compliance with certified audit trails? Use AVEVA.
• Is the project small to mid-size, on a tight budget, and needs to deploy fast? Use Voltrus.
• Is the deployment target a Raspberry Pi or an industrial gateway? Use Voltrus.
• Does the client not have Windows Server infrastructure? Use Voltrus.

What Deployment Actually Looks Like

Comparing price tags is useful. Comparing the deployment experience tells a clearer story. Here is roughly what a system integrator goes through to get each platform from "software acquired" to "dashboard showing live data." The durations below are rough estimates, not measurements.

Deploying AVEVA System Platform

1. Provision Windows Server (or requisition one from IT). Timeline: 1-2 weeks if hardware exists, 4-6 weeks if you need to procure.
2. Install and configure SQL Server. Apply licensing. Timeline: 1-2 days.
3. Install AVEVA System Platform prerequisites (.NET Framework, IIS, other components). Timeline: 1 day.
4. Install AVEVA System Platform. Run the bootstrap, configure the Galaxy Repository. Timeline: 1-2 days.
5. Configure the ArchestrA hierarchy, create application objects, configure I/O server connections. Timeline: 3-10 days depending on complexity.
6. Build InTouch dashboards. Timeline: 5-15 days depending on complexity.
7. Configure alarms, historians, user security. Timeline: 2-5 days.
8. Test, debug, commission. Timeline: 3-7 days.

Total: roughly 3 to 8 weeks for a mid-size deployment.

Deploying Voltrus

1. Download the binary. Timeline: a minute or two.
2. Run it. Timeline: cold start under 1 second (as stated on the Voltrus SCADA product page).
3. Open the web UI, configure Modbus TCP connections. Timeline: 10-30 minutes.
4. Build dashboards with the drag-and-drop builder. Timeline: 1-4 hours depending on complexity.
5. Configure alerts and user accounts. Timeline: 15-30 minutes.

Total: roughly 1 to 6 hours for a typical deployment.

The difference between a few weeks and a few hours of deployment time is the difference between a project that requires scheduling and a project you can finish in a day. For integrators who bill hourly, that difference directly impacts project profitability.

Frequently Asked Questions

How much does AVEVA Wonderware (System Platform) cost?

AVEVA sells System Platform on quotes rather than a public price list, so the cost depends on a quote from AVEVA or a distributor: software licences sized to the system, Windows and SQL Server licences (Microsoft lists SQL Server 2022 Standard at $3,945 per 2-core pack, or $989 per server plus $230 per CAL), server hardware, training, and engineering hours. Get quotes for your own scope before deciding.

Can Voltrus replace Wonderware for small monitoring projects?

Yes, for small to mid-size projects (tens to a few thousand tags) where you need Modbus, Siemens S7, EtherNet/IP, MQTT, OPC-UA, DNP3 or BACnet monitoring with dashboards, trends, and alarms. Voltrus runs on a Raspberry Pi or a Linux or Windows machine instead of a Windows Server and SQL Server stack, and the open source core (AGPL-3.0) is free, with licensed features at $249 to $999 lifetime per site. It is not a replacement for very large plants with MES integration and enterprise compliance requirements.

Does Wonderware require Windows Server and SQL Server?

Not always. AVEVA's System Platform 2020 readme lists Windows 10 as supported for components such as the Galaxy Repository and the IDE, and says a Windows Server operating system is required for large installations (more than 50,000 I/O per node). The Galaxy Repository and Historian use Microsoft SQL Server, and AVEVA does not support SQL Server Express above 25,000 I/O per node. Voltrus runs on Linux or Windows and uses an embedded database.

How long does it take to deploy Voltrus versus AVEVA System Platform?

As a rough estimate, Voltrus takes 1 to 6 hours to reach a working dashboard: download the binary, run it, configure devices, build dashboards. A mid-size AVEVA System Platform deployment commonly takes several weeks: Windows and SQL Server provisioning, AVEVA installation, ArchestrA hierarchy configuration, InTouch dashboard building, alarm and security setup, testing, and commissioning. These are estimates, not measurements.

When should I choose Wonderware over Voltrus?

Choose AVEVA System Platform when the plant already uses AVEVA, the project is very large, you need MES integration with ERP systems, FDA 21 CFR Part 11 compliance with certified audit trails is required, or the client is a large manufacturer with established AVEVA infrastructure. For small to mid-size projects with tight budgets and deployment timelines measured in days, Voltrus is the practical choice.

Further Reading

• SCADA Software for System Integrators: Ignition and Alternatives Compared
• SCADA Software Cost in 2026: From Free to $50K, and What Under $1,000 Gets You