Every product runs offline. One-time payment — no subscription, no account, no telemetry.
All apps Documents & LegalBusiness & FieldEngineering & DesignMedia & AudioSystem & Privacy BundlesGuides DeliveryWhy local Windows appsAndroid apps
Guide

What offline licence verification can and cannot stop

An honest account of the offline licensing model: what device binding actually prevents, why a determined attacker will always win against a local check, and what to design for instead.

Updated 2026-11-18·Covers local-first deployment

Every vendor selling offline software eventually has to answer the same question, usually from a customer: if the app never phones home, what stops someone from copying it? The honest answer has two halves, and most vendors only tell you the first.

What a local check does stop

A signature check that binds a licence to a device fingerprint stops the ordinary forms of sharing, and those are the ones that actually cost money:

  • Copying a key to a second machine. The fingerprint will not match.
  • Reselling a code. The buyer's machine will not activate.
  • Sharing one purchase with an office. One code, one machine.
  • Keeping a working copy after a refund. Refund triggers revocation on the next activation.

In practice, these four cases are where the overwhelming majority of lost revenue sits. They are not attacks; they are convenience. Someone emails a colleague their licence because it is easier than buying a second seat. Device binding makes that fail politely, which is all it needs to do.

What it cannot stop

A determined attacker with the binary on their own machine can patch the check out. This is not a weakness of a particular implementation — it is a property of the situation. The verification code runs on hardware the attacker controls, with a debugger and unlimited time. There is no cryptographic construction that survives that; anyone claiming otherwise is either using a hardware dongle or selling you something.

Obfuscation raises the cost. It does not change the outcome. A vendor who tells you their offline scheme is unbreakable has either not thought about it or is not being straight with you.

Why we still do it, and say so

Because the alternative is worse. A cloud check means the software stops working when the vendor has an outage, when the customer's network is down, or when the vendor goes out of business. For software running in a clinic, an evidence room or an air-gapped facility, "the licence server is unreachable" is not an acceptable failure mode.

So the design target is not "unbreakable". It is: make casual copying inconvenient, keep the software working when everything else fails, and do not lie to the customer about the boundary. That is a defensible product decision, and it is also the one that survives contact with a customer who has been burned by a licence server.

What this means when you buy

  • Ask what happens when the vendor disappears. With a local check, the answer is "nothing changes". With a cloud check, the answer is usually silence.
  • Ask what happens on a machine replacement. A fair policy re-issues at no charge at least once per year; a hostile one charges you for the privilege of replacing a laptop.
  • Ask whether the check is documented. A vendor who will describe the scheme and its limits is more trustworthy than one who calls it proprietary and stops there.

The measure of a licensing scheme is not how hard it is to crack. It is whether it treats paying customers well while making the free-rider path slightly more annoying than paying.

Questions

Could someone crack the licence check?
Yes. Anyone with the binary and enough time can patch a local check. The goal is to stop casual copying and resale, not to defeat a determined reverse engineer — no purely software scheme can do the latter.
What happens if I replace my computer?
The fingerprint changes and the licence needs re-issuing. FutureDev17 re-issues once per paid seat per 12 months at no charge.