Kepware Perpetual vs Subscription: Why a 5-Year TCO Doesn’t Tell the Whole Story

Most Kepware Perpetual vs Subscription comparisons reduce the decision to a single number: total cost over five years. The problem is that this number changes dramatically with three or four assumptions, and even a „correct” 5-year TCO leaves out the factors that actually decide deployment outcomes: OT security exposure, vendor roadmap access, fleet management overhead and operational continuity. This article breaks down what a cost-only model misses, and gives finance and IT leaders a framework that survives the next price change.

Why the 5-Year TCO calculation is harder than it looks

A 5-year TCO comparison between a perpetual license and a subscription license is a reasonable starting point. It is not a verdict. The output shifts by 20 to 50 percent depending on three variables that no online calculator asks: how many communication drivers your environment runs, whether the underlying server infrastructure stays put, and where a major version cycle lands inside the window. The default spreadsheet assumes a closed system, a single instance, and a stable protocol stack. That description fits almost no real industrial deployment.

For an honest analysis, the calculation has to start with the purchased version of Kepware software and then layer the recurring obligations: annual technical support, the cost to renew technical support at each anniversary date, and the periodic kepware update events that may or may not require an additional single payment. The further out the projection runs, the less reliable the inputs become. A 5-year horizon for industrial software is a long time. Server hardware refreshes once. Major software versions ship at least once. Protocol scope grows almost always.

The Assumptions That Swing the Number by Thousands

Three variables move the result more than any pricing change Velotic could announce next year:

• Driver packages count. In a standard perpetual license, every driver is a separate purchase, so each new device family added on a regular basis translates into a fresh line item from the sales department.
• Infrastructure migration cadence. Every server replacement, every cloud move, every disaster recovery failover triggers a transfer event for the software key that sits on a specific computer.
• Major version cycle. If the upgrade lands in year 2, the perpetual side absorbs the cost early; if it lands in year 5, the picture flatters perpetual artificially.

Variable	Impact on TCO	Impact on Subscription TCO
Number of communication drivers	Each new driver adds a separate perpetual license price	Edition includes the full drivers set
Server/cloud migration events	License transfer procedure or new perpetual license	No additional cost during the subscription period
Major version timing	Major Kepserverex update equals additional fee	All newer versions included, no extra invoice

Why Most Online Comparisons Get This Wrong

Generic comparisons assume one license, no driver additions, no infrastructure changes, no major upgrades. From TT PSC deployment experience across European manufacturing sites, the median Kepware environment adds two to three new driver packages within three years and migrates servers at least once over a five-year window.

The Hidden Cost Architecture of Kepware Perpetual License

A kepware perpetual model has five cost layers beyond the headline price. Annual maintenance renewal, major version upgrades, per-driver licensing for new protocols, reinstatement penalties when coverage lapses, and re-deployment costs when infrastructure changes. Together, those layers can match or exceed the original license cost inside the first five years. None of them appear on the quote PDF. All of them appear on the second-year P&L.

Service & Maintenance: The Annual Fee That Is Not Optional

Service & Maintenance, often abbreviated S&M, is the annual contract attached to a perpetual license. The current technical support price typically runs around 20 percent of the original license value per year. Some teams treat it as discretionary. It is not. Without an active S&M contract, the Kepware software continues to operate, but the access channel to the technical support team closes, security patches stop arriving, and minor releases stop installing. Every month without coverage is a month of growing CVE exposure on a piece of software that sits at the OT/IT boundary.

If an organization has stopped paying S&M and later wants to purchase technical support again, Velotic applies a reinstatement penalty on top of the standard renewal fee. The price level depends on how long the gap was. The longer the lapse, the more painful the math. For existing perpetual license customers, a deliberate decision to skip a year almost always costs more than it saves.

The honest framing: in a perpetual license model, S&M is not an optional add-on to purchase support. It is the operating tax on owning the asset. Treating it any other way builds a security liability into the budget.

