How to protect software from piracy.

Why software gets pirated

Most piracy is not a feat of reverse engineering. It's one licence key posted on a forum, an installer passed between colleagues, or a "cracked" build where someone removed the line of code that checks the licence. Every one of these works because the protection is either shareable (a key is just text) or removable (a check is just code).

So the useful question isn't "how do I stop copying?" It's "how do I make a copy worthless, and a leak expensive?"

Why licence keys and online checks aren't enough

A licence key works on any computer it's typed into, so one leaked key unlocks every copy. A key generator can mint more once someone works out how keys are checked. Online activation helps until the activation server is down, blocked, or simply patched out of the program; and it locks out every customer who works offline.

The deeper problem is the if licensed check itself. If the program runs fine once that check is skipped, a cracker only has to find it. Obfuscation slows that down; it doesn't stop it.

Encrypt what you sell, and keep the key in hardware

Strong protection removes the check entirely. Ship the valuable part of your app (a module, a model, a content pack) encrypted, and make the licence the thing that decrypts it. Without the licence there is nothing to patch: the code isn't there to run.

Then put the key where it can't be copied. Most computers have a TPM 2.0 security chip (Windows 11 requires one), and phones have an Android Keystore or Secure Enclave. Keys made inside them can be used but never read out. Seal each customer's licence to their chip, and a copy of the app and the licence on another machine has nothing that can open it. This is a node-locked licence enforced by cryptography rather than by a comparison in code.

Make leaks traceable

Anyone who can use your app can, in the end, capture what it shows them. You can't prevent that, but you can make it attributable. Forensic watermarking gives every customer a copy that differs invisibly; when a copy surfaces, the mark names the licence it came from. Knowing that a leak points back to them is a strong deterrent for paying customers, and it gives you evidence when it happens.

Don't punish honest buyers

Heavy-handed DRM drives people to pirated copies that "just work". Protection that customers barely notice is protection that lasts:

• Works offline, every time, with no server to reach.
• No account to keep alive: the licence travels with the copy.
• A fair way to move on: let people resell a licence they no longer need, with a royalty to you, instead of passing on a copy.

A checklist

1. Decide what is worth protecting, and encrypt that part.
2. Seal each licence to the buyer's hardware: TPM on computers, Keystore or Secure Enclave on phones.
3. Mark every copy so leaks are traceable.
4. Keep everything working offline; put proof in the licence, not on a server.
5. Record releases somewhere public, so customers can check a copy is genuine.
6. Give buyers a legitimate way to resell.

Pramaan does all six. See how to use it, or start free with one app.

Questions

Related guides

• Offline Software Licensing, No License ServerLicense software that must run without internet, on air-gapped sites, field computers and labs: offline activation, and licences that carry their own proof.
• Node-Locked vs Floating Licenses ExplainedNode-locked (device-locked) and floating (concurrent) licenses compared: how each works, when to use which, and how hardware binding beats a hardware ID check.
• How to Find Who Leaked Your SoftwareForensic watermarking and traitor tracing explained: give every customer a uniquely marked copy, so a leaked copy names the licence it came from.