Lua, shipped
without the leak.
An opinionated delivery layer for Lua creators — bytecode VM, per-user keys, hardware binding, and a Discord console. You upload the script, we hand out one URL.
// one project, one endpoint
$ luapot deploy \
--project "aurora" \
--source ./main.lua
✓ compiled → vm bytecode
✓ issued → project endpoint
// share one URL with buyersBuilt for creators who ship, not babysit.
Every primitive you'd otherwise build in a weekend, bolted in and versioned. No glue code. No cron jobs.
- 01Bytecode obfuscation
Sources compiled to a VM — strings encrypted, control flow flattened, varargs preserved across wrapping.
VM - 02Per-Discord-user keys
One key per user per project. Issued on command, idempotent, revocable in a single click.
KEY - 03Hardware binding
Keys bind to the executor HWID on first exec. Owner-configurable reset budget with server-enforced cap.
HWID - 04Signed loadstring
A single URL, signed handshake, short-lived session tickets, rotating per-execution payload.
TLS - 05Discord control panel
Slash commands, embedded buttons, autocomplete, strict per-guild isolation. Buyers self-serve.
BOT - 06Live telemetry
Real-time executions, denial reasons, active sessions. Revoke any live session from the console.
OBS
From paste to production in 3 moves.
- 01AUTHSign in with Discord
Your workspace boots the instant OAuth resolves. Nothing to verify, nothing to confirm.
- 02UPLOADDrop your script
Paste Lua, press build. Obfuscator returns bytecode, we return a loader URL.
- 03SHIPShare the one-liner
Drop it in your server. Buyers redeem a key through the bot, HWID locks, they're running.