NexusGuard

Your public license-server URL isn't set yet. Set it in Settings before protecting scripts.

Generate keys

A standard key locks itself to the first server that uses it - one buyer, one server. A master key works on any number of servers (for your own servers).

Script Script name (folder name) Key type How many Note (buyer / Discord)

Search Status

Key	Script	Status	Registered server	Last check	Note

No keys yet.

1. Choose the script

Zip the script folder (the folder that has fxmanifest.lua in it) and drop it here. Props, stream files and UI files come along untouched.

Drop a .zip here, or click to choose

2. Pick what stays editable

Ticked files ship as normal readable Lua so buyers can change them (config, translations). Everything else gets scrambled and locked.

Resource folder name

This looks like a script you've protected before

Ship it as an update (recommended)
Same keys, so everyone's existing license keeps working - buyers just drop in the new folder. The version number goes up by one. Make it a separate new script
A brand-new product with its own keys. Use this only if it's genuinely a different script.

3. Protection

Locked + license key (recommended)
Code is scrambled, then encrypted. It only unlocks on a server with a registered key. Scramble only (no key needed)
For free releases - code is unreadable but runs anywhere.

Scrambling options (all on by default)

Rename variables to look-alike junk Encrypt all text strings Hide native / function names Hide table field & method names Scramble numbers

Protected builds

Every protected zip you've made. Each build also records a fingerprint of every file in it (props included) so you can prove ownership later. Deleting a licensed build makes every copy of that download stop working - only do that if a download leaked.

Script	Build	Made	Locked	Fingerprinted	Proof

No builds yet.

Is this file mine?

Found one of your props (or any file) on another server, a leak site, or in a FiveM cache folder? Drop it here. NexusGuard checks its fingerprint against every build you've made and tells you if it came from you - and which build and date. That's your proof for a takedown.

Drop any file here, or click to choose

How to use this for a takedown

If a file matches, you have everything you need: the fingerprint, the build it came from, and the date you made it. Download that build's certificate on the Protected builds tab, and include it with your report to the platform (Tebex, Discord, a host, or a DMCA notice). The certificate lists the exact fingerprint of every file, which is independent, dated proof the work is yours.

Activity

Key registrations, blocked attempts and admin changes. Red rows are worth a look - repeated blocks on one key usually mean it was shared.

License server

The public address game servers use to check keys. It gets built into every protected script, so set it before protecting and keep it stable - if it changes, rebuild your scripts.

Public URL

Offline grace period (hours) Re-check keys every (minutes) Server moves buyers can do themselves (per 30 days)

Grace period: if your license server is offline, servers that verified recently keep running this long. Re-check: how often running servers re-confirm their key (a revoked key stops the script at the next check). Server moves: buyers can free their key from their old server with a console command (only from the server it's registered to); set 0 to make every move go through you.

Store connection

Paste this token into NexusStore (Settings → NexusGuard) so a successful sale can auto-create a license key here. Keep it secret — anyone with it can generate keys.

Integration token

Change password

Current password New password (8+ characters)

Backup

Download everything (keys, builds and their unlock keys). Keep it somewhere safe - if you lose this data, existing protected downloads can't be unlocked.

Download backup