LUAWARD
Language
SECURITY & ARCHITECTUREUpdated 2026-11-19

Verifiable security from the Luau compiler to your workspace

Luaward isolates runtime code protection from account and source governance: every script build compiles into a fresh Stack VM, stored source is encrypted with AES-256-GCM behind a 2FA gate (or discarded entirely in Zero-Retention mode), and key pages run on an isolated host.

DEFENSE IN DEPTH

Five layers of technical controls

L1

Per-Build Randomized Stack VM

COMPILER & RUNTIME

Your raw Luau code is compiled on the server into custom Stack VM bytecode with freshly permuted instruction opcodes and encrypted constants on every build. The loader uses a challenge-response handshake to deliver single-use encrypted payloads.

Per-build opcode permutationChallenge-response loader90-second kill switch & rollback
L2

AES-256-GCM Source Encryption & Zero-Retention

DATA AT REST

When source retention is enabled, raw scripts are encrypted at rest with AES-256-GCM using authenticated envelopes and require an active 2FA verification to view. When Zero-Retention is enabled, raw source is discarded right after compilation.

AES-256-GCM authenticated envelopes2FA gate before reading stored sourceOptional Zero-Retention compilation
L3

Device Binding (HWID) & Replay-Protected Sessions

LICENSE AUTHORITY

License keys bind to the device identifier reported by the runtime. Loader sessions carry HMAC-signed tokens and single-use replay nonces, re-checking ban, expiration, and HWID state on every heartbeat.

1 key per device ID (HWID)Single-use replay noncesLive heartbeat revocation checks
L4

Scoped REST API v3, IP Allowlist & OAuth 2.1 MCP

AUTOMATION & AI BOUNDARIES

Developer API keys support separate read/write scopes, per-project boundaries, and CIDR IP allowlists. AI agent connections through the MCP server use OAuth 2.1 with PKCE or dedicated lwm_ tokens that can be revoked in one click.

Project-scoped API keys & CIDR allowlistOAuth 2.1 + PKCE for MCP clientsAtomic Redis rate-limit enforcement
L5

Passkeys, TOTP 2FA, Host Isolation & Audit Redaction

ACCOUNT & INFRASTRUCTURE

Accounts support WebAuthn Passkeys and TOTP 2FA. Public key pages run on key.luaward.com isolated from dashboard session cookies, database roles enforce least privilege, and secret tokens are redacted from audit logs.

WebAuthn Passkeys & TOTP 2FAIsolated key.luaward.com hostAutomatic audit log secret redaction
SOURCE CODE GOVERNANCE

Two source retention modes, configurable per script

Decide for each script whether you want the convenience of browser editing or strict zero-storage compilation.

1. Encrypted Source RetentionDEFAULT · 2FA GATED

Luaward encrypts your Luau source with AES-256-GCM so you can view, edit, and recompile versions in the web dashboard or pull them via @luaward/cli.

  • Encrypted at rest with AES-256-GCM
  • Requires 2FA enabled on your account to unlock and view raw code
  • Included in your full account data export
2. Zero-Retention ModeZERO RAW STORAGE

Luaward uses your uploaded source solely in memory to compile the Stack VM bytecode, then permanently discards the raw source text.

  • Raw Luau source is never written to persistent storage
  • Supported in the web UI and via 'luaward push --no-store-source'
  • Also available via Quick Obfuscate (120-second ephemeral RAM build)

SECURITY FAQ

Common security and privacy questions

Contact support →

No honest platform claims unbreakable client-side code. Luaward raises the cost of reverse engineering by generating a randomized Stack VM per build, verifying keys and HWIDs on the server, and streaming single-use payloads.

Your scripts deserve better than plain text.

Public sign-ups are opening soon. Join our Discord community for early access updates and live news.

Join the Discord