Voltrus vs Kepware: Protocol Gateway vs Full SCADA

We need to address a category error that comes up constantly in SCADA selection discussions. Kepware is not a SCADA system. It is an OPC server, a protocol gateway, a data translator. It takes industrial protocols like Modbus, Siemens S7, Allen-Bradley EtherNet-IP, and dozens of others, and converts them into OPC-UA or OPC-DA so that other software can consume the data. That is an important job. But it is not the same job as running a SCADA system.

This matters because we regularly see system integrators asking "should I use Kepware or Voltrus?" on forums. The question itself reveals a misunderstanding of what each product does. Kepware moves data. Voltrus monitors and visualizes data. They are complementary, not competing. But there are cases where Voltrus alone replaces both, and cases where you genuinely need Kepware alongside Voltrus. This article will clarify exactly when each applies.

What Kepware Actually Does

Kepware, now owned by PTC (the company behind ThingWorx), is the most widely deployed OPC server in industrial automation. It has been around since 1995 and has earned its reputation. Here is what Kepware does well:

• Protocol translation. Kepware supports over 150 industrial protocol drivers. Modbus RTU, Modbus TCP, Siemens S7, Allen-Bradley EtherNet-IP, Mitsubishi, Omron, BACnet, DNP3, and dozens more. If a device talks an industrial protocol, Kepware probably has a driver for it. For an in-depth comparison of industrial protocols including Modbus TCP, OPC-UA, MQTT, and EtherNet/IP, see our protocol guide.
• OPC-UA server. Kepware exposes all connected devices as a unified OPC-UA namespace. Any OPC-UA client can subscribe to data without knowing the underlying protocol.
• OPC-DA server. For legacy systems that still use COM/DCOM-based OPC-DA, Kepware serves as a bridge between modern devices and legacy SCADA clients.
• Data quality management. Kepware handles connection failures, device timeouts, and data quality flags. It provides structured error reporting when a device goes offline.
• Aggregation. Kepware can collect data from hundreds of devices across multiple protocols and present them through a single OPC-UA endpoint.

Kepware runs on Windows. It requires a Windows license. A typical Kepware KEPServerEX installation costs $1,500 to $5,000 depending on the drivers you need. Each protocol driver is licensed separately. Want Modbus TCP? That is one driver. Want Siemens S7? Another driver. Want BACnet for building automation? Another driver. The base server includes a few common drivers, but specialized protocol support adds cost quickly.

What Kepware Does NOT Provide

This is the part that matters for the comparison. Kepware provides the plumbing, not the house. Here is what Kepware does not give you:

• No dashboards. Kepware has no visualization capability. It does not render data on a screen. It serves data to other applications that do.
• No trend charts. Kepware does not store or display historical data trends. It passes live values to whatever client subscribes to them.
• No alerts or notifications. Kepware does not send email alerts, SMS notifications, or push messages when a value exceeds a threshold. It sets quality flags, but it does not notify humans.
• No user management. Kepware has administrative access control for configuration, but it does not provide a user login system for operators viewing dashboards.
• No data retention. Kepware passes data through in real time. It does not store historical values for later retrieval. You need a separate historian for that.
• No web interface. Kepware's configuration UI is a Windows desktop application. There is no web-based access for operators or managers.

What Voltrus Actually Does

Voltrus is a SCADA platform. It connects to industrial devices, visualizes their data, stores trends, triggers alerts, and provides a web-based interface for operators and managers. Here is the full picture:

• Native protocol support. Voltrus connects directly to Modbus TCP, Siemens S7, Allen-Bradley EtherNet-IP, and MQTT devices. No OPC server required. The protocol drivers are built in. If you need to browse OPC-UA servers on your network, Voltrus also includes an OPC-UA client for exploring tags and namespaces without dedicated software.
• Dashboards. Web-based dashboard builder with live data widgets. Gauges, charts, status indicators, custom layouts. Accessible from any browser on any device.
• Trend charts. Built-in historical data storage and visualization. No external historian required. Configurable time ranges, multiple data series, zoom and pan.
• Alerts. Threshold-based email alerts. When a temperature exceeds 80 degrees, when a pressure drops below 2 bar, when a device stops responding. Alerts are configured per-device, per-tag.
• User authentication. Login screen, user accounts, role-based access control. Operators see dashboards. Administrators can configure devices and alerts.
• Data retention. Historical data is stored locally with configurable retention periods. No external database required.
• Single binary deployment. Under 20 MB, runs on Linux, Windows, and ARM. No prerequisites. No Windows Server. Download, run, open browser.

Pricing: $249 Starter, $499 Professional, $999 Enterprise. Lifetime licenses. All protocols included. No per-driver licensing.

