{
  "schemaVersion": "1.0",
  "name": "Luawl",
  "canonicalUrl": "https://luawl.org",
  "oneSentence": "Luawl is a runtime obfuscation service that returns protected output per authorized execution and exposes independently reviewable handling.",
  "identity": {
    "category": "Developer tool",
    "language": "Supported scripting languages",
    "model": "Per-execution runtime protection",
    "audience": "Developers shipping protected programs"
  },
  "whatItDoes": [
    "Accepts supported programs and returns a loader payload rather than a permanent static obfuscated file.",
    "Handles each authorized execution inside an isolated runtime and delivers protected output for that run.",
    "Supports online authorization and whitelist rules as a semi-DRM control for projects that must prevent unauthorized offline execution.",
    "Produces a verification record that can be reviewed without publishing the protected program."
  ],
  "howItWorks": [
    "A loader requests one execution; Luawl validates the request, protects the run, and returns the result only when the requirements pass.",
    "The runtime can decrypt and handle protected material during execution so an offline copy is not a standing execution permission.",
    "Typical loader startup is designed to be about one second; total processing time depends on the submitted program."
  ],
  "privacy": {
    "applicationBoundary": "The Luawl application has no code path, log sink, or durable storage layer for submitted source, protected output, or request contents.",
    "retention": "Submitted source, protected output, and request contents are intended to exist only for the authorized run and are discarded afterward.",
    "tracking": "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.",
    "externalRecords": "Wallets, public networks, browsers, and infrastructure providers can keep records in systems Luawl does not operate or control."
  },
  "identityAndPayment": {
    "authentication": "A compatible wallet or identity agent can present a DID, an optional verifiable credential, and a one-time cryptographic proof.",
    "requirements": "Luawl does not require Ethereum, a particular chain, a password, or custody of private keys.",
    "payment": "Paid access is authorized by the user's wallet through a direct crypto transaction; Luawl does not operate a hosted checkout or recurring card billing flow."
  },
  "security": {
    "model": "Zero-trust infrastructure with a self-attestable execution boundary.",
    "execution": "The protected runtime is designed for hardware-isolated execution.",
    "verification": "Remote attestation and signed execution records provide evidence about a declared environment and handling path without exposing the protected program.",
    "limit": "Attestation and obfuscation increase reviewability and analysis cost; they do not make software on another person's device mathematically unbreakable."
  },
  "decentralizedArchitecture": "Identity and payment are wallet-authorized, and any decentralized records created for a user remain in systems that user or the selected network controls rather than in a Luawl account database.",
  "openSource": "The public website and dashboard are intended to be open source. Protected VPS images, deployment secrets, and enclave configuration are separate infrastructure.",
  "pricing": "The free tier is intended to cover most individual developers; paid plans are for larger or higher-volume projects.",
  "notLuawl": [
    "Not a chatbot, AI assistant, document search product, CRM, helpdesk, workflow automation suite, or business-app integration catalog.",
    "Not a hosted card checkout, recurring billing service, or password-based account system.",
    "Not a promise that protected software or its intended output is impossible to analyze."
  ],
  "canonicalPages": {
    "home": "https://luawl.org/",
    "about": "https://luawl.org/about",
    "pricing": "https://luawl.org/pricing",
    "getStarted": "https://luawl.org/get-started",
    "blog": "https://luawl.org/blog",
    "changelog": "https://luawl.org/changelog",
    "privacyPolicy": "https://luawl.org/privacy-policy",
    "cookiePolicy": "https://luawl.org/cookie-policy",
    "termsOfUse": "https://luawl.org/terms-of-use"
  },
  "articles": [
    {
      "title": "Pushing the Limits of Lua Obfuscation",
      "url": "https://luawl.org/blog/pushing-the-limits-of-luau-obfuscation",
      "category": "Engineering",
      "description": "A spoiler-free look at Luawl’s offline Lua obfuscation challenge, where the hidden integer is recovered by reconstructing the equation that computes it."
    },
    {
      "title": "Why Every Valid Execution Gets Protected Output",
      "url": "https://luawl.org/blog/fresh-protected-build-every-execution",
      "category": "Runtime",
      "description": "Why Luawl returns protected output only for valid executions, and what that means for handling code responsibly."
    },
    {
      "title": "Inside Luawl’s Protected Execution Model",
      "url": "https://luawl.org/blog/non-standard-luau-vm",
      "category": "Engineering",
      "description": "How Luawl handles supported Lua programs inside a protected runtime, preserves behavior, and keeps execution boundaries clear for independent review."
    },
    {
      "title": "How Obfuscation Becomes Self-Attestable",
      "url": "https://luawl.org/blog/self-attestable-obfuscation",
      "category": "Product",
      "description": "How Luawl pairs private obfuscation with verifiable handling without publishing protected code or overstating what attestation proves."
    },
    {
      "title": "Stateless Protection by Design",
      "url": "https://luawl.org/blog/stateless-protection-by-design",
      "category": "Engineering",
      "description": "How Luawl keeps each protected Lua execution transient and verifiable without retaining a reusable source archive."
    }
  ],
  "publicChallenge": "https://crackmes.one/crackme/6a84e079184836c0dbe7d836"
}