Why a license check belongs on the server
A license check that runs only on the user's machine is a single decision an attacker can find and flip. Moving the decision to a server you control removes the thing they would patch.
Updated
What is server-side license validation?
Server-side license validation means a server you control decides whether a copy of your software is allowed to run, not the copy itself. The client presents an identity, the server checks the license, seats and device limits, and returns an answer bound to that request.
Why does a license check in the client fail?
A client-side check is one decision in code the attacker owns. However the key is checked, the program eventually reaches a branch: valid or not. Change that branch, or make the function always return valid, and the check is gone. Obfuscation can hide the branch for longer, but it is still there.
AI makes this worse. Finding the license check is exactly the kind of question an agent answers well, because the check calls recognisable things: a key format, a date, an error message. See what AI agents are good at.
How does server-side license validation work?
- The user signs in or presents a license key from the client.
- The server checks the license against the account: whether it is active, which features it covers, how many devices are using it.
- The server returns a signed, short-lived token, ideally with something the client needs in order to work.
- The client uses the token until it expires, then asks again. Revoking a license on the server stops it at the next renewal.
Step three is the important one. If the server only says yes or no, the client can be patched to stop asking. If the server also hands over a key or a piece of configuration the software cannot run without, skipping the check leaves a broken client.
What about offline use?
Short-lived signed tokens let software work offline for a bounded time. The client verifies the signature locally and refuses expired tokens. An attacker can stop the clock on one token at most; they cannot create a new one.
What server-side licensing doesn't solve
It does not stop someone from studying or patching the client. It stops that work from producing a copy that runs for free. It also cannot protect logic that has to run on the user’s machine, which is why it is paired with obfuscation and runtime anti-tamper rather than replacing them. The full picture is in software protection for the age of AI reverse engineering.
Questions
- What is server-side license validation?
- It is licensing where a server you control decides whether a copy of the software may run or unlock a feature. The client asks, the server answers, and the answer is tied to the account, device and license, so it cannot be reused elsewhere.
- Why is a client-side license check easy to crack?
- Because it is a decision inside code the attacker controls. Somewhere a comparison returns true or false. Find that branch and change it, and the check always passes. Language models make finding that branch faster.
- Does server-side licensing require the software to always be online?
- Not always. A server can issue a signed, short-lived token that the client checks offline until it expires. The client still cannot mint its own token, so an attacker gains only the time left on one they already have.
- Can server-side licensing be bypassed?
- The check itself can be cut out of the client, but if the server also holds something the software needs to work, such as a key, a configuration or a piece of logic, cutting the check out leaves a client that does not work. That is the part that makes it hold.
- Is a signed license file enough?
- A signature stops forged licenses, but the code that verifies the signature runs on the client and can be patched to skip it. Signing helps; it does not replace a server decision.