LuaLock is a script obfuscator for Lua, Luau, and Roblox. Rather than renaming variables or inserting junk code, it compiles your source into a private bytecode instruction set and runs it inside a virtual machine generated fresh for every build.
Because the opcode mapping is unique per build, standard decompilers — which target the public PUC-Rio bytecode format — produce nothing useful against LuaLock output. Constants are encrypted, strings are hidden, and runtime tamper checks stop anyone patching the VM in place.
Upload or paste a .lua or .luau file and LuaLock returns hardened output in seconds. The pipeline lowers your code to a custom register-based bytecode, generates a matching VM, then remaps opcodes and folds in integrity checks so two builds of the same script never look alike. See the full feature list for the engine internals.
LuaLock targets Lua 5.1, 5.3, and 5.4, LuaJIT, Luau, and Roblox Luau. Each target produces output tuned for the VM your code actually runs on, so protected scripts behave exactly like the originals.
Every account starts with a free trial of 3 obfuscations — no credit card required. See pricing and plans for Flex, Pro, Max, and Enterprise. For automated pipelines, install the cross-platform LuaLock CLI and read the REST API and CLI documentation.
Use an obfuscator that compiles your code to a private bytecode virtual machine rather than one that just renames variables or encodes strings. LuaLock compiles your Lua or Luau source into a per-build instruction set executed by a generated VM, so standard decompilers can't recover it.
The strongest options are VM-based obfuscators. LuaLock covers Lua 5.1–5.4, LuaJIT, Luau, and Roblox in one service; Roblox-focused alternatives include Luraph and MoonSec. Renamers and string encoders are weaker because your program's structure survives.
Yes — a free trial (3 files), Flex at $0.05 per file, Pro at $9.99/month, Max at $49.99/month, and Enterprise. Every tier uses the same engine; higher tiers add volume, API keys, and support, never weaker protection.
No. LuaLock compiles source into a private bytecode format with per-build opcode remapping. Standard Lua decompilers like unluac and LuaDec target PUC-Rio bytecode and produce nothing useful against LuaLock output.
No. Source and output are processed in memory and discarded when the response is sent — nothing is written to a database or logged, unless you explicitly opt in to saving a build to your history.