Comparison # Aditum Data vs Kepware Server plus a historian Kepware Server (formerly KEPServerEX) is a connectivity layer: it translates PLC protocols into OPC UA and MQTT, and a historian then stores the data. Aditum Data sits on top of that: it reads Kepware over OPC UA and adds the pipelines, cross-site KPIs, data health incidents and dashboards that a connectivity server and a historian don't provide on their own. Since March 2026 Kepware belongs to Velotic, which also owns the Proficy historian line ([Velotic](https://www.velotic.com/products/kepware), [IoT Now](https://www.iot-now.com/2026/03/17/155881-ptc-completes-divestiture-of-kepware-and-thingworx-businesses/)). Facts checked 24 October 2026 ## Aditum Data and Kepware + a historian at a glance Kepware talks to the PLCs; Aditum Data turns what Kepware reads into checked, comparable numbers. **Aditum Data and Kepware + a historian side by side** | | Aditum Data | Kepware + a historian | | --- | --- | --- | | What it is | Industrial data pipelines and dashboards as a managed service: connect plant and business sources, prepare the data without code, deliver it to your platform or to live dashboards. | "Kepware Server converts proprietary protocols into open standards like OPC UA and MQTT." ([Velotic](https://www.velotic.com/products/kepware/kepware-server)) | | Where it runs | Managed by Aditum Data in Frankfurt (EU); a small read-only edge connector at each site (Windows or Linux), outbound HTTPS on port 443 only. | Self-hosted: Kepware Server on Windows, Kepware Edge on Linux in a container; Kepware+ Manager as a SaaS control plane. ([Velotic](https://www.velotic.com/products/kepware), [Velotic](https://www.velotic.com/products/kepware/kepware-edge)) | | Plant connectivity | Edge connector for OPC UA, MQTT (Sparkplug B) and Modbus TCP; AVEVA PI (PI Web API) and GE Proficy; SQL databases, InfluxDB, warehouses, data lakes, Kafka, SAP OData and REST. See [connectors](https://aditumdata.com/connectors). | "150+ drivers and customizable interfaces", with OPC DA and OPC UA. ([Velotic](https://www.velotic.com/products/kepware/kepware-server)) | | Historian | Not a historian. Reads your historian, or stores prepared data in the Aditum database (hosted PostgreSQL with TimescaleDB) or your own destination. | Not a historian; paired with one such as Proficy Historian or PI. | | Asset model and context | A reviewed plant graph per organisation: naming rules (ISA-5.1, KKS), OPC UA folders and MQTT topics become site, unit and equipment; P&IDs and 3D models link to time series after a person approves. | Device and tag structure inside the server; asset modelling lives in other products. | | Calculations | f(x): no-code engineering calculations with unit checks on every step, nine equipment templates (LMTD, duty, OEE, specific energy and more), time-weighted averages. | Not part of a connectivity server. | | Data health and alerts | Incidents without setting up rules: failed runs, stale sources, stuck or silent tags, missed schedules, data received but not stored, offline connectors; email, Teams, Slack, webhooks, PagerDuty, Opsgenie. | Device and server diagnostics; the health of downstream pipelines is outside its scope. | | Dashboards | Live dashboards, including from a plain-language request that a person approves; every number traces to its source tags. | Not part of a connectivity server. | | AI | AI drafts pipelines, dashboards and formulas for approval; the platform calculates every number. Metadata only by default; an organisation can switch AI off. | None found on its product pages. | | How it is sold | Per organisation, never per seat: a free self-serve start, a pilot, then a site subscription. Prices on request. | Kepware Server "a la carte" (drivers, plug-ins, suites); Kepware Edge by subscription with all drivers included. ([Velotic](https://www.velotic.com/products/kepware/kepware-server), [Velotic](https://www.velotic.com/products/kepware/kepware-edge)) | Checked 24 October 2026. Statements about Kepware + a historian come from the vendor's public pages listed under Sources. ## Where Kepware + a historian is the better choice Kepware + a historian is ahead of Aditum Data in these areas today. - **PLC driver library.** 150+ drivers for proprietary protocols ([Velotic](https://www.velotic.com/products/kepware/kepware-server)); the standard OPC server in many plants. - **Runs inside the plant** on Windows or Linux, close to the devices. - **Streams to many targets** through the IoT Gateway (MQTT and REST), with buffering ([Velotic](https://www.velotic.com/products/kepware/kepware-server/advanced-plug-ins/iot-gateway)). ## Where Aditum Data is different What Aditum Data adds for teams that need the same, trustworthy number from every site. - **Everything after connectivity:** pipelines without code, f(x) calculations with unit checks, one KPI definition for every site, and dashboards. - **Data health:** stale sources, stuck tags, heartbeats without data and missed runs open incidents automatically. - **Kepware DataLogger tables** are recognised when Aditum Data reads the database they log to. - **One managed service** instead of a connectivity server, a historian and a BI tool to keep in step at every site. ## Can Aditum Data work with Kepware + a historian? Yes, this is the most common set-up. Aditum Data's edge connector reads Kepware Server through its OPC UA server, which also brings OPC DA devices in. Kepware keeps talking to the PLCs. ## Questions **We already run KEPServerEX. What changes?** Nothing on the Kepware side. Aditum Data's edge connector reads Kepware's OPC UA server, read-only, and sends data out over HTTPS on port 443. **Is KEPServerEX the same as Kepware Server?** Yes. Velotic now names the Windows product Kepware Server ([Velotic](https://www.velotic.com/products/kepware/kepware-server)). ## Sources Public pages the statements about other products rely on, read on 24 October 2026 . Product names are trademarks of their owners. - [Velotic: Kepware product family](https://www.velotic.com/products/kepware) - [Velotic: Kepware Server](https://www.velotic.com/products/kepware/kepware-server) - [Velotic: Kepware Edge](https://www.velotic.com/products/kepware/kepware-edge) - [Velotic: Kepware IoT Gateway plug-in](https://www.velotic.com/products/kepware/kepware-server/advanced-plug-ins/iot-gateway) - [IoT Now: PTC completes divestiture of Kepware and ThingWorx (17 March 2026)](https://www.iot-now.com/2026/03/17/155881-ptc-completes-divestiture-of-kepware-and-thingworx-businesses/) ## Read next - [ConnectorsWhich plant and business systems Aditum Data reads and writes: OPC UA, MQTT and Sparkplug B, Modbus TCP, AVEVA PI, GE Proficy, SQL databases, InfluxDB, Kafka, S3, SAP OData and REST.](https://aditumdata.com/connectors) - [Aditum Data vs AVEVA PI SystemAVEVA PI System is the established plant historian; Aditum Data reads PI and turns it into comparable multi-site KPIs, data health alerts and dashboards. Sourced comparison.](https://aditumdata.com/compare/aveva-pi) - [Data health and incidentsAditum Data opens an incident and emails the owner when a source goes stale, a tag stops changing, a run fails or an edge connector goes offline.](https://aditumdata.com/use-cases/data-health) ## Discuss architecture with an industrial data specialist. Source compatibility, security boundaries, deployment and multi-site operation. Or request a 45-minute technical session to select one KPI and three sites and draft the acceptance criteria. [Book a technical demo](https://aditumdata.com/#contact)[sales@aditumdata.com](mailto:sales@aditumdata.com)