Softwr

Manufacturing · head to head

Kepware Server vs Siemens WinCC Unified

Kepware Server logo

Kepware Server

Manufacturing

Industrial connectivity server translating 150-plus PLC protocols into OPC UA, formerly KEPServerEX

From
On request
Rated
-
Full reviewWebsite
Siemens WinCC Unified logo

Siemens WinCC Unified

Manufacturing

Siemens web-based HMI and SCADA platform, licensed by PowerTag count inside TIA Portal

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Kepware Server the base server is the small part of the bill; driver suites are priced by protocol family, and a mixed-vendor plant buys several, which is how a connectivity layer alone reaches tens of thousands of dollars.; Siemens WinCC Unified licensing counts PowerTags, and archived tags are licensed separately from displayed tags, so a project that adds historian logging late can breach a tier and trigger an unbudgeted step-up purchase.
  • They diverge on capability: Kepware Server covers 150-plus device drivers, Siemens WinCC Unified covers TIA Portal engineering.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Kepware Server and Siemens WinCC Unified actually diverge.

Attributes where Kepware Server and Siemens WinCC Unified differ
AttributeKepware ServerSiemens WinCC Unified
PlatformsWindows, LinuxWindows, Web, Linux

Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated), category (Manufacturing).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Kepware Server

  • 150-plus device drivers
  • OPC UA server
  • IoT Gateway
  • DataLogger
  • Redundancy Master
  • Security Policies
  • Configuration API
  • Kepware Edge

Only in Siemens WinCC Unified

  • TIA Portal engineering
  • HTML5 runtime
  • PowerTag licensing tiers
  • Unified Comfort Panels
  • Parameter Control
  • Performance Insight
  • JavaScript scripting
  • OPC UA server and client

What people use each for

The jobs each tool is most often brought in to do.

Kepware Server

  • Feeding a historian from a mixed plant of Allen-Bradley and Siemens PLCs without writing per-protocol driversnot Siemens WinCC Unified
  • Publishing CNC machine state from FANUC and Haas controls to an OEE system over MQTTnot Siemens WinCC Unified
  • Bridging legacy serial Modbus devices into an OPC UA architecture during a phased controller replacementnot Siemens WinCC Unified
  • Running redundant collection servers so a cloud analytics pipeline does not lose data during Windows patchingnot Siemens WinCC Unified

Siemens WinCC Unified

  • A machine builder standardising on S7-1500 who wants HMI screens engineered in the same project as the PLC codenot Kepware Server
  • Replacing a WinCC V7 plant SCADA before the 2027 support cut-off without changing controller vendornot Kepware Server
  • A line supervisory system where operators and supervisors need browser access from tablets with no client software rolloutnot Kepware Server
  • A plant already committed to the TIA Portal toolchain, where the cost of a rival SCADA is the second engineering environment and the second set of skills rather than the licencenot Kepware Server

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Kepware Server

  • The base server is the small part of the bill; driver suites are priced by protocol family, and a mixed-vendor plant buys several, which is how a connectivity layer alone reaches tens of thousands of dollars.
  • KEPServerEX to Kepware Server 7 is a migration rather than an in-place upgrade, and driver entitlements do not always transfer cleanly, so budget for revalidating every channel.
  • The full driver portfolio is Windows-only; the Linux product, Kepware Edge, supports a subset of drivers and is subscription-licensed by tag count, so an edge-first architecture cannot simply reuse the Windows configuration.
  • Three names have been in circulation for the same lineage, and quotes, forum answers and integrator experience still mix KEPServerEX, ThingWorx Kepware Server and Kepware Server, which produces mismatched proposals.
  • It is a translation layer with no storage, contextualisation or visualisation of its own, so it is always an addition to a historian or platform purchase rather than a substitute for one.

Siemens WinCC Unified

  • Licensing counts PowerTags, and archived tags are licensed separately from displayed tags, so a project that adds historian logging late can breach a tier and trigger an unbudgeted step-up purchase.
  • There is no migration tool that converts a WinCC V7 project to Unified, so leaving the classic line before its 2027 support end means rebuilding screens, scripts and alarm configuration by hand.
  • Scripting moved from VBScript to JavaScript, which invalidates the script libraries in-house engineers accumulated over a decade on classic WinCC.
  • It is effectively bound to the Siemens controller stack; connecting Rockwell or Mitsubishi PLCs works through OPC UA but loses the shared tag database that is the main reason to buy it.
  • Three unrelated products share the WinCC name, and buyers who specify WinCC without saying Unified, V7 or OA regularly receive quotes for the wrong platform with different licensing and a different contractor pool.

