What actually stops a customer keeping your software?

Plenty of software is sold to run on the customer’s own infrastructure, and usually for good reasons. Regulated industries require it. Security teams prefer it. Some buyers simply will not put their most sensitive processing on someone else’s servers, and telling them to grow out of that view loses the deal.

So you ship. Your product goes onto their hardware, inside their network, under their control, and it works. That is the sale.

It also means every customer now holds a complete, working copy of the thing your company is. Your pricing engine. Your matching logic. Your scoring model. The parts that took years and that a competitor would need years to reproduce.

Renewal season arrives and a customer decides to leave, or a deal quietly lapses, or a pilot never converts.

Ask what actually happens to the software at that moment. In most companies the honest answer is: nothing. The install keeps running. The licence key, if there is one, was checked at installation and never again, or it checks a file the customer’s own administrator can edit. Your terms require them to stop and to delete the binaries, and those terms are enforced by a lawyer writing a letter, which nobody wants to do to a company they might sell to again.

So the product keeps working. Sometimes for years. Sometimes on the production systems of a company that is no longer paying you, running the thing you built, at scale.

The usual responses are worth being honest about.

Obfuscation makes code harder to read. It does not stop it running, which is the actual problem here. A customer who never opens your binary but keeps using it for three years has cost you the same amount whether the code was obfuscated or not.

Licence key checks are a speed bump, because the check runs on hardware the other party controls. Anything your software decides locally can be changed locally.

Audit clauses assume you will exercise them. Almost nobody does, because the first company you audit is a company you will never sell to again.

IP protection takes a narrower approach. You do not lock the whole product, which would be impractical and slow. You identify the parts that actually make it yours, which in most products is a small fraction of the codebase, and those parts ship locked.

The software runs on the customer’s servers exactly as it always did. When it reaches a protected part, it asks for permission, gets it, and continues. Under normal conditions nobody notices anything, and brief network interruptions are tolerated by design, so a momentary outage does not take a customer’s production system down.

What changes is what happens when you stop giving permission. The contract ends, and the protected parts stop unlocking. The software does not go on running without you, because the pieces that made it worth having were never fully in the customer’s hands.

The security argument is the obvious one. The commercial argument is the one that pays for the project.

Today, a renewal conversation with an on-premise customer has an unspoken asymmetry: they already have everything. Renewing is, in a sense, optional, and both sides know it. Support and updates are the only leverage, and a customer running a stable version may not value either very much.

When the software stops at the end of the term, renewal becomes a real decision about continuing to use a working product. That is the normal shape of a software business, and most on-premise vendors have never had it.

The same mechanism turns pilots into pilots. A 60-day evaluation that actually ends on day 60 does not become a three-year free deployment while a deal stalls.

Less than they expect. Protection is applied to selected parts as part of your build, not by rewriting your product. Developers work with the source as normal. The locked version is what ships.

The honest cost is that protected software needs to reach your permission service, and that makes your uptime a contractual commitment rather than a marketing line. That is the trade. A file that opens without checking anything is a file you have permanently given away.