Lua protection
Lua script protection with encryption, obfuscation, and licensing
Ship Lua code to customers without shipping readable source. Trust Secure obfuscates and encrypts your Lua, delivers it through a signed loader, and ties every copy to a license you control.
Overview
Lua is easy to distribute and just as easy to copy. Once a .lua file is on another machine, the plain text can be read, edited, and reshared. For anything you sell or license, that is a direct revenue problem.
Trust Secure protects Lua in layers: your code is obfuscated, packaged, and encrypted, then delivered at runtime only to authorized environments through a loader that verifies a signed authorization. The readable source never sits on the customer's disk.
This works for FiveM resources and for standalone Lua projects. You keep a normal workflow — upload, license, distribute — while your customers run the code without ever holding your original source.
Key benefits
Source stays private
Customers receive a signed loader and encrypted bundle, not your original .lua files.
Layered obfuscation
Even the delivered code is transformed, so a runtime dump is far harder to read, understand, or reuse.
License-bound execution
Code only loads for a valid, active license — revoke it and execution stops on the next run.
Works standalone or in FiveM
Protect a FiveM resource or a standalone Lua project with the same licensing and delivery model.
How it works
- 1
Upload your Lua
Add a single Lua file or a full project. Trust Secure prepares an obfuscated, encrypted build.
- 2
Create a license
Generate a key, optionally IP-locked and time-limited, for each customer.
- 3
Distribute the loader
Send the protected package or a one-time download link. The loader authorizes and loads the real code at runtime.
- 4
Update and revoke anytime
Publish new builds that reach authorized users automatically, and revoke access the instant you need to.
What you get with Trust Secure
Signed, authenticated delivery
Protected code is delivered with a signature the loader verifies, so a spoofed server can't inject code into your resource.
AES-256-GCM at rest
Bundles are encrypted at rest and only decrypted for authorized runtimes.
Instant revocation
Disable a key and the protected code stops loading on the next start.
Monitoring & security events
See where your code runs and get alerted to suspicious activity.
Related pages
Frequently asked questions
What is the difference between obfuscation and this protection?
Obfuscation transforms your code so it is hard to read. Trust Secure adds encryption, signed runtime delivery, and licensing on top, so the readable source is never stored on the customer's machine and only runs with a valid license.
Can I protect a single Lua file?
Yes. You can protect one standalone Lua file or a full multi-file project.
Will my Lua still run normally?
Yes. The protected code runs the same as your original for authorized users; the loader handles authorization transparently.
Can I change the code after I distribute it?
Yes. Publish a new protected build and authorized environments load the updated code on their next start, with the same license.
Is protected Lua impossible to reverse?
No. Any code that runs on a machine you don't control can eventually be analyzed. Trust Secure makes that far more expensive and gives you revocation and tracing to respond to leaks.
Keep your Lua source private
Upload your Lua, issue a license, and distribute a protected build in minutes.
Get started free