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

Wonderware was the SCADA system everyone grew up with. If you walked into a plant between 1995 and 2015, there was a better-than-even chance the HMI was running InTouch, Wonderware's flagship visualization product. The brand carried weight. Engineers trusted it. Procurement departments had it on approved vendor lists. Then AVEVA acquired it, folded it into System Platform, and the pricing went from "expensive but manageable" to "enterprise procurement event."

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. Wonderware as a standalone product barely exists anymore. What AVEVA sells today is AVEVA System Platform, which absorbed the old Wonderware InTouch, Wonderware Historian, and Wonderware Application Server into a unified architecture. When someone says "Wonderware" in 2026, they mean AVEVA System Platform with the InTouch visualization component.

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

• Windows Server requirement. AVEVA System Platform runs on Windows Server. Not Windows Desktop. Windows Server, with Client Access Licenses. If your IT department does not have a Windows Server infrastructure, you are building one just for SCADA.
• Microsoft SQL Server. The historian, configuration database, and alarm journal all require SQL Server. That is another license. SQL Server Standard Edition runs about $1,000 per core. SQL Server Enterprise runs significantly more.
• Engineering workstation. Development and configuration happens on a dedicated engineering workstation running the AVEVA IDE, which is a heavy .NET application with its own system requirements.
• Dedicated networking infrastructure. AVEVA recommends separate networks for the Galaxy Repository, the I/O servers, and the client tier in larger deployments.
• Certified training. AVEVA requires certified training for most integrators. Their System Platform boot camp is a five-day course that costs $3,000 to $5,000 per person.

The total cost of entry for a basic AVEVA System Platform deployment, including software licensing, server infrastructure, SQL Server, and training, starts at $50,000 and realistically runs $80,000 to $100,000+ for a mid-size plant. That is before you pay for the engineering hours to configure it, which typically adds another $30,000 to $80,000 depending on complexity.

These are not inflated numbers. They come directly from AVEVA's own pricing sheets and from system integrators who post their project costs on PLCTalk.net and Control.com. A mid-size food and beverage plant with 3,000 tags reported spending $92,000 on AVEVA licensing alone in a 2025 forum thread.

What Voltrus Actually Is

Voltrus is SCADA software built for the projects AVEVA does not want. Single binary, under 20 MB, runs on anything. 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:

• No operating system requirements. Voltrus runs on Linux, Windows, and ARM. 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, not 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: $249 Starter, $499 Professional, $999 Enterprise. All lifetime licenses. No annual renewal. No per-tag pricing. No module marketplace where you discover the feature you need costs another $2,000. 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 Fortune 500 manufacturer with an existing AVEVA deployment, you use AVEVA. Full stop. These plants have standardized on AVEVA across their entire organization. Their maintenance teams are trained on it. Their IT departments have security hardening playbooks for it. Their procurement departments have master service agreements with AVEVA. Proposing an alternative is a political fight you will not win, regardless of technical merit.

Existing AVEVA Ecosystem

Plants that already run AVEVA System Platform have the infrastructure in place: Windows Server, SQL Server, trained operators, established backup procedures, and integration with AVEVA MES, AVEVA Historian, and AVEVA Enterprise Agreement. Adding another AVEVA node is incremental. Replacing it with something different is a transformation project with a multi-year timeline and a seven-figure budget.

MES and Enterprise Integration

AVEVA's real strength is not the SCADA layer. It is the integration between SCADA, MES, historian, and enterprise resource planning. 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 compliance, AVEVA's ecosystem handles this out of the box. No other platform integrates these layers as tightly. That integration is what the $50K+ price tag 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 they are invisible to AVEVA's sales organization. AVEVA's channel partners will quote them, but the software licensing alone exceeds the total project budget. We have seen system integrators on PLCTalk.net describe being quoted $45,000 in AVEVA licensing for a 300-tag project. The integrator's total project budget was $25,000. That conversation ends quickly.

Fast Deployment Requirements

