vodka / Roblox key system
A free Roblox key system. Keys, HWID and delivery, in one place.
Run a key system for your Roblox script without paying for one: free-key tasks, HWID locking, revocation and a Discord bot, with protection and a stable loadstring in the same workspace.
Yours from
the first line.
Saved privately
Validated before publishing
Your next release, same address
Your release workflow / illustrated
The short version
A key system that lives on the server.
vodka runs a free key system for your Lua and Luau scripts. Set your free-key acquisition tasks and their order, choose key lifetimes, add HWID locks, and revoke or blacklist keys when you need to. Every one of those decisions is enforced on the server, not trusted to the loader.
You can also run no key system at all and ship a protected loadstring on its own. The key system is a choice per script, not a requirement.
An honest boundary
A community link visit is not verified group membership, and a delivery count is not proof a script actually ran.
vodka distinguishes authorized deliveries from client-reported starts rather than dressing one up as the other.
The pieces
Redemption, tracing and import.
A Discord bot that runs it
One setup provisions your server: players redeem and manage their own keys in Discord, and you issue, revoke and read stats from chat, with ticketing and moderation alongside it.
See the Discord bot and the developer API if you want to automate issuing and revoking keys.
Leak tracing and key import
Each keyed delivery carries a traceable fingerprint, so a casually leaked copy maps back to the buyer's key. You can also bind each key to one machine with opt-in HWID locking.
Moving in? Bulk-import your existing keys so your current users keep the keys they already have.
The money stays yours
Monetize free keys, keep every cent.
If you monetize access, you connect your own work.ink, LootLabs or Linkvertise account as a key-claim step. The provider pays you directly, and vodka verifies completion on the server so the step cannot be click-skipped.
vodka takes no cut and holds none of your revenue. Read how creator earnings work, or see that it is free either way.
Where protection ends
Honest about the boundary.
No client-side obfuscator can make a delivered secret unrecoverable. An authorized client receives the code it runs, so running the loader can recover the strings and reverse the arithmetic. This is true of every obfuscator, vodka included, and we will not pretend otherwise.
What protection does is raise the cost of casual inspection and copying. What actually gates access is server-side: the key check, expiry, revocation and HWID locks are all enforced where the client never sees how the decision was made. Keep anything that must stay secret on a server, and read the benchmarks for exactly what the engine does and does not defeat.
Where to go next
Where to go next.
HWID locking
Bind a license key to one machine, enforced server-side, with bounded player self-service resets.
The obfuscator
Encoded constants, flattened control flow and an opt-in bytecode VM for your Roblox Lua and Luau scripts.
Reproducible benchmarks
Run the exact harness yourself: protection resistance, runtime overhead and the weaknesses we do not hide.
What it costs
Free for creators and players. Monetize with your own ad-link provider; the platform never holds the money.
vodka vs Luarmor
The dated, sourced comparison of documented workflows, pricing and protection.
Guides and writing
Honest notes on protecting and shipping Luau: what the build does, and where client-side protection ends.
Questions
A few things worth knowing.
01Is vodka's key system really free?
Yes. Running a key system on vodka costs nothing, for you and your players: free-key tasks, lifetimes, HWID locks, revocation and the Discord bot are all included. If you monetize access, your own ad-link provider pays you directly and vodka takes no cut.
02Is the key check enforced on the server?
Yes. Key validity, expiry, revocation, the blacklist and HWID locks are all decided on the server in the verify handshake, not in the distributed loader. A client cannot grant itself access by editing what it received.
03Can I lock a key to one device?
Yes. Opt-in HWID locking binds a key to the first machine that runs it and refuses the rest, with bounded player self-service resets. It is enforced server-side, and you can also ban by HWID.
04Can I keep my existing keys if I switch?
Yes. vodka has a bulk key importer: export your current keys, import them onto your script, and they keep verifying for your users without a re-redeem. You recreate your access rules and distribute the new vodka loadstring after testing.
Keep building
Your next release starts here.
Bring your original source. Make the workspace your own.