On March 16, 2026, PTC closed the sale of ThingWorx and Kepware to TPG for $523 million in cash. What they did with the money tells you everything: approximately $375 million went to an accelerated share repurchase program. PTC didn’t reinvest in IoT. They didn’t spin the proceeds into adjacent industrial technology. They bought back their own stock. IoT is no longer core to PTC’s strategy, and they didn’t bother pretending otherwise.
Three weeks later, on April 8, SUSE announced the acquisition of Losant. Cumulocity had already gone independent via a management buyout from Software AG in January 2025, backed by Avedon Capital, Schroders Capital, and Verso Capital.
Three ownership changes in fifteen months. The people most affected aren’t the vendors or the private equity firms. They’re the system integrators who spent years building expertise, earning certifications, and establishing client relationships around platforms that now answer to new owners with different priorities.
What actually happened, and where each platform is heading
ThingWorx + Kepware → TPG. TPG is private equity. They’re calling this a “generational opportunity.” PE firms acquire with a 3-5 year horizon, and the playbook is well understood: optimize margins, grow the installed base, prepare for the next transaction.
We’ve been talking to integrators who went through this before. VMware partners saw license restructuring within months of the Broadcom deal in 2023. Marketo’s channel got squeezed after Vista Equity acquired it in 2016, only to flip the asset to Adobe two years later. These aren’t obscure examples — they’re the deals that people in our partner conversations keep bringing up, because they remember what it felt like on the receiving end.
Nobody knows TPG’s specific plans yet. For integrators, that’s the problem. You’re operating in a vacuum for 6-12 months post-close while being expected to sell long-term platform commitments to clients. That vacuum doesn’t clear until the new owner shows you their actual strategy through action — not press releases.
Compounding the problem: ThingWorx was deeply integrated with PTC’s Windchill and Creo. Projects that sold the “PTC ecosystem story” now span two separate vendors with two separate roadmaps. The tight integration your clients depended on lives on a business relationship between TPG and PTC, two companies serving two different sets of shareholders.
Losant → SUSE. Different structure. SUSE is a technology company filling a specific gap: the layer between their existing near-edge infrastructure and the device/sensor layer. Losant becomes the IoT application piece in a broader SUSE Edge story, with plans to open-source parts of the technology.
For integrators, the concern is straightforward. Standalone IoT platforms that get absorbed into larger portfolios stop being the main character. The roadmap gets reprioritized around the parent company’s strategy. The partner program gets restructured. Losant integrators who built their practice around Losant’s standalone value need to figure out how their platform fits into SUSE’s edge play, and whether their clients’ use cases still map to it. The founding team and key engineers tend to leave within 12-18 months of these deals. Cisco lost most of Jasper’s original leadership after the 2016 acquisition; IBM saw the same with The Weather Company — the pattern repeats.
Cumulocity → Independent. Of the three transactions, this one is structurally the most integrator-friendly. Management buyout. The people running the platform are the people who own it. No PE exit horizon. No absorption into a broader corporate portfolio. But it’s still an ownership change, and new backers mean new governance, new priorities, and at least temporary friction for the partner ecosystem.
Why this hits system integrators harder than anyone else
System integrators make a different bet than end customers. When a factory picks an IoT platform, they’re solving a problem. When an SI picks a platform, they’re choosing a business partner whose pricing model, partner program, technical roadmap, and support infrastructure will determine whether their own projects succeed or fail across dozens of clients.
A CTO at a 400-person manufacturing company doesn’t pick an IoT platform because of feature checklists. They pick it because you, the integrator, looked them in the eye and said: “This platform will serve you for the next five years. Here’s the roadmap. Here’s the pricing trajectory. Here’s what support looks like when something breaks at 2 AM on a Saturday.”
When the platform changes owners, the foundation under that promise shifts.
Your answers get weaker. “I’m confident in the roadmap through 2027” becomes “I’m waiting to see what the new ownership announces.” That’s not a comfortable position. The CTO who trusted you doesn’t care about M&A dynamics. They care about their production line.
Your reputation absorbs the vendor’s problems. We talk to partners regularly, and the support question comes up in almost every conversation about platform stability. During a vendor ownership transition, the problems are predictable: role confusion between old and new support teams, fragmented account ownership, new engineers who don’t know your client’s configuration. The client doesn’t call TPG when their support ticket goes unanswered for two weeks. They call you. You sold the platform.
Pricing shifts under active deployments. Per-device pricing, consumption tiers, usage-based billing: these structures determine integrator margins. A new owner with different financial priorities can compress your margins mid-engagement. You quoted the client based on one pricing model. Eight months later, the model changes. Your contract with the client didn’t. I’ve seen this break project economics on a 3,000-device rollout where the platform cost doubled between pilot and production.
Lock-in stops being abstract. Every IoT platform creates some form of lock-in: proprietary data models, custom workflow logic, platform-specific APIs, certifications that represent months of invested time. The consolidation wave doesn’t create lock-in. It makes it personal. You’re locked into a product, sure. But now you’re also locked into an ownership structure you didn’t choose, serving priorities you may not share.
What to evaluate when choosing a platform right now
Whether you’re picking a platform for the first time or re-evaluating your current one, the consolidation wave changes what matters. I’m a Technical Product Manager at Iotellect, so my perspective is shaped by our platform and our partners. But these questions apply regardless of which vendor you’re considering.
Ownership structure and time horizon. Who owns the platform, and how long do they plan to own it? A PE firm with a 3-5 year exit strategy. A public company where IoT is a non-core line item. A large enterprise absorbing IoT into a broader portfolio. Or an independent company where the platform is the business. Your client engagements run 2-5 years. Your vendor’s ownership timeline should at least rhyme with that.
Pricing that doesn’t punish growth. Per-device pricing looks clean in the proposal. Then the client’s deployment grows from 800 to 12,000 devices, and the platform cost curve makes the project unprofitable. Tier-based pricing, structured around deployment scope and infrastructure rather than device count, gives integrators defensible margins. Ask the vendor: what happens to pricing when my client adds 40% more devices in year two? Get the answer in writing.
Protocol coverage and deployment flexibility. Real deployments in manufacturing, smart buildings, and utilities need to speak Modbus, BACnet, OPC UA, MQTT, SNMP, DNP3, IEC 60870-5-104, EtherNet/IP, and your next client will need a protocol you haven’t encountered yet. If your platform doesn’t support it natively, you’re building custom integration layers at hours you can’t bill at margin. Same logic applies to deployment models: cloud-only works until a client’s IT security team blocks outbound data transfer, or a remote facility needs local processing because the WAN drops twice a week. On-prem, hybrid, and edge options aren’t nice-to-haves. They’re the difference between winning a deal and watching it go to a competitor who can deploy where the client needs.
Roadmap and support you can verify. Can the vendor show you a committed 18-month roadmap — funded, staffed, with delivery dates? Not the aspirational version. On support: who handles your technical escalations? Can you get a named technical contact, or are you submitting tickets into a queue? Dedicated partner support and a generic help desk are not the same thing, and you’ll feel the difference at 2 AM on a factory floor.
Your current deployments are safe. Your next proposal is the decision point.
The ThingWorx, Losant, and Cumulocity deployments you have in production will keep running. APIs won’t break tomorrow. Current projects will deliver.
But every new proposal you write from this point forward locks you into a vendor relationship for years. That’s the decision worth making deliberately — while you still have options and before your current vendor makes choices you didn’t ask for.
Iotellect has been independently owned since 2001. No acquisitions, no private equity involvement, no portfolio strategy where IoT is a supporting character. The platform ships with tier-based pricing, 30+ protocol drivers, and deploys on-prem, cloud, edge, or hybrid. The partner program was designed for system integrators.
If that’s relevant to your next platform decision, we should talk.