Manufacturing · head to head
Augury vs Kepware Server

Augury
Manufacturing
Machine health monitoring sold as a per-machine annual service including sensors, installation and analyst diagnostics
- From
- On request
- Rated
- -

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: Augury the per-machine annual fee never stops, so over a five to eight year horizon the total exceeds buying sensors and software outright and running the programme yourself.; 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: Augury covers Halo sensors, 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 Augury and Kepware Server actually diverge.
| Attribute | Augury | Kepware Server |
|---|---|---|
| Platforms | Web, iOS, Android | 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 Augury
- Halo sensors
- Diagnostics as a Service
- Named fault diagnosis
- Process Health
- CMMS integration
- Installation included
- Fleet views
- Unlimited users
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.
Augury
- A food plant with 200 similar motors and pumps and no vibration analyst on staffnot Kepware Server
- A multi-site manufacturer that needs one reliability picture across plants without standardising their maintenance teamsnot Kepware Server
- An operator whose capex budget will not approve sensor hardware but whose opex budget will approve a servicenot Kepware Server
- A site trying to move from calendar-based motor overhauls to condition-based intervals with defensible evidencenot Kepware Server
Kepware Server
- Feeding a historian from a mixed plant of Allen-Bradley and Siemens PLCs without writing per-protocol driversnot Augury
- Publishing CNC machine state from FANUC and Haas controls to an OEE system over MQTTnot Augury
- Bridging legacy serial Modbus devices into an OPC UA architecture during a phased controller replacementnot Augury
- Running redundant collection servers so a cloud analytics pipeline does not lose data during Windows patchingnot Augury
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Augury
- The per-machine annual fee never stops, so over a five to eight year horizon the total exceeds buying sensors and software outright and running the programme yourself.
- Coverage is aimed at standard rotating equipment; reciprocating compressors, very low-speed machinery and non-rotating assets are poorly served, so you still need a second monitoring approach.
- Diagnoses depend on Augurys analysts, which means the quality of your programme is set by a vendor queue you do not control and turnaround is not something you can escalate internally.
- The sensors and the analytics are one system, so leaving Augury means removing the hardware and starting again; there is no path to keep the sensors and change the software.
- Pricing is unpublished and negotiated per fleet, so buyers have no benchmark and comparable plants can pay materially different per-machine rates.
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
Augury
On request- Machine Health$undefined/year
- Flat annual fee per monitored machine
- Sensors, gateway, connectivity and installation included
- Unlimited users and unlimited diagnostic reviews
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 Augury if
- You need halo sensors.
- You work on Web, iOS, Android.
- You also want diagnostics as a service.
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 Augury or Kepware Server better?
- Neither clearly leads. Augury 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, Augury or Kepware Server?
- Augury starts at On request and Kepware Server at On request.
- Does Augury or Kepware Server run on more platforms?
- Augury runs on Web, iOS, Android. Kepware Server runs on Windows, Linux.
- What is Augury best used for?
- Augury is most often used for a food plant with 200 similar motors and pumps and no vibration analyst on staff, a multi-site manufacturer that needs one reliability picture across plants without standardising their maintenance teams, an operator whose capex budget will not approve sensor hardware but whose opex budget will approve a service, a site trying to move from calendar-based motor overhauls to condition-based intervals with defensible evidence. Of those, a food plant with 200 similar motors and pumps and no vibration analyst on staff and a multi-site manufacturer that needs one reliability picture across plants without standardising their maintenance teams are not what Kepware Server is typically brought in for.
- What can Augury do that Kepware Server cannot?
- Augury covers Halo sensors, Diagnostics as a Service, Named fault diagnosis, Process Health. Kepware Server covers 150-plus device drivers, OPC UA server, IoT Gateway, DataLogger.
Answered from the vendors’ own pages
Augury: Do I buy the sensors?
No. Sensors, gateways, connectivity and installation are included in the per-machine annual fee.
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.
Augury: Is there a per-user licence?
No. The web application allows unlimited users; the meter is monitored machines.
Kepware Server: Is a perpetual licence still available?
Yes for the Windows server, with annual maintenance. Kepware Edge on Linux is subscription-only.
Augury: Who does the diagnosis?
Machine-learning models flag issues and Augury vibration analysts review them before a finding is released to you.
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.
Augury: What happens if we cancel?
The sensors are part of the service and monitoring stops; you do not retain a usable standalone system.
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.
Related pages
More on Kepware Server
Other head to heads
- Augury vs KCF Technologies
- Augury vs SKF Enlight Centre
- Augury vs Sensemore
- Augury vs Waites Sensor Technologies
- Augury vs Nanoprecise Sci Corp
- Augury vs Erbessd Instruments
- Augury vs PROGNOST Systems
- Augury vs Petasense
- Augury vs MOVUS
- Augury vs Samotics
- Augury vs Poseidon Systems
- Augury vs eMaint
- Augury vs ABB 800xA
- Augury vs AVEVA System Platform
- Augury vs Hippo CMMS
- Augury vs Rockwell FactoryTalk
- Augury vs 3YOURMIND
- Augury vs AMFG
- Augury vs Ignition
- Augury vs Litmus Edge
- Augury vs Guidewheel
- Augury vs Oden Technologies
- Augury vs Aras Innovator
- Augury vs GENESIS Version 11
- Augury vs Markforged Eiger
- Augury vs Materialise Magics
- Augury vs OpenBOM
- Augury vs Oqton
- Kepware Server vs KCF Technologies
- Kepware Server vs SKF Enlight Centre
- Kepware Server vs Sensemore
- Kepware Server vs Waites Sensor Technologies
- Kepware Server vs Nanoprecise Sci Corp
- Kepware Server vs Erbessd Instruments
- Kepware Server vs PROGNOST Systems
- Kepware Server vs Petasense
- Kepware Server vs MOVUS
- Kepware Server vs Samotics
- Kepware Server vs Poseidon Systems
- Kepware Server vs eMaint
- Kepware Server vs ABB 800xA
- Kepware Server vs AVEVA System Platform
- Kepware Server vs Hippo CMMS
- Kepware Server vs Rockwell FactoryTalk
- Kepware Server vs 3YOURMIND
- Kepware Server vs AMFG
- Kepware Server vs Ignition
- Kepware Server vs Litmus Edge
- Kepware Server vs Guidewheel
- Kepware Server vs Oden Technologies
- Kepware Server vs Aras Innovator
- Kepware Server vs GENESIS Version 11
- Kepware Server vs Markforged Eiger
- Kepware Server vs Materialise Magics
- Kepware Server vs OpenBOM
- Kepware Server vs Oqton
