Custom-VM Luau protection

Your scripts, compiled into a VM nobody has studied

Cyrway compiles Luau into its own bytecode format and ships it with a per-build interpreter. Opcodes reshuffle every build, strings stay encrypted, and tamper checks run the whole time.

Start Obfuscating Read Docs

Built different, on purpose

Every layer of the engine was written for Cyrway. Nothing here is a reskin.

Custom bytecode VM

Your script is compiled away. What ships is our own instruction set running on a generated interpreter, not the source you wrote.

Per-build randomization

Opcodes, encoding keys and interpreter structure are re-randomized on every build, so a crack written for one script fits none of the others.

Encrypted everything

Strings and constants are encrypted at build time and only decrypted inside the VM as they're needed. No plaintext to scrape.

Anti-tamper & anti-env

Integrity checks, environment logging detection and debugger hooks are wired in. Tampering breaks the run instead of leaking your script.

1. Paste or uploadDrop a .lua or .luau file into the dashboard, or paste it in.
2. Pick a presetLightweight, balanced, maximum or paranoid. Seeded builds stay reproducible.
3. Ship itDownload one protected file that runs the same as the original.

Protection raises the cost of reverse engineering. No obfuscator, including this one, can promise a script is impossible to deobfuscate.