Sometimes you do not have six 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 under an hour. Voltrus does exactly that. 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 all of it. AVEVA requires Windows Server with minimum hardware specifications that exclude most edge hardware. If your deployment target is a $35 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, AVEVA does not exist as an option. Voltrus at $249 to $999 is the only commercial SCADA that 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 Fortune 500 companies with enterprise procurement processes. The integrators who deploy AVEVA are large system integration firms with AVEVA-certified engineers on staff. Many of these deployments run entirely on-premise with air-gapped networks, which AVEVA's Windows Server architecture was designed to 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 $50,000 in software licensing.

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 under 5,000 tags, under $50K total 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 actual deployment experience tells a clearer story. Here is what a system integrator goes through to get each platform from "software acquired" to "dashboard showing live data."

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: 3 to 8 weeks for a mid-size deployment.

Deploying Voltrus

1. Download the binary (20 MB). Timeline: 30 seconds.
2. Run it. Timeline: cold start under 1 second.
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: 1 to 6 hours for a typical deployment.

This is not a joke or an exaggeration. The difference between 3 weeks and 3 hours of deployment time is the difference between a project that requires scheduling and a project you can finish between lunch and dinner. For integrators who bill hourly, that difference directly impacts project profitability.

The Bottom Line

Wonderware, now AVEVA System Platform, is the established enterprise SCADA platform. It has earned its position through decades of deployment in the world's largest manufacturing plants. For Fortune 500 facilities with MES requirements, existing AVEVA infrastructure, and budgets that accommodate $50K+ in software licensing, it is the correct choice.

But most system integrators do not work on Fortune 500 plants. Most integrators work on projects with 50 to 5,000 tags, budgets under $50,000, and clients who need a monitoring system operational this week, not next month. For those projects, AVEVA is too expensive, too complex, and too slow to deploy.

Voltrus fills that gap. $249 to $999 lifetime. Single binary, no dependencies, runs on a Raspberry Pi. Modbus TCP, Siemens S7, EtherNet-IP, MQTT. Dashboards, trend charts, alerts, user authentication. Deployed in hours, not weeks. The commercial SCADA platform for the projects the enterprise vendors ignore.

Frequently Asked Questions

How much does AVEVA Wonderware (System Platform) cost?

A basic AVEVA System Platform deployment starts at $50,000 and realistically runs $80,000-$100,000+ for a mid-size plant. This includes Windows Server licensing, SQL Server licensing ($1,000+ per core for Standard Edition), AVEVA software licensing, and certified training ($3,000-$5,000 per person for a five-day course). Engineering configuration hours typically add another $30,000-$80,000.

Can Voltrus replace Wonderware for small monitoring projects?

Yes, for projects with 50 to 5,000 tags where you need Modbus TCP, Siemens S7, EtherNet-IP, or MQTT monitoring with dashboards, trends, and alerts. Voltrus deploys in hours instead of weeks, runs on a Raspberry Pi instead of Windows Server, and costs $249-$999 lifetime instead of $50,000+. It is not a replacement for 10,000+ tag plants with MES integration and enterprise compliance requirements.

Does Wonderware require Windows Server and SQL Server?

Yes. AVEVA System Platform requires Windows Server with Client Access Licenses, Microsoft SQL Server for the historian, configuration database, and alarm journal, and a dedicated engineering workstation running the AVEVA IDE (.NET application). Voltrus has no operating system prerequisites beyond a basic Linux, Windows, or ARM system and uses an embedded database.

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

Voltrus deploys in 1-6 hours: download the binary, run it, configure devices, build dashboards. AVEVA System Platform takes 3-8 weeks for a mid-size deployment: Windows Server provisioning, SQL Server setup, AVEVA installation, ArchestrA hierarchy configuration, InTouch dashboard building, alarm and security setup, testing, and commissioning.

When should I choose Wonderware over Voltrus?

Choose AVEVA System Platform when the plant already uses AVEVA, the project has 10,000+ tags, you need MES integration with ERP systems, FDA 21 CFR Part 11 compliance is required, or the client is a Fortune 500 company with established AVEVA infrastructure. For everything else — projects under 5,000 tags, budgets under $50K, and deployment timelines measured in days — Voltrus is the practical choice.

Further Reading

• Voltrus vs Ignition: An Honest Comparison for System Integrators
• Is There Any SCADA Under $1,000? (Yes, and It's Not Open Source)
• The Best SCADA Software Alternatives in 2026