Softwr

Manufacturing · head to head

Kepware Server vs Rockwell FactoryTalk

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
Rockwell FactoryTalk logo

Rockwell FactoryTalk

Manufacturing

Rockwell Automation software portfolio for HMI, historian, analytics and industrial data

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.; Rockwell FactoryTalk factoryTalk is a brand, not a product, so a quote that says FactoryTalk may cover any of six separately licensed things; buyers repeatedly find that the demo they saw needed View plus Historian plus a Hub subscription.
  • They diverge on capability: Kepware Server covers 150-plus device drivers, Rockwell FactoryTalk covers FactoryTalk View SE and ME.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Kepware Server and Rockwell FactoryTalk actually diverge.

Attributes where Kepware Server and Rockwell FactoryTalk differ
AttributeKepware ServerRockwell FactoryTalk
PlatformsWindows, LinuxWindows, Linux, Web, Cloud

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 Rockwell FactoryTalk

  • FactoryTalk View SE and ME
  • FactoryTalk Historian
  • FactoryTalk Optix
  • FactoryTalk Batch
  • FactoryTalk Hub
  • Native Logix tags

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 Rockwell FactoryTalk
  • Publishing CNC machine state from FANUC and Haas controls to an OEE system over MQTTnot Rockwell FactoryTalk
  • Bridging legacy serial Modbus devices into an OPC UA architecture during a phased controller replacementnot Rockwell FactoryTalk
  • Running redundant collection servers so a cloud analytics pipeline does not lose data during Windows patchingnot Rockwell FactoryTalk

Rockwell FactoryTalk

  • A plant standardised on ControlLogix that needs supervisory HMI without building and maintaining an OPC layer between controller and screennot Kepware Server
  • A hybrid manufacturer needing ISA-88 batch execution audited against recipes, where FactoryTalk Batch is already validated in the industrynot Kepware Server
  • Consolidating machine-level HMI screens across many Allen-Bradley lines under one tag model and one alarm schemenot Kepware Server
  • Adding a plant historian quickly where the site has Rockwell distribution support but no PI administrator on staffnot 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.

Rockwell FactoryTalk

  • FactoryTalk is a brand, not a product, so a quote that says FactoryTalk may cover any of six separately licensed things; buyers repeatedly find that the demo they saw needed View plus Historian plus a Hub subscription.
  • Licensing units differ per product, tags for Historian, display tags and clients for View, another scheme for Optix, which makes forecasting the cost of a plant expansion genuinely hard.
  • The migration of products onto FactoryTalk Hub subscriptions converts what used to be a perpetual licence into an annual payment where lapsing stops the software, changing a capital purchase into an operating one you cannot exit.
  • Value drops sharply outside an Allen-Bradley estate; against a Siemens or Mitsubishi PLC you are back to OPC UA and lose the main reason to buy FactoryTalk at all.
  • There is no public price list and buying is through distribution, so two plants of identical size in the same company can pay materially different amounts depending on when and how they negotiated.

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

Rockwell FactoryTalk

On request
  • FactoryTalk$undefined/year
    • Sold through Rockwell distribution, not direct or self-service
    • View licensed by display tag count and client seats
    • Historian licensed by tag count

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 Rockwell FactoryTalk if

  • You need factorytalk view se and me.
  • You work on Windows, Linux, Web, Cloud.
  • You also want factorytalk historian.
Rockwell FactoryTalk review

Questions people ask

Is Kepware Server or Rockwell FactoryTalk better?
Neither clearly leads. Kepware Server starts at On request and Rockwell FactoryTalk at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Kepware Server or Rockwell FactoryTalk?
Kepware Server starts at On request and Rockwell FactoryTalk at On request.
Does Kepware Server or Rockwell FactoryTalk run on more platforms?
Kepware Server runs on Windows, Linux. Rockwell FactoryTalk runs on Windows, Linux, Web, Cloud.
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 Rockwell FactoryTalk is typically brought in for.
What can Kepware Server do that Rockwell FactoryTalk cannot?
Kepware Server covers 150-plus device drivers, OPC UA server, IoT Gateway, DataLogger. Rockwell FactoryTalk covers FactoryTalk View SE and ME, FactoryTalk Historian, FactoryTalk Optix, FactoryTalk Batch.

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.

Rockwell FactoryTalk: Is FactoryTalk Historian the same as AVEVA PI?

It is built on the PI engine under an OEM arrangement, tuned for Rockwell integration. If you already run PI enterprise-wide, buying Historian too usually duplicates a system you have.

Kepware Server: Is a perpetual licence still available?

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

Rockwell FactoryTalk: Can I still buy FactoryTalk perpetually?

Some products yes, but the direction is toward FactoryTalk Hub subscriptions. Confirm per product before assuming a capital purchase is available.

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.

Rockwell FactoryTalk: Does FactoryTalk work with non-Rockwell PLCs?

Yes, through OPC UA and drivers, but the native tag browse advantage disappears and the case for FactoryTalk over a cheaper independent SCADA weakens.

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.

Rockwell FactoryTalk: Where do I find pricing?

You cannot without a distributor. Rockwell publishes no list pricing for the FactoryTalk portfolio.

Share

Related pages

More on Kepware Server

More on Rockwell FactoryTalk

Keep looking

Other head to heads