Pricing, plan by plan

Kepware Server

On request
  • Kepware Server$undefined/year
    • Base server as a perpetual licence with annual maintenance, or subscription
    • Driver suites priced by protocol family and bought separately from the server
    • Advanced plug-ins such as IoT Gateway, DataLogger and Redundancy Master licensed individually

Siemens WinCC Unified

On request
  • WinCC Unified$undefined/year
    • Engineering licence per seat within TIA Portal
    • Runtime licensed in PowerTag tiers, from 100 tags to unlimited
    • Archived tags licensed separately from displayed process tags

Which should you pick?

Choose Kepware Server if

  • You need 150-plus device drivers.
  • You work on Windows, Linux.
  • You also want opc ua server.
Kepware Server review

Choose Siemens WinCC Unified if

  • You need tia portal engineering.
  • You work on Windows, Web, Linux.
  • You also want html5 runtime.
Siemens WinCC Unified review

Questions people ask

Is Kepware Server or Siemens WinCC Unified better?
Neither clearly leads. Kepware Server starts at On request and Siemens WinCC Unified at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Kepware Server or Siemens WinCC Unified?
Kepware Server starts at On request and Siemens WinCC Unified at On request.
Does Kepware Server or Siemens WinCC Unified run on more platforms?
Kepware Server runs on Windows, Linux. Siemens WinCC Unified runs on Windows, Web, Linux.
What is Kepware Server best used for?
Kepware Server is most often used for feeding a historian from a mixed plant of allen-bradley and siemens plcs without writing per-protocol drivers, publishing cnc machine state from fanuc and haas controls to an oee system over mqtt, bridging legacy serial modbus devices into an opc ua architecture during a phased controller replacement, running redundant collection servers so a cloud analytics pipeline does not lose data during windows patching. Of those, feeding a historian from a mixed plant of allen-bradley and siemens plcs without writing per-protocol drivers and publishing cnc machine state from fanuc and haas controls to an oee system over mqtt are not what Siemens WinCC Unified is typically brought in for.
What can Kepware Server do that Siemens WinCC Unified cannot?
Kepware Server covers 150-plus device drivers, OPC UA server, IoT Gateway, DataLogger. Siemens WinCC Unified covers TIA Portal engineering, HTML5 runtime, PowerTag licensing tiers, Unified Comfort Panels.

Answered from the vendors’ own pages

Kepware Server: Is KEPServerEX discontinued?

The name is. KEPServerEX and ThingWorx Kepware Server have been unified into Kepware Server, currently version 7, and the older names are being retired.

Siemens WinCC Unified: Should I buy WinCC Unified or WinCC V7?

Unified, for any new project. V7 and V8 receive no new features and support ends in 2027.

Kepware Server: Is a perpetual licence still available?

Yes for the Windows server, with annual maintenance. Kepware Edge on Linux is subscription-only.

Siemens WinCC Unified: Is WinCC OA the same product?

No. WinCC OA came from ETM, has its own engineering environment and licensing, and is aimed at very large distributed systems. It shares only the brand.

Kepware Server: What drives the price?

The number and type of driver suites, not the number of tags on the Windows product. Kepware Edge is priced by tag count.

Siemens WinCC Unified: What is a PowerTag?

An externally connected process variable in the runtime. Internal tags do not count, but archived tags are licensed separately from displayed ones.

Kepware Server: Can I evaluate it before buying?

Yes. The runtime works for two hours at a time without a licence, indefinitely, which is enough to prove connectivity but not to run production.

Siemens WinCC Unified: Can operators use it from a browser without installing anything?

Yes, the runtime is HTML5, but concurrent browser clients need WebUX or Unified client licences.

Share

Related pages

More on Kepware Server

More on Siemens WinCC Unified

Keep looking

Other head to heads