Softwr

Manufacturing · head to head

Kepware Server vs Nanoprecise Sci Corp

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
Nanoprecise Sci Corp logo

Nanoprecise Sci Corp

Manufacturing

Battery-powered six-in-one condition monitoring sensors with automated fault diagnosis

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.; Nanoprecise Sci Corp the hardware and analytics are inseparable, so you cannot bring your own accelerometers or keep the platform if you change sensor vendor, and every expansion of coverage is a hardware purchase as well as a subscription increase.
  • They diverge on capability: Kepware Server covers 150-plus device drivers, Nanoprecise Sci Corp covers Six-parameter sensor.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Kepware Server and Nanoprecise Sci Corp actually diverge.

Attributes where Kepware Server and Nanoprecise Sci Corp differ
AttributeKepware ServerNanoprecise Sci Corp
PlatformsWindows, LinuxWeb, Cloud, iOS, Android

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 Nanoprecise Sci Corp

  • Six-parameter sensor
  • Automated fault classification
  • Remaining useful life estimate
  • Multi-connectivity
  • Long battery life
  • Energy and carbon reporting

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

Nanoprecise Sci Corp

  • A plant with no vibration analyst that needs a named fault rather than a spectrum to interpretnot Kepware Server
  • Monitoring rotating equipment in areas with no power or network cabling, where a battery sensor on LTE avoids an electrical projectnot Kepware Server
  • A mining site tracking conveyor and pump condition across a large area where walkaround routes are impracticalnot Kepware Server
  • A facilities team wanting motor energy waste and condition from the same device to justify the spend on two groundsnot 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.

Nanoprecise Sci Corp

  • The hardware and analytics are inseparable, so you cannot bring your own accelerometers or keep the platform if you change sensor vendor, and every expansion of coverage is a hardware purchase as well as a subscription increase.
  • Per-asset subscription costs scale linearly with the number of monitored machines, so full coverage of a large rotating asset population becomes expensive in a way a traditional route-based programme does not.
  • Nanoprecise is a small venture-funded company, so a buyer standardising a whole estate on its sensors is taking a supplier continuity risk that a Baker Hughes or SKF purchase does not carry.
  • Automated fault classification is only as good as the model for your specific machine type, and unusual or slow-speed equipment is where these systems are weakest, exactly where a human analyst would still be needed.
  • Nothing is published on pricing, hardware cost, gateway requirements or contract length, so total cost for a realistic deployment cannot be estimated without a sales engagement.

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

Nanoprecise Sci Corp

On request
  • MachineDoctor$undefined/month
    • Subscription priced per monitored asset
    • MachineDoctor sensor hardware required per asset
    • Gateway hardware required for WiFi and LoRa deployments

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 Nanoprecise Sci Corp if

  • You need six-parameter sensor.
  • You work on Web, Cloud, iOS, Android.
  • You also want automated fault classification.
Nanoprecise Sci Corp review

Questions people ask

Is Kepware Server or Nanoprecise Sci Corp better?
Neither clearly leads. Kepware Server starts at On request and Nanoprecise Sci Corp at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Kepware Server or Nanoprecise Sci Corp?
Kepware Server starts at On request and Nanoprecise Sci Corp at On request.
Does Kepware Server or Nanoprecise Sci Corp run on more platforms?
Kepware Server runs on Windows, Linux. Nanoprecise Sci Corp runs on Web, Cloud, iOS, Android.
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 Nanoprecise Sci Corp is typically brought in for.
What can Kepware Server do that Nanoprecise Sci Corp cannot?
Kepware Server covers 150-plus device drivers, OPC UA server, IoT Gateway, DataLogger. Nanoprecise Sci Corp covers Six-parameter sensor, Automated fault classification, Remaining useful life estimate, Multi-connectivity.

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.

Nanoprecise Sci Corp: Can I use my own vibration sensors?

No. The platform is built around the MachineDoctor sensor and third-party sensor data is not a supported first-class input.

Kepware Server: Is a perpetual licence still available?

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

Nanoprecise Sci Corp: Do I need a gateway?

For WiFi and LoRa deployments yes. LTE sensors report directly but carry a connectivity cost.

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.

Nanoprecise Sci Corp: Does it tell me what is wrong or just that something is wrong?

It classifies the fault type and estimates remaining useful life, which is the main reason plants without a vibration analyst choose it.

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.

Nanoprecise Sci Corp: How is it priced?

Per monitored asset on subscription, plus sensor and gateway hardware. Nothing is published; expect a multi-year agreement.

Share

Related pages

More on Kepware Server

More on Nanoprecise Sci Corp

Keep looking

Other head to heads