Kepware Server — the market-leading industrial connectivity platform, formerly known as KEPServerEX — is now part of Velotic. It transforms proprietary data from virtually any industrial device into normalized data ready for any application, from SCADA, MES and historians to cloud platforms and AI initiatives.

150+Drivers
OPC UAMQTT · Sparkplug B
7.1Current release line
Windowsand Linux (Kepware Edge)
The data path from the field to target systemsKepware Server collects data from PLCs, meters and legacy devices; OPC Router moves it to SQL, MES/ERP and MQTT targets using triggers and transformation rules.FieldAcquisitionIntegrationTarget systemsPLCsSiemens, Rockwell,Mitsubishi, ABBMeters /analysersModbus and similarLegacy devicesSerial, proprietaryKepware ServerDrivers, tags, OPCUA and DA serverOPC RouterTriggers, mapping,transformation,routingSQL databaseTables, recordsMES / ERPOrders, recipes,resultsMQTT / cloudPublish,analyticsReading and writing are designed together: orders and recipes flow down, measurements and results flow up
Acquisition, integration and delivery are separate layers; type, unit, timestamp and quality are preserved at every step.

Why Kepware Server?

Kepware Server provides a unified source of normalized data from OT devices: it aggregates data from PLCs, CNCs, DCS, robots and sensors into a single server and distributes it securely to MES, ERP, SCADA, cloud and analytics systems. No costly hardware upgrades or custom coding — bridge OT and IT in minutes, not months.

Device Connectivity

Connect virtually any device quickly and reliably with 150+ pre-built drivers and scriptable options for custom interfaces.

Data Transformation

Convert proprietary protocols into open standards like OPC UA and MQTT, and enable real-time, condition-based linking between devices.

Secure OT/IT Integration

Minimize your attack surface with secure data tunnels, access control and modern protocols; integrate device data into ERP, MES, SCADA, AWS and Azure.

One Source of Truth

Aggregate OT data from devices, lines and sites into one secure interface — a single point of entry for all client applications.

Use Cases

  • Automation & MES: Real-time, standardized data flow from PLCs to DCS, SCADA and HMI systems, with instant access for MES applications.
  • Industrial IoT (IIoT): Carry plant data securely to cloud and analytics platforms with MQTT and Sparkplug B.
  • AI and analytics: Normalized, real-time data for AI/ML models, OEE analysis and predictive maintenance.
  • Machine-to-machine (M2M): Central data processing and event management between devices with Advanced Tags.

Advanced Plug-Ins

IoT Gateway

Carry OT/IT data to cloud and enterprise platforms with MQTT, Sparkplug B, REST and Azure IoT Hub.

Advanced Tags

Create new data, measure operation durations, observe event summaries and turn raw sensor data into meaningful information.

DataLogger

Log data to SQL, Oracle, MySQL and ODBC-compatible databases for historical analysis.

How a connectivity project proceeds

Every Kepware Server project follows the same hierarchy: channel, device, tag. A consistent order speeds up the build and makes later maintenance easier.

  1. Device inventoryWhich controllers, which protocols, which networks and which addresses? The drivers you need come out of this list.
  2. Channel and deviceOne channel per physical network or protocol and one device per controller; timeout and retry values are set at this stage.
  3. TagsTag names, data types and scaling are defined. Names are part of the item path clients see, so they should be permanent and meaningful.
  4. VerificationThe OPC Quick Client that ships with the installation is used to compare values with the device's own software, and to check quality and timestamps.
  5. SecurityThe OPC UA endpoint, security policy, certificate trust and user permissions are set for the production network.
  6. Hand-over and backupClients (SCADA, MES, OPC Router, cloud) connect; the project file is backed up and changes are recorded.
The Kepware Server project hierarchyA channel defines the physical connection and driver, a device a specific controller, a tag group the logical grouping and a tag a single data point; the names form the OPC item path.ChannelDriver and physicalconnection (networkadapter, serialport)DeviceController addressor IP, model, timingand scan modeTag groupLogical grouping:equipment or systemTagAddress, datatype, scan rate,access, scalingChannel1.Line2_PLC.Filler.TemperatureOPC item path: clients reference the tag by this path; renaming breaks client references
Names are part of the item path that clients use; they should be permanent and meaningful.

Ready to try it?

Temporary demo licenses for Kepware products are available through the "My Kepware" portal. For demo requests, projects and technical support in Turkey, contact us — our expert team prepares scenarios specific to your architecture.

Request a Demo Contact Us

Frequently asked questions

Are Kepware Server and KEPServerEX the same product?

Yes. The product continues under the name Kepware Server within Velotic; the architecture and way of working are the same. See the 7.x release notes for version-specific changes.

Which devices can it connect to?

With 150+ drivers it connects to controllers from Allen-Bradley, Siemens, Modbus, Mitsubishi, Omron, ABB and many more. See the driver list for details; if your device is not listed, write to us.

Which protocols does it serve data over?

It works as an OPC UA server; with the IoT Gateway add-on it can also publish over MQTT, Sparkplug B and REST. The OPC UA Client driver connects it to other UA servers as well.

Do I need both Kepware Server and OPC Router?

No, they are separate products. Kepware Server connects to devices and serves the data through a standard interface. OPC Router moves that data to enterprise systems such as SAP, databases and MES. If you only need to feed a SCADA or historian, Kepware Server on its own is enough.

How do I manage the licence?

Activation, transfer and demo licences are handled in the My Kepware portal. Details are on the licensing page.

Next step

Driver listWhich device families are supported?Driver packsLicence structure and optionsAdvanced optionsIoT Gateway, DataLogger, Advanced TagsChannel–device–tag modelHow to build a robust configurationKepware Server 7.0What changed in the new release lineThe right data collection pathChoosing between drivers, OPC UA and MQTT

Official Resources

For current product information, release notes and documentation, see the official sources: