LuaProjects, scripts & plan limits
Projects group your scripts. Limits apply across your whole workspace and are enforced by the database.
| Plan | Projects | Scripts |
|---|---|---|
| Free | 1 | 1 |
| Pro | 3 | 5 |
| Premium | 6 | 10 |
| Owner role | Unlimited | Unlimited |
Publish & update a script
Create a project, add a script, and save your Lua/Luau source. The 32-character hex file ID is what the loader uses and never changes. Save new source anytime — future authorized runs get it; a copy already running does not restart.
Issue license keys
In Keys, pick the script and generate a key. Keys belong to one script and owner. Add a note to identify the buyer and set an expiration when access should end. Give the buyer their key plus the loader snippet from the script.
First-use binding & resets
An unused key has no device binding; its first successful run stores the buyer's HWID and later runs must match it. To move a buyer to a new device, find their key and reset the HWID — the next run re-binds it.
Ban, expire & kill switch
Ban a key to return Banned; set/keep an expiry to return Expired. Disable a script (kill switch) to block all future authorized downloads for everyone until you re-enable it. None of these remove a copy already downloaded.
Keyless mode
Toggle a script to keyless to allow access without a key (the script and owner-account checks still apply, and a HWID is still required). Use it for free/public scripts.
Players & blacklist
Players shows recorded license activity. The blacklist action bans keys currently bound to a given HWID; it is not an independent device registry that auto-blocks new keys.
See the loader, error reference, and security model.