VTScada, developed by Trihedral (a Delta Electronics company), has one of the most loyal user bases in SCADA — especially in water and wastewater, where its all-in-one installer and low-maintenance historian have earned decades of goodwill. So how does it stack up against a managed cloud platform built with an oil and gas backbone? This is the honest, dimension-by-dimension comparison — written by Merobix, so read it with that context, and note that we concede the categories VTScada genuinely wins.
Choose VTScada if you are a municipal water or wastewater utility with staff (or a trusted integrator) comfortable running Windows servers, you want a perpetual license you own forever with publicly listed pricing, and you value the industry's simplest all-in-one install — HMI, historian, alarming, and thin clients in one package with nothing extra to buy.
Choose Merobix if you want a managed cloud deployment that goes live in 3–5 days with a 99.9% uptime SLA and no servers to run — or a vendor-supported on-premise deployment with hot standby redundancy for air-gapped networks. Merobix is the stronger fit for oil and gas and distributed operations, for teams that need enterprise integrations like SAP, ServiceNow, PagerDuty, and Kafka out of the box, and for anyone who wants PLC programming and UL 508A panel fabrication from the same team that runs the SCADA.
Neither verdict is a throwaway. VTScada earned its reputation honestly, and pretending otherwise would make everything else on this page less credible. The rest of the article explains where each platform's design decisions come from and what they cost you in practice.
| Dimension | Merobix | VTScada (Trihedral) |
|---|---|---|
| Architecture | One platform, two homes: managed cloud or on-premise on your servers/VMs | Windows application, self-hosted on servers you own and maintain |
| Deployment model | Managed cloud live in 3–5 days; on-premise supports air-gapped networks with full data residency | Famously simple all-in-one installer — but you build, patch, and back up the environment |
| Licensing model | Custom-quoted subscription plans (Starter, Professional, Enterprise); no per-tag fees | Publicly listed perpetual licenses tiered by tag count, plus annual support; free tier for very small systems |
| Protocol support | 20 drivers across 7 families: Modbus TCP/RTU, OPC UA/DA, EtherNet/IP, Siemens S7, DNP3, BACnet, MQTT Sparkplug B, IEC 60870-5-104, PROFINET, HART-IP | Broad built-in driver library with strong water-telemetry coverage (Modbus, DNP3, OPC, and others) |
| Alarming | SMS and email delivery in under 30 seconds, included in every plan | Integrated alarm management and notifications; deep roots in water-utility alarm callout practice |
| Historian | Included; historian federation across sites on Enterprise | Proprietary built-in historian, widely praised for simplicity and automatic synchronization |
| Integrations | Enterprise connectors: SAP, Maximo, ServiceNow, PagerDuty, AWS IoT, Azure IoT, Kafka, Tableau | Scripting and standard interfaces; enterprise connectors are typically custom-built projects |
| Security & identity | Enterprise identity stack: LDAP, SAML, RADIUS, FIDO2; SIEM integration | Application security on the Windows platform; network hardening and remote-access exposure are your responsibility |
| Redundancy & uptime | 99.9% cloud SLA; hot standby included in Enterprise on-premise | Well-regarded redundant server synchronization; actual uptime depends on your infrastructure |
| Support model | Direct vendor engineering support; PLC programming and UL 508A / C1D2 panels from the same team | Vendor support with a loyal integrator network; field services come from third parties |
VTScada's signature move is the single installer. One download puts HMI development, runtime, historian, alarm management, reporting, and thin-client serving on a Windows machine — no module shopping, no separate historian product, no license-key scavenger hunt. Among traditional on-premise SCADA packages, it is probably the fastest path from download to a running screen, and users have loved it for exactly that reason for decades.
But installation is maybe five percent of the life of a SCADA system. The other ninety-five percent is operating it: Windows patching, antivirus exceptions, certificate renewals, backups, restore tests, redundant-pair failover drills, and — the big one in 2026 — safely exposing remote access without exposing the plant. All of that stays on your desk with VTScada, because the product is self-hosted by design.
Merobix starts from the opposite premise: the fastest installer is the one you never run. On the managed cloud deployment, Merobix operates the platform and has customers live in 3–5 days — tag database, alarm setpoints, dashboards, and users configured by our engineers. For operations that cannot or will not put SCADA in the cloud, the same platform deploys on-premise on your servers or VMs, including fully air-gapped networks with complete data residency. The full trade-off is covered in our cloud vs on-premise SCADA comparison — the short version is that with Merobix you choose the home; with VTScada, self-hosting is the only model.
Give Trihedral credit: VTScada publishes its pricing. Licenses are perpetual and tiered by tag count, annual support is optional and predictable, and there is even a free edition for very small systems that has introduced a generation of water operators to the product. If your organization's procurement culture demands a printed price list and a one-time capital purchase, VTScada fits that culture unusually well — see our guide to SCADA licensing models for how rare that is.
The trade-off of tag-tier licensing is the tier boundary. Growth — more sites, more instrumentation, higher-resolution data — eventually pushes you across a tag threshold and into a license upgrade, and the perpetual license does not cover the servers, Windows licenses, and staff time underneath it. Merobix prices the other way around: custom-quoted subscription plans (Starter, Professional, and Enterprise) that include the platform, hosting on cloud plans, alarming, and the historian, with no per-tag fees to engineer around. Which model is cheaper depends entirely on your size, growth curve, and how you account for internal IT labor — we would rather quote your actual operation than pretend one number fits everyone.
VTScada's driver library grew up in water telemetry, and it shows in a good way: Modbus, DNP3, OPC, and the radio-and-RTU patterns municipal systems depend on are well covered and battle-tested. For a lift-station network or a treatment plant, its protocol coverage is rarely the deciding factor.
Merobix ships 20 protocol drivers across 7 families — Modbus TCP/RTU, OPC UA/DA, EtherNet/IP, Siemens S7, DNP3, BACnet, MQTT Sparkplug B, IEC 60870-5-104, PROFINET, and HART-IP among them. Two of those matter especially for anyone comparing the platforms in 2026: MQTT Sparkplug B, which is becoming the backbone of modern IIoT architectures, and IEC 60870-5-104 for utility telecontrol. And the bigger separation is above the protocol layer: the Merobix Enterprise plan connects SCADA data to SAP, Maximo, ServiceNow, PagerDuty, AWS IoT, Azure IoT, Kafka, and Tableau as supported integrations rather than scripting projects. If your alarms should open ServiceNow tickets and your production data should land in a Kafka topic, that is configuration on Merobix and custom development on most traditional packages, VTScada included.
Search data brought many readers here via "WinCC vs VTScada remote access," so let us answer it directly. Between those two, VTScada is generally regarded as the easier platform: browser-based thin clients are part of the core product, so putting an operator screen on a phone or a laptop is a configuration task, not a licensing negotiation. Siemens WinCC typically reaches the same destination through separately licensed web add-ons and more configuration effort. If the choice is strictly WinCC vs VTScada for remote access, VTScada has the cleaner story.
But both share the harder problem: they are self-hosted, so "remote access" really means "exposing your own servers to the internet safely." VPN concentrators, DMZ design, firewall rules, certificate management, patch urgency — the thin client is easy; the perimeter around it is not, and in critical infrastructure it is the part that keeps security teams up at night. Our security architecture page details the alternative model: with Merobix cloud, there is no customer-managed perimeter to engineer. Operators reach the platform from any browser, Enterprise plans authenticate against your existing LDAP, SAML, RADIUS, or FIDO2 infrastructure, and security events export to your SIEM. Remote access stops being a project and becomes a login.
These are real advantages, not polite gestures:
Replacing a working VTScada system is not always the right move, so it is worth separating the two paths.
Full migration is less disruptive than most teams fear because nothing changes in the field. Merobix connects to the same PLCs and RTUs over the same protocols — Modbus TCP/RTU, DNP3, OPC UA, EtherNet/IP, Siemens S7, BACnet — so controllers are not reprogrammed. Tag lists and alarm setpoints are migrated, and both systems can poll the same devices in parallel during commissioning, which means the old system stays live until the new one has proven itself. There is no blind window. Our SCADA migration guide walks through the sequencing in detail.
Coexistence is often the smarter first step, particularly for utilities. A common pattern worth evaluating: keep VTScada running the treatment plant it already runs well, and put new, remote, or acquired assets — outlying lift stations, wellfields, oil and gas facilities that came with an acquisition — on Merobix cloud, where a 3–5 day go-live beats extending a self-hosted system's VPN perimeter to another county. Enterprise historian federation can then present multiple sites' history as one queryable whole. Migration becomes a decision you make with evidence, on your schedule, instead of a leap.
For the wider field of options beyond these two platforms, our SCADA comparison hub collects every head-to-head we have published, including Merobix vs Ignition. Water-sector readers should also see our water utility SCADA monitoring guide.
It depends on the operation. VTScada is a genuinely excellent all-in-one on-premise SCADA package — one installer covers HMI, historian, alarming, and thin clients, and it has decades of pedigree in municipal water and wastewater telemetry. Merobix is the stronger fit when you want a managed cloud deployment that goes live in 3–5 days, a vendor-backed 99.9% uptime SLA, alarm delivery in under 30 seconds, enterprise integrations such as SAP, ServiceNow, PagerDuty, and Kafka, or bundled PLC programming and UL 508A panel fabrication. Many water utilities are well served by VTScada; distributed oil and gas operations and teams without server infrastructure are usually better served by Merobix.
Nothing beats VTScada at what it was designed for: a self-contained, perpetually licensed Windows SCADA application for water and wastewater utilities. Platforms that beat it do so on different terms. Merobix offers something VTScada does not — a fully managed cloud deployment, live in 3–5 days, with a 99.9% uptime SLA, sub-30-second SMS and email alarms, and out-of-the-box enterprise integrations. If your pain points are server maintenance, remote access security, or connecting SCADA data to systems like SAP, Maximo, or PagerDuty, a cloud-hosted platform like Merobix is the most meaningful upgrade.
VTScada is generally regarded as the easier of the two for remote access: browser-based thin clients are part of the core product, so publishing an operator screen to a phone or laptop is straightforward. Siemens WinCC typically requires separately licensed web add-ons and more configuration to reach the same result. Both, however, are self-hosted — remote access means exposing your own servers through VPNs, firewalls, and DMZ architecture that your team must build and maintain. A cloud-hosted platform like Merobix removes that burden entirely: the platform is reached securely from any browser, with no server exposure for your team to engineer.
Yes. Merobix speaks the same field protocols VTScada deployments rely on — Modbus TCP/RTU, DNP3, OPC UA, EtherNet/IP, Siemens S7, and BACnet are among its 20 protocol drivers — so existing PLCs and RTUs are not reprogrammed. Tag lists and alarm setpoints are migrated, and the two systems can run in parallel against the same field devices during the transition, so there is no monitoring gap. For operators that must stay on their own hardware, Merobix also deploys on-premise on customer servers or VMs, including air-gapped networks with full data residency.
Several things, genuinely. Its single-installer packaging is among the simplest in the industry — historian, alarming, reporting, and thin clients arrive in one setup with no modules to assemble. Its integrated historian and built-in application version control are widely praised for being low-maintenance. It publishes its license pricing, offers a free tier for very small systems, and has one of the deepest track records in municipal water and wastewater telemetry. If you are a water utility with staff who are comfortable running Windows servers and you want a perpetual license you control forever, VTScada is a very strong choice.
Cloud live in 3–5 days or on-premise on your hardware — custom-quoted plans with no per-tag fees, and PLC programming plus panel fabrication from the same team.