You point your app at our API, and we handle the rest: issuing keys, verifying users, locking access to specific devices, blocking abusers, and, if you want, monetizing the key handout through ads or subscriptions.

The public name is Panda Auth. The "R3" marks the third generation, a ground-up rewrite of the older Panda Key System with a faster dashboard, a cleaner API, and modern security.

Panda Auth is universal. It is not tied to one language or platform. If your software can make an HTTPS request, it can talk to Panda Auth.

• Roblox scripts and game hubs (the largest community using us today)
• Roblox executors and loaders (full session control via our WebSocket layer)
• Discord bots (premium command unlocks, per-server licensing)
• Windows desktop apps (installers, paid tools, internal utilities)
• Websites and SaaS dashboards (gating premium pages or API access)
• Mobile apps, CLI tools, browser extensions, game mods: anything that can hit a URL

The underlying contract is just HTTP, so any language works. We ship documentation and sample code for Lua, JavaScript, Python, and C#.

A few features only make sense for Roblox Lua and only work there. They're clearly labeled in the dashboard. The main one is the Virtual Storage System (VSS). It lets you ship encrypted Lua scripts that only execute inside a verified session. We also integrate with Lua obfuscators like Luraph and IronBrew.

• Keys — license keys you generate and hand out. Format looks like PANDA-XXXX-XXXX-XXXX-XXXX.
• HWID locking — bind a key to a single device so it can't be shared.
• Checkpoints — make users clear 1 to 10 ad steps before they get a key (optional).
• GetKey page — the public page where your users obtain a key.
• VSS — encrypted Lua script hosting (Roblox only).
• Dashboard — real-time stats, analytics, webhooks, branding, and team permissions.

We've been building in this space for years. Panda Auth R3 is the result of everything we learned from the earlier versions.