Anti reverse engineering
Attach a debugger, patch the binary, or dump the strings — there is no local branch that says yes. The verdict is minted off the machine, so a patched client can only ask and be told no.
Issue a key, lock it to a single machine, and keep verifying it while your app runs. Revoke it and the client on that PC closes within a minute — one platform between your software and everyone who uses it.
No card · 1,000 keys free · Cancel anytime
Your app sends the key the user typed. Nothing is granted on the key alone — it is matched to the machine it was bound to, fingerprinted, signature-checked, and only then exchanged for a session that dies in a minute.
Patch the binary, attach a debugger, or replay yesterday's token and the grant never exists. There is no local check to flip — the answer comes from outside the machine.
Security console
app_x9k2_prod · v2.4
key received · parsing payload
A cracker cannot patch out a verdict that was never stored locally. Every grant is minted server-side, bound to a device fingerprint, and expires in sixty seconds — so the usual attacks have nothing to aim at. Spoofing the hardware only invalidates the binding it was trying to reuse.
Attach a debugger, patch the binary, or dump the strings — there is no local branch that says yes. The verdict is minted off the machine, so a patched client can only ask and be told no.
Swap a serial and the composite fingerprint still will not line up. Device identity is several hardware signals folded into one signed token, so a spoofer breaks its own binding instead of escaping it.
38 ms p95 from the nearest edge. Checking a key remotely costs less than most apps spend parsing a config file on startup.
Kill a key and the running client closes itself inside a minute. Nothing cached outlives the decision you made.
Fifteen languages, one shape of call. Same key, same answer — Electron, .NET, Unity, or a plain command line.
FAQ
Still stuck on something? The docs cover the whole API, and support answers on the same day.
Generate one from the dashboard or hit the API. Every key comes back with its format, its seat limit, and its expiry already attached — no extra call to make it usable.
Yes. Bind the key to a hardware ID on first activation and it stops working anywhere else. One seat, one machine, and moving it is a deliberate action you take, not something the user can do quietly.
The next verification fails and the client on that machine closes within a minute. No waiting for a session to expire, no cached grant to outlive the decision.
Your app sends the key and its hardware ID to a single endpoint. The response is signed, short-lived, and safe to cache briefly — so a network hiccup slows a check, it never bricks a paying user.
A key can validate offline for a window you choose, usually twenty-four to seventy-two hours. After that the client has to reach the API once to renew the grant before it keeps running.
Anything that can make an HTTPS request. First-party SDKs cover JavaScript, Python, C#, Java, Go, PHP, Rust, and C++, and the raw endpoint is documented for everything else.
Reset the hardware binding from the dashboard and the next activation claims the new machine. Previous bindings are logged with a timestamp, so you always know what moved and when.
Public beta opens in