PTC Sells ThingWorx and Kepware to TPG as Industrial IoT Platforms Consolidate

PTC exits industrial IoT platform business

PTC has signed a definitive agreement to sell its Kepware industrial connectivity and ThingWorx IoT platform businesses to TPG, the private equity firm. The deal removes two of the most widely deployed industrial connectivity and application platforms from a diversified CAD/PLM vendor and places them under PE ownership, where roadmap predictability typically declines and profitability optimization accelerates.

This is the sixth ownership change among the most-cited industrial IoT brands in the past 24 months. The same period saw Google Cloud IoT Core retired, IBM Watson IoT shut down, and multiple AWS IoT services enter end-of-life or maintenance-only status. The pattern is clear: industrial IoT platforms built in the 2010s are being divested, consolidated, or killed.

For enterprise buyers, the immediate question is vendor risk. Existing ThingWorx and Kepware customers should expect changes to licensing, support models, and integration priorities over the next 12 to 24 months as TPG assesses the portfolio. New platform selections must now weigh the stability of hyperscaler-led offerings like Azure IoT Operations against PE-owned platforms, especially where asset lifecycles exceed 10 years.

Platform sunset risk now part of TCO planning

The consolidation wave has changed how industrial firms budget for IoT programs. Analysts now recommend building migration contingency into multi-year TCO models — typically an extra 10 to 20 percent to cover potential replatforming costs. Platform decisions that looked safe three years ago now carry measurable exit risk.

RFPs and RFQs for industrial IoT platforms should include explicit questions on ownership stability, end-of-life policies, and data portability. The ThingWorx/Kepware sale is a current example of why that due diligence matters. Buyers should also evaluate platform-agnostic integration layers using OPC UA, MQTT, or data hubs like Siemens Industrial Information Hub to reduce lock-in.

The shift also increases the value of platform diversification strategies. Relying on a single vendor for connectivity, application development, and analytics raises the stakes when ownership changes. Separating these layers — using Kepware for connectivity but a different platform for analytics, for example — creates flexibility but adds integration overhead.

Siemens positions Industrial Edge as OT-first alternative

Siemens announced general availability of its Industrial AI Suite and released Industrial Edge Management v2.0 with support for OpenShift and Hyper-V hypervisors. The updates position Siemens Industrial Edge as a complete OT-first stack for industrial data and AI, competing directly with ThingWorx/Kepware, Azure IoT Operations, and AWS IoT Greengrass.

The addition of OpenShift and Hyper-V support narrows the gap with IT-centric platforms and reduces hardware lock-in. Siemens workloads can now run on existing IT virtualization infrastructure rather than requiring Siemens-specific edge devices. The Industrial Information Hub now supports bidirectional data flows between edge devices and central IT systems, with availability on ARM-based devices like the SIMATIC IOT2050, which can operate on battery power with planned LTE wireless networking.

Siemens is also developing air-gapped operation aligned to IEC 62443-4-2, targeted for the second half of 2026. This addresses a requirement in critical infrastructure and defense-adjacent manufacturing where internet connectivity creates unacceptable risk.

What this means for platform selection

Manufacturers already standardized on Siemens automation now have a vendor-native AI and edge stack with GA status, reducing the need to assemble a mix of third-party platforms. The risk is typical vendor lock-in, mitigated somewhat by the OpenShift and Hyper-V support.

For buyers not committed to Siemens, the competitive landscape now divides into three categories: PE-owned platforms with uncertain roadmaps (ThingWorx/Kepware, potentially others), hyperscaler platforms with cloud-first architectures (Azure IoT Operations, AWS IoT), and OT-vendor platforms with proprietary hardware dependencies (Siemens, Schneider Electric/Aveva, Software AG Cumulocity IoT).

None of these categories is risk-free. PE ownership introduces roadmap uncertainty. Hyperscalers have retired more IoT services in the past three years than they have launched. OT vendors tie platform decisions to automation vendor relationships, which limits flexibility but can reduce integration complexity.

What to watch

Track TPG's first 12 months of ThingWorx/Kepware ownership for signals on licensing changes, integration priorities, or potential spin-offs. Watch whether Siemens extends Industrial Edge support to additional hypervisors or maintains OpenShift and Hyper-V as the IT interoperability layer. Monitor whether other major industrial IoT platforms follow PTC's divestiture path — several PE-owned automation vendors have underperforming software portfolios that could be next.

For buyers with active platform evaluations, the safest near-term move is to prioritize interoperability over feature depth. Platforms that support standard protocols and offer documented data export paths carry less risk than those with proprietary integration models, regardless of current ownership.