Major Version Upgrades: What „Free Updates” Actually Means

Active S&M includes minor releases, bug fixes, and higher stability bug fixes throughout the entire duration of the contract. It does not include major version upgrades. Moving from Kepware v6 to v7, for example, is a separate transaction. For older licenses, that transaction can approach the price of a new perpetual license. Standard subscription licenses behave differently: every major release is included, and software updates install without a separate procurement cycle. Across a five-year window, at least one major version event is statistically likely. Plan accordingly.

Per-Driver Licensing: When Your Protocol Stack Grows

In the perpetual world, every protocol is its own SKU. Modbus TCP, EtherNet/IP, PROFINET, Siemens S7, OPC UA, and the long tail of OEM-specific drivers each carry an individual perpetual license price, typically in the 400 to 1,500+ USD per driver range. Kepware ships (Kepware drivers list), and industrial environments rarely freeze their protocol scope. A new PLC vendor, a fleet of new devices from an acquired plant, an integration partner with different equipment, each one of these moments adds another invoice.

A subscription includes the full driver set inside the chosen edition, with no per-protocol gating inside that scope. Three additional drivers added across five years in the perpetual model adds 1,200 to 4,500 USD or more that does not appear in the baseline 5-year TCO. Multiply that by site count and the gap widens further.

Re-Deployment: The Hidden Cost Even Analysts Miss

The perpetual license is node-locked. The license id is bound to a specific computer. Moving the workload to a new server, a virtualized host, a cloud instance, or a DR replica requires a formal transfer procedure with Velotic, and in some cases a fresh license purchase. Every M&A integration, every hardware refresh, every cloud-first IT initiative triggers this overhead. From TT PSC field practice, infrastructure migration is the single most underestimated cost in perpetual planning. It does not appear in any generic TCO calculator we have ever reviewed.

A subscription is environment-agnostic inside Velotic’s terms. Servers can move. Workloads can migrate. The license follows the account, not the box.

What Kepware Subscription Covers, and at What Price

A Kepware subscription is an all-inclusive annual fee billed on the anniversary date. A single line item covers:

• The Kepware license
• All communication drivers in the selected edition
• Every minor and major release
• Expert technical support
• Security patches

There are no separate invoices for any of these components.

What’s Included in Each Subscription Edition

Each edition tier (the entry, standard, and advanced configurations available through TT PSC and other authorized channels) includes technical support, full named driver coverage for the edition, every minor release, every major release during the period selected, and active patch delivery. The per-driver, per-upgrade, per-incident billing pattern that defines the perpetual model disappears entirely. For finance, that translates into deterministic forecasting: the same line item, every year, until the subscription is terminated.

It also simplifies the ownership of license information and personal details tied to support. A single contract, a single renewal date, a single point of contact for the customer.

What Subscription Does NOT Cover

Honesty matters here, because credibility carries the rest of the article. A subscription does not cover everything.

• Drivers outside the selected edition scope require a tier change.
• On-premise hardware, network, and OS support remain outside Velotic scope and stay with internal IT or an integration partner.

Custom plugin development, advanced *manufacturing suite** integration work, and tailored configuration projects fall under VAR services. This is where TT PSC engages LINK.

If a competitor pitches subscription as a „covers everything” model, that pitch is incomplete. The right framing is: subscription removes the licensing friction; integration work is a separate line on a separate scope.

The Four Factors a TCO Model Can’t Capture

A cost spreadsheet answers one question: „which option is cheaper under these assumptions.” It does not answer the four questions that decide whether a deployment ages well:

• What happens to OT security if patches stop arriving?
• Will the license survive a server move?
• Does the vendor’s product roadmap stay accessible?
• Can the finance team actually approve the chosen budget shape?

OT Security Exposure Without Current Patches

Kepware runs at the OT/IT convergence point. It is, by architectural position, a critical attack surface in any industrial environment. Without active S&M, no CVE patches arrive. No security updates apply. Six months of deferred patching is six months of accumulating exposure on a component that touches every PLC in the plant.

