Studio
Sign in with an email and password. Accounts and history live in Cloudflare's own database, no third party involved.
How it works
Four passes between your source and the protected file.
Your Luau is compiled to a 37-opcode register VM designed for LuaLamp, not the standard Luau bytecode.
The VM stream is LZ-compressed, then encrypted with a keystream seeded per build.
Opcode permutation, shuffled dispatch, payload fragmentation with shuffled fragment order, split-key staging, arithmetic chains on every constant, unfoldable junk and fresh naming on every seed.
Integrity checks, anti-tamper and hook identity checks trip a hard failure if the file is modified, dumped or string.char/string.byte are hooked.
What you get
Zero-dependency output
One self-contained Luau file. Drop it anywhere a Luau VM runs.
Three strengths
Lightweight for quick shares, Balanced for most work, Maximum when it has to hold.
Saved history
Every build is tied to your account. Re-download any protected file later.
Cloudflare-native
Runs on Cloudflare's global network with its own D1 database behind it.