Voltrus vs Kepware: Side-by-Side Comparison

Why They Solve Different Problems

The comparison table makes this clear, but let's spell it out with a real scenario.

Scenario: You are a system integrator tasked with monitoring 30 Modbus TCP energy meters across a factory floor. The client wants a dashboard showing real-time power consumption, trend charts for the last 30 days, and email alerts when any meter reports a voltage deviation beyond 10%. For more on setting this up, see our guide to monitoring Modbus TCP devices with dashboards and alerts.

Solution A: Kepware Alone

You install Kepware. You configure the Modbus TCP driver for 30 meters. Kepware connects to all of them and exposes the data as OPC-UA tags. Now what? You have no dashboard. No trend charts. No alerts. No way for the client to see the data. You need to buy, install, and configure separate software for visualization, alerting, and data storage. Kepware handled the protocol connection, but you still need the rest of the SCADA stack.

Solution B: Voltrus Alone

You install Voltrus. You configure 30 Modbus TCP devices in the web UI. You build a dashboard with power consumption widgets. Trend charts are automatic because Voltrus stores the data. You configure threshold alerts for voltage deviation. The client opens a browser and sees everything. Done. Total deployment time: 2-4 hours.

Solution C: Kepware + Voltrus

Wait, why would you use both? Because some plants already have Kepware installed and connected to hundreds of devices. In that case, Voltrus does not need to replace Kepware's protocol connectivity. But the plant still needs dashboards, trends, and alerts that Kepware does not provide. This is the complementary scenario, and we will discuss it in detail below.

When to Use Kepware With Voltrus

There are legitimate scenarios where using Kepware and Voltrus together makes sense. These are not theoretical. They happen regularly in the field.

Legacy Device Translation

Some industrial devices speak obscure protocols that Voltrus does not support natively. Maybe you have BACnet devices from a building management system. Maybe you have DNP3 devices from a utility SCADA. Maybe you have Profibus devices through a legacy gateway. Kepware has drivers for these protocols. Voltrus does not. In this scenario, Kepware translates the obscure protocol into OPC-UA, and Voltrus (or another OPC-UA client) consumes the data. Kepware is the translator. Voltrus is the monitor.

Existing Kepware Deployment

Many plants already have Kepware installed and configured with dozens or hundreds of device connections. The engineering hours invested in that configuration are significant. Tearing it out to replace it with Voltrus's native protocol support is unnecessary risk. Instead, you add Voltrus as the visualization and alerting layer on top of Kepware's data infrastructure. The plant gets modern dashboards, trend charts, and alerts without disrupting the established data pipeline.

Multi-Client Architecture

In some architectures, Kepware serves as a centralized data broker that feeds multiple consumers. The SCADA system reads from Kepware. The MES reads from Kepware. The data historian reads from Kepware. Kepware is the single source of truth for device connectivity. In this architecture, Voltrus might be one of several consumers reading from Kepware's OPC-UA server. This is a valid and common pattern in larger plants.

When Voltrus Alone Is Enough

For a large number of system integration projects, Voltrus handles everything without needing Kepware. If your devices speak the protocols Voltrus supports natively, there is no reason to add a separate OPC server to the architecture.

Modbus TCP Projects

Modbus TCP is the most deployed industrial protocol in the world. Energy meters, VFDs, PLCs, temperature controllers, pressure transmitters. If your project is Modbus TCP, Voltrus connects directly. No OPC server needed. No Windows machine needed. Configure the device IP, register map, and polling rate in Voltrus, and you have live data flowing into dashboards within minutes.

Siemens S7 Projects

Siemens S7-200, S7-300, S7-400, S7-1200, and S7-1500 PLCs are everywhere. Voltrus connects to them directly using the S7 protocol over Ethernet. No Kepware S7 driver needed. No OPC-UA translation layer. Direct connection, direct data.

Allen-Bradley EtherNet-IP Projects

Allen-Bradley ControlLogix and CompactLogix PLCs communicate via EtherNet-IP (CIP). Voltrus supports EtherNet-IP natively. If your project is a Rockwell Automation environment with ControlLogix PLCs, Voltrus reads the controller tags directly without Kepware as an intermediary.

MQTT Projects

MQTT is increasingly common in industrial IoT deployments. Sparkplug B payloads from edge gateways, MQTT messages from sensor nodes, telemetry from remote sites. Voltrus subscribes to MQTT topics directly and can display live values, trigger alerts, and store trends from MQTT data sources.

The Simplicity Argument

Every component in a system architecture adds a point of failure, a licensing cost, a configuration effort, and an ongoing maintenance burden. If Voltrus can connect to your devices directly, adding Kepware introduces a component that provides no additional value while adding cost and complexity. The best architecture is the simplest one that meets the requirements.

