A free workspace for the scripts you put yourself into. Protect your source, add a key system only if you want one, and see what happens after you publish.
A WORKSPACE THAT GETS OUT OF YOUR WAY
Meet your new release routine.
Try a little of it below.
1-- Your original source2local player = game.Players.LocalPlayer3local name = player.DisplayName45local function welcome(message: string)6print(message .. ", " .. name)7end89welcome("Welcome back")
MADE FOR THE WAY YOU BUILD
Your editor, protection, keys and activity.
Finally in the same place.
FROM FIRST DRAFT TO WHAT'S NEXT
A proper home for the code you wrote. Private drafts, retained versions, and an editor that understands Lua and Luau.
Build a key flow around your community. Order tasks, choose lifetimes, and revoke access when you need to.
Publish a validated build to one stable loadstring. Keep player activity, deliveries and reported runs within reach.
-- Something worth keeping yours. local Players = game:GetService("Players") local player = Players.LocalPlayer local function welcome(name: string) print("Welcome back, " .. name) end welcome(player.DisplayName)
A proper home for the code you wrote. Private drafts, retained versions, and an editor that understands Lua and Luau.
Build a key flow around your community. Order tasks, choose lifetimes, and revoke access when you need to.
Publish a validated build to one stable loadstring. Keep player activity, deliveries and reported runs within reach.
THE DETAILS MAKE THE DIFFERENCE
Each build runs automatically through a per-function bytecode VM, with encoded strings and numbers, flattened control flow and a watermark. A failed build leaves your working release in place.
Compare, restore and build on what came before. Your source history stays with your script.
Flexible task flows for free keys — or no key system at all. The gate is optional; publish a protected loadstring and you're done.
Run it from Discord.Players redeem and manage keys in your server.One loadstring points to your latest published build. Your players keep their link. You keep moving.
loadstring(game:HttpGet("https://use.vodka/scripts/your-script"))()EXAMPLE ADDRESS · YOURS IS GENERATED IN THE WORKSPACETHE COMMUNITY, ONE SEARCH AWAY
Browse by game. Find a new favorite. Give your next release a place in Discovery.
Explore DiscoveryPublished scripts are listed automatically.Every published build runs through our engine automatically — there is nothing to configure. Supported functions are compiled into a per-function Luau bytecode VM; strings and numbers are replaced with encoded expressions, control flow is flattened, local names are rewritten, and the output is minified and watermarked. Functions the VM does not support keep native execution alongside the other transformations.
Create an account and bring your original Lua or Luau source. Paste it into the editor or upload a file. We generate the delivery loadstring after your build is validated.
You can access your own originals and drafts. Authorized site administrators can inspect stored source for support and moderation, and source access is audited. Public Discovery never includes originals.
New artifacts are parsed and compiler-checked before publication. Failed or cancelled builds leave the previous working release available. You can compare and restore earlier source versions.
Yes. Order your own acquisition tasks, configure timers and available captcha, and set key lifetimes. Tasks repeat for every newly generated free key. Community visits do not verify Roblox group membership.
You attach your own ad-link provider — work.ink, LootLabs or Linkvertise — as a step players complete to claim a free key. The provider pays you directly; vodka never holds the money and takes no cut. Using a key system at all is optional.
No. Protection deters casual inspection, but an authorized client can still inspect delivered code and runtime behavior. Expiry, revocation and access validation are enforced on the server.
LESS BETWEEN YOU AND YOUR NEXT RELEASE
Your source. Your community. Your next chapter.