Softwr

Manufacturing · head to head

ABB 800xA vs Kepware Server

ABB 800xA logo

ABB 800xA

Manufacturing

Distributed control system and process automation platform for continuous and hybrid process plants

From
On request
Rated
-
Kepware Server logo

Kepware Server

Manufacturing

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

From
On request
Rated
-

The short version

  • Each has a real cost: ABB 800xA licensing is by I/O count, controller count and workplace clients, and none of it is published, so two plants of similar size can be quoted very differently with no external benchmark to argue against.; 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: ABB 800xA covers Extended Automation, 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 ABB 800xA and Kepware Server actually diverge.

Attributes where ABB 800xA and Kepware Server differ
AttributeABB 800xAKepware 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 ABB 800xA

  • Extended Automation
  • AC 800M controllers
  • Connectivity servers
  • Safety integration
  • IEC 61850 electrical
  • Batch management
  • Information management
  • Asset optimisation

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.

ABB 800xA

  • A refinery replacing operator consoles and control room infrastructure while keeping working field controllers in placenot Kepware Server
  • A pulp and paper mill consolidating process, electrical and safety monitoring into a single operator workplacenot Kepware Server
  • A mining operation that needs SIL 3 safety functions on the same network as process control rather than a separate safety systemnot Kepware Server
  • A marine or offshore platform where ABB already supplies the electrical distribution and IEC 61850 integration removes a second systemnot Kepware Server

Kepware Server

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

Where each one falls short

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

ABB 800xA

  • Licensing is by I/O count, controller count and workplace clients, and none of it is published, so two plants of similar size can be quoted very differently with no external benchmark to argue against.
  • Engineering and commissioning typically cost more than the software and controller hardware together, and that share is not visible in the initial ABB quotation, which prices the system rather than the project.
  • It is Windows only for servers and workplaces, so the operating system lifecycle drives forced upgrade cycles that have nothing to do with your process.
  • Once configured, the aspect object model and the specific integrator conventions used make handing the system to a different service provider expensive; ABB service contracts are effectively sticky.
  • Software maintenance is an annual contract on top of the licence and lapsing it means you cannot take version upgrades, so the system quietly ages out of security support if the plant skips renewals to save money.

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

ABB 800xA

On request
  • ABB Ability System 800xA$undefined/year
    • Licensed by I/O count, controller count and workplace clients
    • Sold as a project through ABB or a certified partner
    • Annual software maintenance contract priced separately

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 ABB 800xA if

  • You need extended automation.
  • You work on Windows.
  • You also want ac 800m controllers.

Choose Kepware Server if

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

Questions people ask

Is ABB 800xA or Kepware Server better?
Neither clearly leads. ABB 800xA 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, ABB 800xA or Kepware Server?
ABB 800xA starts at On request and Kepware Server at On request.
Does ABB 800xA or Kepware Server run on more platforms?
ABB 800xA runs on Windows. Kepware Server runs on Windows, Linux.
What is ABB 800xA best used for?
ABB 800xA is most often used for a refinery replacing operator consoles and control room infrastructure while keeping working field controllers in place, a pulp and paper mill consolidating process, electrical and safety monitoring into a single operator workplace, a mining operation that needs sil 3 safety functions on the same network as process control rather than a separate safety system, a marine or offshore platform where abb already supplies the electrical distribution and iec 61850 integration removes a second system. Of those, a refinery replacing operator consoles and control room infrastructure while keeping working field controllers in place and a pulp and paper mill consolidating process, electrical and safety monitoring into a single operator workplace are not what Kepware Server is typically brought in for.
What can ABB 800xA do that Kepware Server cannot?
ABB 800xA covers Extended Automation, AC 800M controllers, Connectivity servers, Safety integration. Kepware Server covers 150-plus device drivers, OPC UA server, IoT Gateway, DataLogger.

Answered from the vendors’ own pages

ABB 800xA: Is 800xA sold as a perpetual licence?

Yes, the system licence is perpetual, but a separate annual software maintenance agreement is required to receive updates and version upgrades.

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.

ABB 800xA: Can 800xA control non-ABB field hardware?

Yes. Connectivity servers front third-party PLC and DCS systems and legacy ABB families, which is the main reason it wins brownfield projects.

Kepware Server: Is a perpetual licence still available?

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

ABB 800xA: Does it replace a separate electrical SCADA?

It can. IEC 61850 substation integration is native, so many plants drop a separate electrical monitoring system.

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.

ABB 800xA: What is the realistic implementation timeline?

A full plant migration is measured in years, not months; phased cutovers of one unit at a time are the norm.

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

Other head to heads