Direct Modbus TCP connection via Voltrus: one binary, one config, one maintenance point. Modbus TCP through Kepware then OPC-UA to Voltrus: two binaries, two configs, two license costs, two maintenance points, and a protocol translation layer between them that can fail independently. If the first architecture meets your requirements, the second architecture is waste.

The Pricing Reality

Let's talk about cost, because cost drives decisions in system integration more than any technical feature.

A Kepware KEPServerEX installation with Modbus TCP and Siemens S7 drivers costs approximately $2,000 to $3,500 in licensing. Add Allen-Bradley EtherNet-IP and you are at $3,500 to $5,000. Each additional driver adds cost. And Kepware runs on Windows, so add the Windows Server license if you do not already have one.

Voltrus Professional at $499 includes Modbus TCP, Siemens S7, EtherNet-IP, and MQTT. All protocols, one price, lifetime license. No per-driver costs. No Windows requirement.

If you need both, the combined cost is $499 (Voltrus) + $1,500-$5,000 (Kepware) = $2,000 to $5,500. That is still cheaper than most enterprise SCADA alternatives. But if your devices speak Modbus TCP, S7, EtherNet-IP, or MQTT natively, Voltrus alone at $499 replaces both the protocol gateway and the monitoring platform.

The Bottom Line

Kepware and Voltrus are not competitors. They are different products in different categories. Kepware is an OPC server that translates industrial protocols. Voltrus is a SCADA platform that connects to devices, visualizes data, stores trends, and triggers alerts. Comparing them directly is like comparing a network switch to a monitoring dashboard. They exist at different layers of the architecture.

The right decision depends on your project:

• If your devices speak Modbus TCP, Siemens S7, Allen-Bradley EtherNet-IP, or MQTT, Voltrus alone handles both protocol connectivity and monitoring. Kepware adds cost without adding value.
• If your devices include obscure protocols like BACnet, DNP3, or legacy serial protocols that Voltrus does not support, use Kepware for protocol translation and Voltrus for monitoring. They work together.
• If your plant already has Kepware deployed and configured, add Voltrus on top for dashboards, trends, and alerts. No need to rip out working infrastructure.
• If you are starting from scratch with Modbus TCP or S7 devices and need a complete monitoring solution, Voltrus alone at $249 to $499 is the most cost-effective path.

Stop asking "Kepware or Voltrus?" Start asking "do I need protocol translation, monitoring, or both?" The answer to that question tells you exactly which combination of products to deploy.

Frequently Asked Questions

Can Voltrus replace Kepware for Modbus TCP and Siemens S7 connectivity?

Yes. For Modbus TCP, Siemens S7, Allen-Bradley EtherNet-IP, and MQTT devices, Voltrus connects directly without needing Kepware as a protocol gateway. Voltrus also provides dashboards, trend charts, alerts, and user authentication — none of which Kepware includes. You only need Kepware alongside Voltrus if your devices use protocols Voltrus does not support natively (BACnet, DNP3, Profibus, etc.).

Does Kepware include dashboards and trend charts?

No. Kepware is an OPC server and protocol gateway. It translates industrial protocols into OPC-UA or OPC-DA for other software to consume. It does not provide dashboards, trend charts, alerts, user authentication, or data retention. If you buy Kepware expecting a SCADA system, you will have data connectivity but no way to visualize it.

When should I use both Kepware and Voltrus together?

Use both when your plant has devices using protocols Voltrus does not support natively, such as BACnet, DNP3, or legacy serial protocols. Kepware handles the protocol translation, and Voltrus provides the monitoring dashboards and alerts. You should also use both if your plant already has Kepware deployed — just add Voltrus on top as the visualization layer.

Is Kepware more expensive than Voltrus?

Yes. A Kepware KEPServerEX installation with Modbus TCP and Siemens S7 drivers costs $2,000-$3,500. Each additional protocol driver adds cost, and Kepware requires Windows. Voltrus Professional at $499 includes Modbus TCP, S7, EtherNet-IP, and MQTT in one lifetime license, and runs on Linux, Windows, or ARM.

Does Kepware run on Linux?

No. Kepware KEPServerEX is Windows-only and requires a Windows license for the host machine. Voltrus runs on Linux, Windows, and ARM-based devices including Raspberry Pi, giving you lower infrastructure costs and more deployment flexibility.

Further Reading

• Voltrus vs Ignition: An Honest Comparison for System Integrators
• Modbus TCP vs OPC-UA: Which Protocol Should Your SCADA Use?
• SCADA for Siemens S7 and Allen-Bradley: A Multi-Protocol Guide