Softwr

Manufacturing · head to head

Kepware Server vs Seeq

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
Seeq logo

Seeq

Manufacturing

Self-service analytics for process manufacturing time-series data sitting on top of existing historians

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.; Seeq named-user pricing suits a small core team but scales badly: a site wanting a hundred engineers with occasional access pays for a hundred licences that mostly sit idle, which is why deployments often stay artificially narrow.
  • They diverge on capability: Kepware Server covers 150-plus device drivers, Seeq covers Query in place.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Kepware Server and Seeq actually diverge.

Attributes where Kepware Server and Seeq differ
AttributeKepware ServerSeeq
PlatformsWindows, LinuxWeb, Cloud, On-premise, Windows, 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 Seeq

  • Query in place
  • Capsules
  • Asset trees
  • Seeq Data Lab
  • Organizer
  • Multi-source joins

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

Seeq

  • A pharmaceutical plant comparing hundreds of batches against a golden batch profile without exporting historian data into spreadsheetsnot Kepware Server
  • A reliability engineer investigating why a compressor trips, needing to overlay vibration, process and maintenance data across two years of historynot Kepware Server
  • Refinery process engineers building a recurring shift report that pulls live values rather than being rebuilt by hand each weeknot Kepware Server
  • A site whose data lake project has stalled and that needs engineers analysing plant history now, without waiting for an ingestion pipelinenot 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.

Seeq

  • Named-user pricing suits a small core team but scales badly: a site wanting a hundred engineers with occasional access pays for a hundred licences that mostly sit idle, which is why deployments often stay artificially narrow.
  • Seeq inherits whatever quality exists in the historian, so plants with unstructured tag names and no asset model spend real effort building asset trees in Seeq that should have been fixed upstream.
  • Certain historian connectors are charged separately, so the licence quote and the actual cost of connecting your specific data sources are two different numbers.
  • It is analysis, not control or action; findings still have to be carried into a CMMS or a control change by hand, so value depends on a workflow Seeq does not provide.
  • The product assumes competent process engineers. Organisations without that skill in-house get little from it, because Seeq deliberately does not ship prebuilt failure models the way condition monitoring vendors do.

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

Seeq

On request
  • Seeq$undefined/year
    • Licensed per named user, not per tag
    • Separate charges for certain historian connectors
    • Cloud-hosted and self-hosted deployments quoted differently

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 Seeq if

  • You need query in place.
  • You work on Web, Cloud, On-premise, Windows, Linux.
  • You also want capsules.
Seeq review

Questions people ask

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

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.

Seeq: Does Seeq store my data?

No. It queries connected historians and databases in place. Removing Seeq leaves your data exactly where it was.

Kepware Server: Is a perpetual licence still available?

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

Seeq: Who owns Seeq?

It is an independent private company in Seattle, most recently funded by a 2024 growth round led by Sixth Street. It has not been taken over by a private equity buyer.

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.

Seeq: How is it licensed?

Per named user, with some historian connectors charged separately. Nothing is published; every number comes from a quote.

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.

Seeq: Do I need a data scientist?

No, and that is the point. Workbench is aimed at process engineers. Data Lab exists for the minority who want Python.

Share

Related pages

More on Kepware Server

More on Seeq

Keep looking

Other head to heads