The NIS2 Directive, in force across EU member states since October 2024, and the IEC 62443 standard for industrial control system security, both treat patch currency as a baseline control. They do not treat it as a nice-to-have. Running an unpatched Kepware instance can constitute a compliance gap during an audit. The cost of that gap, the cost of an OT incident, the cost of a regulatory finding, none of these appear in a „perpetual vs subscription” worksheet. They are real, and in a serious incident scenario they dwarf every line on the spreadsheet combined.

This is the reason S&M is not a purchase terms detail. It is a security control.

Infrastructure Migration Risk

Cloud-first IT strategies, hybrid OT architectures, and edge consolidation programs are accelerating server change in industrial environments. A perpetual license is a liability in a dynamic infrastructure. A subscription is not. If the IT/OT roadmap for the next year, the next year, or the five-year horizon includes any combination of server consolidation, virtualization shift, cloud migration, or DR failover, the re-deployment cost has to be modeled explicitly. Otherwise the comparison is fictional.

Vendor Roadmap Lock-In: Kepware Edge Is Subscription-Only

The most strategically important fact in this entire decision is also the simplest: Kepware Edge is subscription-only. There is no perpetual option for the next-generation edge connectivity stack. ThingWorx integration patterns, containerized edge deployments, cloud-native OPC UA aggregation: every modern path forward in Velotic’s portfolio runs through subscription licensing. Choosing perpetual today means access to the current Kepware generation only. The roadmap closes behind that choice.

For organizations on an active Industry 4.0 or IIoT trajectory, this single point overrides nearly every cost argument in either direction. Perpetual fits a frozen architecture. It does not fit a transformation.

Budget Model Fit: CAPEX vs OPEX

A perpetual license is CAPEX: a one-time capital expenditure, depreciable over three to five years, requiring capital approval above whatever threshold the organization has set. A subscription is OPEX: an operating expense, expensed in the period, no capital cycle required. For a CFO managing a tight capex envelope, OPEX subscription removes a procurement bottleneck. For an IT manager building next year’s run-rate forecast, OPEX delivers deterministic numbers without surprise upgrade invoices.

The nuance worth respecting: some organizations, particularly in defense, regulated utilities, and certain public-sector contexts, genuinely prefer CAPEX. The pricing policy internally favors capitalizable assets. In those cases, the perpetual route is not a finance failure. It is the right answer for that governance model.

Honest Take: Perpetual Wins on Paper. Then Reality Happens.

The reader already knows this, so there is no point pretending otherwise. A simple, single-site, single-instance perpetual deployment looks cheaper on a spreadsheet than the equivalent subscription over five years. Admitting that builds the credibility to discuss what happens next.

Reality happens. Drivers get added because someone bought a new robot cell. A server gets retired because the OEM ended hardware support. A new plant joins the group through acquisition and runs different PLCs. The audit team asks for evidence of CVE patch status across OT. Suddenly the spreadsheet that won on paper is paying out in pieces: one subscription conversion license here, one driver pack there, one Kepware update invoice next quarter, one re-deployment fee the year after.

Subscription does not „win” in the abstract. It wins when complexity arrives, and in industrial environments, complexity always arrives. The right way to phrase the decision is not „which is cheaper today” but „how much does the complexity I am about to encounter cost me under each model.”

The Scaling Penalty in Perpetual

Scaling is where the perpetual model strains hardest. Every new protocol is a separate purchase. Every new instance, on every new site, is a separate subscription license contract equivalent on the perpetual side: another standard perpetual license, another S&M renewal, another anniversary date to track, another set of license information and personal details to maintain. By the third site, the operational overhead of tracking renewals, version states, and driver inventories per instance becomes its own cost center. Subscription consolidates this under a single account with a single renewal cadence.

Fleet Management: The Cost That Has No Line Item

