This sample uses a public key to authorize LuaRN. Local mode processes the Lua code in your browser. Create a separate key for each HTTPS origin in the LuaRN dashboard.
Configure and process
The public SDK authorizes this HTTPS website, then obfuscates Lua in the visitor’s browser. Lua source is not uploaded to LuaRN.
Enter the public key created for this website's exact HTTPS origin.
Generated Lua
The result appears here after authorization succeeds. Download it or copy the generated code for your app.
No output yet.
How it works: create a key for the exact HTTPS site origin in the secure LuaRN console, then use the generated snippet. Each key has a daily quota and optional expiry. Lua source stays in the visitor’s browser; the public authorization endpoint receives only key and usage metadata. Never put admin credentials in website code. Origin checks limit normal browser use but are not strong authentication against custom clients that can forge HTTP headers. Sites with a strict Content Security Policy must allow scripts and connections to https://luarn.pages.dev and scripts from https://esm.sh for the current engine loader.