Who runs vodka
One developer builds, ships and supports vodka. There is no company name, no office address and no legal entity behind it that we could honestly print here, so we won't invent one. It is a small, independent operation, and we think that is a feature: you talk to the person who writes the code, decisions are made in minutes rather than committees, and there is no incentive to lock you in to keep a quarterly number up. The flip side is honest too. It is one person, not a 24/7 support desk, and we would rather set that expectation than overpromise.
The engine is our own, and it is open
vodka does not resell a black box you upload to and hope about. The protection that runs on every build is our own engine, published as an open project you can read and run. Every protection and performance claim comes from a harness you can execute yourself. See the benchmarks, which deliberately report where protection is weak as well as where it is strong. We would rather you verify than trust us.
How to reach support
Support, questions and bug reports all go to one place: the Discord server. It is a direct line to the person who built the thing you are asking about, not a ticket queue that routes your message to someone reading from a script. Premium access and anything that needs a human is arranged there too.
What happens if it goes away
The honest fear with any small tool is “what if it just vanishes?” So here is how vodka is built to not strand you:
- You keep your own loadstring. Your distributed loader is yours. You can export your original source and every retained version from the dashboard and leave at any time. Nothing holds your code hostage.
- Source versions are retained and downloadable. Your originals, drafts and protected output are kept and restorable, so you always have a copy to walk away with.
- The platform never holds your money. If you monetize, you connect your own ad-link provider and they pay you directly. vodka never sits between you and your earnings, so there is no balance to be trapped behind.
More on the free tier, its real limits and continuity is on the pricing page.
What we do not claim
Protection raises the cost of reverse-engineering and defeats casual inspection. It is not a vault: any secret shipped to a client is ultimately recoverable, which is true of all client-side obfuscation, not just ours. Keep real secrets and authority on a server you control. How we handle data is written out in full in the privacy statement, and the rules for using the service are in the terms.