Ten Kepware instances without a central management plane is ten times the operational overhead. Configuration drift, version drift, patch state drift, and certificate management each multiply per instance. Kepware+ Manager, the central management plane that addresses exactly this problem, is included in the subscription period model. It is not available as a perpetual product at all.

For multi-site manufacturing groups, this is a quiet but decisive factor. The fleet management overhead never makes the product description section of a vendor quote. It absolutely shows up in the operations team’s time sheets.

Break-Even Depends on Context, Not on a Universal Formula

Anyone offering a single break-even point is selling, not advising. The honest answer is contextual.

• Perpetual breaks even faster in single-site, single-protocol, stable environments with no Industry 4.0 ambitions and a strong CAPEX preference.
• Subscription breaks even faster under three or more sites, mixed device fleets, active compliance obligations, and any active IIoT roadmap.

Both the license model and the operational shape of the deployment have to be evaluated together. Both the license type and the environment around it determine the actual TCO, and the spreadsheet alone cannot see the environment.

A Decision Framework: Five Questions Before You Choose

Skip the verdict. Use five diagnostic questions instead. The answers point cleanly toward one model or the other for any given site.

1. Is the protocol stack expected to grow over the next three to five years?
2. Is the underlying server or cloud infrastructure 100 percent stable, or is a refresh expected?
3. Does the IIoT or Industry 4.0 roadmap include Kepware Edge, ThingWorx, or cloud-native edge connectivity?
4. Is the OT security posture under formal scrutiny under NIS2, IEC 62443, or customer audits?
5. Does finance prefer OPEX predictability over CAPEX approval cycles?

A „yes” on three or more questions points firmly to subscription. A „no” across the board is the honest case for perpetual.

When Perpetual Still Makes Sense

A non-adversarial treatment of where perpetual is the right answer.

Scenario: Closed, static deployment with no planned expansion

Why perpetual works here: No driver growth, no migration, S&M is the only recurring overhead

Scenario: Air-gapped OT network with strict no-connectivity policy

Why perpetual works here: Updates cannot be applied anyway, and most subscription advantages disappear

Scenario: CAPEX-mandated organizations (defense, regulated sectors)

Why perpetual works here: Finance governance requires capital expenditure shape

Scenario: Short project duration under two years

Why perpetual works here: Subscription break-even has not been reached inside the project window

Even in these scenarios, the security framing still matters. Air-gapped does not mean risk-free. Discuss NIS2 implications with an authorized VAR before treating S&M as optional.

When Subscription Is the Stronger Choice

Five clean signals that a subscription model wins.

1. Protocol scope is expected to grow, with new PLC vendors, devices, or partners coming online.
2. Server infrastructure is not 100 percent stable; refresh, virtualization, or cloud migration is on the roadmap.
3. The IIoT or Industry 4.0 program is active, and Kepware Edge or ThingWorx is in scope.
4. OT security and compliance are under audit scrutiny.
5. Finance favors OPEX predictability over CAPEX approval cycles.

Three of these signals is usually enough. Four is decisive.

Migrating from Perpetual to Subscription

For existing perpetual license customers considering a move, subscription conversion programs run periodically, often with very favorable terms during specific windows. Velotic and authorized partners have offered an attractive incentive offer structure that credits the existing perpetual investment toward the subscription license, sometimes packaged as a trade-in, sometimes as a co-termination of S&M against a new subscription start. Volume customers may qualify for a volume discount depending on the purchased version profile and active S&M status.

The mechanics are straightforward in principle: the sales department at the VAR confirms current S&M coverage, validates the license id of the existing instance, and structures a subscription conversion license with the appropriate price level and purchase terms. In advance of the renewal anniversary date, the customer chooses from the following options: continue perpetual with S&M renewal, convert to subscription on unique conditions, or run hybrid with new sites on subscription and legacy sites on perpetual until natural retirement.

For complete information on the current price of conversion, favorable terms available in a given quarter, and the access to specific edition tiers, contact your authorized VAR. Many software companies publish indicative pricing; Velotic does not, and a VAR engagement is the only way to return complete information matched to a specific environment.

