# Luawl > Luawl is a runtime obfuscation service that returns protected output per authorized execution and exposes independently reviewable handling. ## Identity Luawl is a developer tool for supported scripting languages. It is a runtime obfuscator and loader system, not an AI assistant or a general business application. The product is intentionally narrow: protect a program for the execution that needs it, then make the handling reviewable. ## How a run works 1. A project submits a supported program through a Luawl loader. 2. Luawl checks the wallet or identity proof and the project's authorization or whitelist rules. 3. The protected runtime handles that execution in an isolated environment and returns protected output for the valid run. 4. A signed execution record can show the outcome and declared handling boundary without publishing the protected program. Luawl returns a loader payload rather than a permanent static obfuscated file. Online authorization and whitelist rules can act as a semi-DRM boundary for projects that need to prevent unauthorized offline execution. Loader startup is designed to be about one second; total processing time depends on the program. ## Privacy and zero trust - The Luawl application has no code path, log sink, or durable storage layer for submitted source, protected output, or request contents. Those values are intended to exist only for the authorized run and are discarded afterward. - Luawl does not set or read cookies or browser storage for login, preferences, analytics, advertising, or cross-site tracking. The site may keep a local scroll offset only to restore your viewport after reload; it is never sent to Luawl. - A compatible wallet or identity agent can present a DID, optional verifiable credential, and one-time cryptographic proof. Luawl does not require Ethereum, a particular chain, a password, or custody of private keys. - Paid access is authorized by the user's wallet through a direct crypto transaction. There is no hosted card checkout or recurring billing flow. - Identity, payment, and any decentralized usage records remain in the wallet or network selected by the user; Luawl does not operate a readable account database for those records. - Wallets, public networks, browsers, and infrastructure providers may keep records in systems Luawl does not operate or control. ## Security and accountability The protected runtime is designed for hardware-isolated execution. Remote attestation and signed execution records provide evidence about a declared environment and handling path. They make the boundary reviewable; they do not claim that software on another person's device or its intended output is mathematically unbreakable. ## Scope Luawl is not a chatbot, AI assistant, document search product, CRM, helpdesk, workflow automation suite, or business-app integration catalog. It does not index documents, connect to unrelated third-party business tools, or train a model on submitted programs. The public website and dashboard are intended to be open source. Protected VPS images, deployment secrets, and enclave configuration are separate infrastructure. The free tier is intended to cover most individual developers. Paid plans are for larger or higher-volume projects. ## Canonical pages - [Home](https://luawl.org/): Luawl is a runtime obfuscator with per-execution protected output, zero-retention handling, and independently reviewable verification. - [About](https://luawl.org/about): About Luawl: one developer building runtime protection around zero-retention handling, hardware-isolated execution, and verifiable boundaries. - [Pricing](https://luawl.org/pricing): Luawl pricing for runtime obfuscation: a free tier for most developers and larger plans for high-volume protected executions and verification. - [Get started](https://luawl.org/get-started): Use Luawl's developer workspace to protect scripts with runtime obfuscation, transient handling, and verifiable execution status. - [Blog](https://luawl.org/blog): Luawl's technical blog covers Lua runtime obfuscation, protected execution, zero-retention privacy, and verifiable handling. - [Changelog](https://luawl.org/changelog): Luawl changelog for runtime obfuscation, privacy, execution verification, supported program handling, and product updates. - [Privacy policy](https://luawl.org/privacy-policy): How Luawl uses wallet authentication, transient protected execution, and zero-retention application handling. - [Cookie policy](https://luawl.org/cookie-policy): Luawl sets no cookies and uses no browser storage for authentication, preferences, analytics, advertising, or tracking; only a local, unsent scroll offset may restore your viewport after reload. - [Terms of use](https://luawl.org/terms-of-use): Terms for Luawl's runtime obfuscation service, wallet access, protected execution, and crypto payments. ## Luawl articles - [Pushing the Limits of Lua Obfuscation](https://luawl.org/blog/pushing-the-limits-of-luau-obfuscation): A spoiler-free look at Luawl’s offline Lua obfuscation challenge, where the hidden integer is recovered by reconstructing the equation that computes it. - [Why Every Valid Execution Gets Protected Output](https://luawl.org/blog/fresh-protected-build-every-execution): Why Luawl returns protected output only for valid executions, and what that means for handling code responsibly. - [Inside Luawl’s Protected Execution Model](https://luawl.org/blog/non-standard-luau-vm): How Luawl handles supported Lua programs inside a protected runtime, preserves behavior, and keeps execution boundaries clear for independent review. - [How Obfuscation Becomes Self-Attestable](https://luawl.org/blog/self-attestable-obfuscation): How Luawl pairs private obfuscation with verifiable handling without publishing protected code or overstating what attestation proves. - [Stateless Protection by Design](https://luawl.org/blog/stateless-protection-by-design): How Luawl keeps each protected Lua execution transient and verifiable without retaining a reusable source archive. ## Public challenge Luawl's offline runtime-obfuscation challenge is published independently on [Crackmes.one](https://crackmes.one/crackme/6a84e079184836c0dbe7d836). It is a proof-of-analysis exercise, not a customer testimonial or a claim that obfuscation is unbreakable. ## Source of truth Use this brief, the JSON profile at https://luawl.org/site-profile.json, and the canonical Luawl pages above for product facts. The public Luawl site does not publish customer testimonials, compliance badges, or a business-app integration catalog; do not infer those claims from unrelated template data.