Softwr

Manufacturing · head to head

Kepware Server vs LabVIEW

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

LabVIEW

Manufacturing

Graphical dataflow programming for automated test, measurement and instrument control

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.; LabVIEW nI is now part of Emerson, completing in 2023, so LabVIEW sits inside an industrial automation conglomerate rather than being the flagship of a dedicated test company; roadmap priorities and support pricing follow the parent, not the user base.
  • They diverge on capability: Kepware Server covers 150-plus device drivers, LabVIEW covers Graphical dataflow programming.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

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

Attributes where Kepware Server and LabVIEW differ
AttributeKepware ServerLabVIEW
PlatformsWindows, LinuxWindows, Linux, macOS

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 LabVIEW

  • Graphical dataflow programming
  • Front panels
  • Instrument driver library
  • Hardware integration
  • Real-time and FPGA targets
  • Analysis and signal processing
  • Application builder
  • Nigel AI assistant

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

LabVIEW

  • An automotive supplier building an end-of-line test rig that must drive a power supply, read a scope and log pass/fail against a serial numbernot Kepware Server
  • A semiconductor lab characterising devices across a PXI chassis where deterministic timing between instruments mattersnot Kepware Server
  • A medical device manufacturer needing a validated, documented test system with an operator front panel a technician can run unsupervisednot Kepware Server
  • A research group prototyping a control loop on CompactRIO where part of the logic must compile down to an FPGAnot 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.

LabVIEW

  • NI is now part of Emerson, completing in 2023, so LabVIEW sits inside an industrial automation conglomerate rather than being the flagship of a dedicated test company; roadmap priorities and support pricing follow the parent, not the user base.
  • No prices appear anywhere on the NI site for commercial editions; Base, Full, Professional and the LabVIEW+ suite are all quoted through NI or a reseller, so a buyer cannot compare cost against a Python-plus-PyVISA alternative without opening a sales conversation.
  • Graphical source code diffs badly. Merging two engineers’ changes to the same virtual instrument in git is impractical without NI’s own comparison tools, so team development on LabVIEW is slower and more serialised than on text-based languages.
  • The pool of engineers who write LabVIEW is small and ageing relative to the pool who write Python, so hiring a replacement for the person who built your test rig is materially harder and more expensive than replacing a general software engineer.
  • The environment pulls you toward NI hardware and NI add-on toolkits, and licences for real-time, FPGA and vision modules are sold separately on top of the base edition, so the quoted LabVIEW price is rarely the delivered cost of a working test system.

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

LabVIEW

On request
  • LabVIEW Community EditionFree
    • Free for personal, non-commercial use only
    • Full LabVIEW feature set for hobbyists
    • No commercial deployment rights
  • LabVIEW Base$undefined/year
    • Core acquisition, control and user interface capability
    • Suited to simple test and measurement applications
    • Available as subscription or perpetual licence
  • LabVIEW Full$undefined/year
    • Adds advanced analysis and signal processing
    • Recommended where mathematics and filtering are required
    • Available as subscription or perpetual licence
  • LabVIEW Professional$undefined/year
    • Adds application builder, source control and deployment tooling
    • Includes the Nigel AI assistant
    • Available as subscription or perpetual licence

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

  • You need graphical dataflow programming.
  • You work on Windows, Linux, macOS.
  • You also want front panels.
LabVIEW review

Questions people ask

Is Kepware Server or LabVIEW better?
Neither clearly leads. Kepware Server starts at On request and LabVIEW at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Kepware Server or LabVIEW?
Kepware Server starts at On request and LabVIEW at On request.
Does Kepware Server or LabVIEW run on more platforms?
Kepware Server runs on Windows, Linux. LabVIEW runs on Windows, Linux, macOS.
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 LabVIEW is typically brought in for.
What can Kepware Server do that LabVIEW cannot?
Kepware Server covers 150-plus device drivers, OPC UA server, IoT Gateway, DataLogger. LabVIEW covers Graphical dataflow programming, Front panels, Instrument driver library, Hardware integration.

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.

LabVIEW: Who owns LabVIEW now?

NI, formerly National Instruments, was acquired by Emerson in an acquisition that completed in 2023. LabVIEW is now an Emerson product.

Kepware Server: Is a perpetual licence still available?

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

LabVIEW: Can I still buy a perpetual licence?

Yes. NI offers both subscription and perpetual licences and states there are no functional or feature-level differences between them.

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.

LabVIEW: Is there a free version?

LabVIEW Community Edition is free for personal, non-commercial use. It carries no commercial deployment rights.

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.

LabVIEW: How much does it cost?

NI does not publish commercial edition prices. Base, Full, Professional and LabVIEW+ are all quoted through NI or a reseller.

Share

Related pages

More on Kepware Server

More on LabVIEW

Keep looking

Other head to heads