Softwr

Manufacturing · head to head

AVEVA System Platform vs Kepware Server

AVEVA System Platform logo

AVEVA System Platform

Manufacturing

Supervisory HMI and SCADA platform, formerly sold as Wonderware System Platform

From
On request
Rated
-
Full reviewWebsite
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

The short version

  • Each has a real cost: AVEVA System Platform wonderware is no longer a name you can buy; if you have inherited documentation, purchase orders or job specifications that say Wonderware, everything has to be re-mapped to AVEVA product names before you can quote it.; 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.
  • They diverge on capability: AVEVA System Platform covers ArchestrA object model, Kepware Server covers 150-plus device drivers.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which AVEVA System Platform and Kepware Server actually diverge.

Attributes where AVEVA System Platform and Kepware Server differ
AttributeAVEVA System PlatformKepware Server
PlatformsWindowsWindows, 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 AVEVA System Platform

  • ArchestrA object model
  • InTouch HMI
  • AVEVA Historian
  • Redundancy
  • Situational awareness graphics
  • OMI
  • Alarm management
  • Connectivity

Only in Kepware Server

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

What people use each for

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

AVEVA System Platform

  • A multi-site food manufacturer standardising operator screens across plants that run different PLC brandsnot Kepware Server
  • A water utility with a decade of ArchestrA templates where rewriting to another platform cannot be justifiednot Kepware Server
  • A pharmaceutical line needing ISA-88 batch recipe handling above existing Rockwell and Siemens controllersnot Kepware Server
  • A plant modernising legacy InTouch applications without discarding the existing screens and scriptsnot Kepware Server

Kepware Server

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

Where each one falls short

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

AVEVA System Platform

  • Wonderware is no longer a name you can buy; if you have inherited documentation, purchase orders or job specifications that say Wonderware, everything has to be re-mapped to AVEVA product names before you can quote it.
  • AVEVA Flex converts licensing to a recurring subscription draw-down, so organisations that budgeted for a perpetual licence with a support percentage face a materially different cost model at renewal.
  • It is Windows only, and version compatibility between System Platform, Historian and InTouch is tight, so upgrades are coordinated projects rather than incremental patches.
  • The ArchestrA object model has a steep learning curve and small systems end up paying for structure they do not need, which is why integrators often deploy standalone InTouch instead.
  • Licence enforcement counts I/O aggressively and unexpected tag growth during commissioning can trigger a mid-project licence purchase at list price.

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.

Pricing, plan by plan

AVEVA System Platform

On request
  • AVEVA System Platform$undefined/year
    • Licensed by I/O count, client count and platform nodes
    • Sold through AVEVA Flex subscription token pool or legacy perpetual licence
    • Legacy perpetual licences carry an annual customer FIRST support fee

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

Which should you pick?

Choose AVEVA System Platform if

  • You need archestra object model.
  • You work on Windows.
  • You also want intouch hmi.
AVEVA System Platform review

Choose Kepware Server if

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

Questions people ask

Is AVEVA System Platform or Kepware Server better?
Neither clearly leads. AVEVA System Platform starts at On request and Kepware Server at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, AVEVA System Platform or Kepware Server?
AVEVA System Platform starts at On request and Kepware Server at On request.
Does AVEVA System Platform or Kepware Server run on more platforms?
AVEVA System Platform runs on Windows. Kepware Server runs on Windows, Linux.
What is AVEVA System Platform best used for?
AVEVA System Platform is most often used for a multi-site food manufacturer standardising operator screens across plants that run different plc brands, a water utility with a decade of archestra templates where rewriting to another platform cannot be justified, a pharmaceutical line needing isa-88 batch recipe handling above existing rockwell and siemens controllers, a plant modernising legacy intouch applications without discarding the existing screens and scripts. Of those, a multi-site food manufacturer standardising operator screens across plants that run different plc brands and a water utility with a decade of archestra templates where rewriting to another platform cannot be justified are not what Kepware Server is typically brought in for.
What can AVEVA System Platform do that Kepware Server cannot?
AVEVA System Platform covers ArchestrA object model, InTouch HMI, AVEVA Historian, Redundancy. Kepware Server covers 150-plus device drivers, OPC UA server, IoT Gateway, DataLogger.

Answered from the vendors’ own pages

AVEVA System Platform: Is Wonderware still sold?

No. The brand was retired; buy AVEVA System Platform, AVEVA InTouch HMI, AVEVA Historian or AVEVA Plant SCADA instead.

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.

AVEVA System Platform: Can I still buy a perpetual licence?

AVEVA steers new business to Flex subscriptions. Perpetual is increasingly restricted to existing agreements and renewals.

Kepware Server: Is a perpetual licence still available?

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

AVEVA System Platform: Do my old InTouch applications still run?

Yes, legacy InTouch applications are supported in System Platform, though the older graphics do not gain the newer situational-awareness features without rework.

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.

AVEVA System Platform: What is AVEVA Flex?

A subscription credit pool you draw against for any AVEVA product, which trades a fixed licence for a recurring balance you must keep topped up.

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.

Share

Related pages

More on AVEVA System Platform

More on Kepware Server

Keep looking

Other head to heads