Fixes and updates
Privacy and transparency
Luawl can now show how a protected program was handled without exposing the program itself. Each valid run produces a verification record with its outcome and status.
Verification does not depend on our dashboard. Review the run record independently without exposing protected details.
Improved
HandlingProtected runs remain inside the service boundaryVerificationA clear run record for each completed executionPrivacyIndependent review without protected detailsRuntimeClear status for each completed run
Fixed
PrivacyFixed stale verification state after re-obfuscationVerificationFixed run status appearing before completionHandlingFixed verification refresh after an expired session
Execution receipts
We rebuilt how Luawl records executions. Every valid run now has a clear verification record you can inspect after completion.
Verification makes handling reviewable without exposing protected details. Requests that do not qualify remain separate from completed runs.
Transparency keeps each execution and its verification record together across the product.
New
VerificationA clear run record for each completed executionPrivacyHandling status attached to each run recordExecutionsA review link for each completed runVerifierIndependent review of the run record
Improved
TransparencyCleaner execution details and proof states
RuntimeFaster verification updates after a run
Fixed
VerificationFixed mismatched run status after retriesExecutionsFixed delayed proof visibility for recent runs
Loader authorization controls
Projects can now define execution requirements before protected output is returned. Existing access rules stay outside the protected runtime.
Valid executions receive protected output; requests that do not qualify stop before delivery. Records separate attempts from completed runs.
New
AuthorizationExecution requirements can be set per projectLoaderClear entry point for each projectWebhooksStatus events for completed executionsProjectsProject access settings are easier to rotate
Improved
RuntimeClearer denial states for expired authorizationDashboardExecution and runtime obfuscation totals separated
Fixed
LoaderFixed duplicate build requests during retriesWebhooksFixed event ordering during rapid executions
Protected execution model
Luawl now prepares supported scripts for its protected execution model. The loader is only the entry point; protected output is returned only for a valid execution.
Each valid execution is handled independently, with the details of that handling kept behind the service boundary. Support expands only as behavior preservation is proven.
Broader Lua support will follow as compatibility and behavior-preservation tests are completed.
New
RuntimeProtected handling for supported Lua programsCompilerClear support boundaries for Lua programsRuntimeIndependent handling for each valid executionLoaderProtected output returned for valid executions
Improved
CompilerClear diagnostics for unsupported syntaxRuntimeLower startup overhead for small scripts
Fixed
RuntimeFixed conditional handling in nested control flowLoaderFixed stale status after execution requirements changed
Get started today
Luawl is easy to set up, maintain, and use. It takes less than 5 minutes to get up and running.
Intel SGX
End-to-end encryption
Welcome back
Ready to obfuscate today, Alex?
-- Paste your Lua script to obfuscate.
Scripts
Obfuscations
Compute
Traces
Terrain Generator
Character Controller