FAQ

What is the difference between Kepware perpetual and subscription license?

Perpetual is a one-time purchase plus annual S&M. Subscription is an annual all-inclusive fee covering the license, all drivers in the selected edition, support, and updates as one line item, with no separate billing for components.

What is Kepware S&M and how much does it cost?

S&M (Service & Maintenance) is the annual maintenance contract attached to a perpetual license. The current technical support price typically runs around 20 percent of the original license value per year. Without it, technical support, security patches, and minor updates are unavailable.

Does a Kepware subscription include all communication drivers?

All drivers in the selected edition tier are included. Drivers outside that tier require an edition change. Contact an authorized VAR for the exact edition scope.

What happens if S&M payments stop on a perpetual license?

The kepserverex software continues to operate, but support, kepserverex update access, and security patches stop. Reinstating S&M after a lapse incurs a reinstatement penalty proportional to the gap.

Is the 5-year TCO lower with subscription or perpetual?

It depends on the environment. Subscription wins under driver growth, infrastructure migration, or a major upgrade cycle inside the window. Perpetual wins in closed, static deployments with no protocol expansion. There is no universal answer.

Can a Kepware perpetual license be moved to a new server?

Yes, through a formal license transfer procedure with Velotic. In some scenarios (major version mismatch, certain virtualization patterns), a new perpetual license purchase is required instead.

Is Kepware Edge available as a perpetual license?

No. Kepware Edge is subscription-only. Any IIoT roadmap including Kepware Edge requires subscription licensing.

How do I migrate from perpetual to subscription?

Contact an authorized Kepware VAR such as TT PSC. Migration paths include trade-in, co-termination of S&M against a new subscription start, and hybrid models. Specific options depend on current S&M status and purchased version.

What is the reinstatement fee for lapsed S&M?

Velotic applies a reinstatement penalty on top of the missed renewal, scaled to the length of the lapse. Exact rates change over time. A VAR can confirm the current rate for a specific license id.

Does TT PSC support both license models?

Yes. As an authorized Kepware VAR with deep deployment experience across European manufacturing, TT PSC supports both the license types, advises on conversion timing, and engages on integration work that sits outside Velotic scope in either model.

The Bottom Line

Perpetual is a tool for simple deployments. The 5-year TCO question is not the right question for an enterprise environment. The right question is: how much does the complexity that perpetual carries actually cost over time?

Driver growth costs money. Server moves cost money. Major version cycles cost money. Lapsed S&M costs security. Multi-site fleets without a central management plane cost operational hours. None of these line items appear in the cheap version of the comparison, and all of them appear in real environments.

If the deployment is one site, one protocol, one server, with no IIoT ambitions and a CAPEX mandate, perpetual remains a defensible choice. For everything else, subscription is structurally aligned with how industrial environments actually evolve.

Talk to TT PSC About Your Kepware Licensing

TT PSC is an authorized Kepware reseller and certified system integrator serving European manufacturing. We sit on both sides of this conversation: we know the licensing mechanics in detail, and we deploy Kepware into real OT environments every quarter. That combination matters when the question is no longer „what does it cost on paper” but „what fits the environment we actually have.”

Three ways to engage:

• Subscription quote, sized to your environment. Tell us your driver footprint, site count, and IIoT roadmap. We come back with the right edition tier and a clean subscription license quote. No discovery phase required for straightforward cases.
• Perpetual to subscription conversion. For existing perpetual license customers, we run the conversion math against your current S&M status, anniversary date, and purchased version, and we structure the subscription conversion license under whatever incentive window is currently active.
• Free TCO and risk assessment. When the answer is genuinely unclear, we model the full picture: driver growth, migration risk, fleet management overhead, NIS2 and IEC 62443 implications, and CAPEX vs OPEX fit. The output is a defensible recommendation you can take to finance and IT leadership.