How Licensing Works

A Nerotek license is bought once and is permanent: one payment covers the product on every server you own, with all updates for the current major version included. What the payment actually buys is a license that is bound to you — not a floating key that can be pasted into any install by anyone who copies it. Three pieces work together: the license key, the bindings, and your personal loader.

#The license key

After your payment is verified, a license key is issued for your order and delivered to you personally, together with your build. The key identifies your purchase on Nerotek's license server — it is the identity of your license. Treat it like a credential: it is yours alone, it is delivered 1:1, and sharing it is how a license ends up invalidated.

#The bindings

Licenses are IP-bound and hardware-bound. When the product is activated on a server, that install is bound to the server's IP address and hardware — every server install is bound to the buyer's own infrastructure. Restarts and normal operation are unaffected; the binding only becomes visible when the underlying server itself changes, and that is exactly what the reset flow is for (see IP & Hardware Binding).

#The personal loader and the license server

The product does not run from a jar you download from a portal — it is activated by your personal loader, a small launcher build issued to you alone. On activation, the loader validates your license against Nerotek's license server. That connection is protected end to end: it runs over TLS on port 8443, with mutual TLS (mTLS) at the application layer, so the loader and the license server authenticate each other — not just an encrypted pipe, but a verified one on both sides.

The practical meaning: a copied build without your loader and your license simply does not activate, and a loader issued to someone else does not validate for you. Piracy is handled by the architecture instead of by honor-system serial numbers.

#What this means in practice