Protection Overview
Follow a script from source upload through protected builds and loader delivery.
The build flow
Luaward keeps each source upload as a versioned build request. The source is encrypted before storage, and a compiler worker turns it into a protected artifact. Build states are Queued, Building, Ready, and Failed.
The loader does not return a build until the edge service authorizes the request and a ready build is available. If the newest build fails, the previous ready build can remain in service.
What you control
- Select a protection preset for compiler output.
- Enable keyless access or require a license key.
- Choose whether the loader shows Luaward's informational messages.
- Enable periodic checks for keyed sessions.
- Upload new source, inspect build history, and roll back to a ready build.
See Protection presets, Runtime settings, and Loader checks for details.
What protection means
Luaward compiles source into a custom VM-based representation with per-build changes to the generated output. The selected preset changes the transformation depth and output overhead. This raises the effort needed to inspect a script; no client-side protection can guarantee that a determined user cannot analyze the code while it runs.
Build limits
Source uploads are limited to 2 MB. A workspace can have up to six queued or building jobs at once; wait for a job to finish before submitting more.