Sell access instead of files. Every buyer gets their own key, it locks to their machine on first run, and you can kill it between one execution and the next.
rayenallowedmikaallowed—key revokedEvery SolAuth build ships with layered protection, on by default — nothing to configure and nothing to bolt on. Key features include:
and many more advanced security measures.
rayenallowedmikaallowed—hwid mismatch—key revokedProjects, keys, buyers and executions — managed from one dashboard.
SOLA-4KP2A ready-to-use bot for your own server. Buyers redeem keys and reset their own device, so only the real problems reach you.
W9ALCrShLknPLEfSlockedRb1nm8OjeGkkXheJlockedx2Bv9Lp04sRk8EzqrevokedEQsPFzhlhvu7QRc7unusedGenerate keys in bulk and hand them out however you sell. Sixteen characters, one buyer each, revocable the moment you need it.
Disable a script, revoke a key or kill a build whenever you want. It takes effect on the very next execution.
-- your loader getgenv().sol_key = "W9AL…" loadstring(game:HttpGet(url))()
Upload the script, hand out the loadstring. Verification, device matching and delivery all happen server-side.
Choose the tier that fits your hub, and scale up as your catalogue grows.
If you're just starting to sell scripts, this is the one. Move up whenever you outgrow it.
The plan most hubs settle on. Room for a real catalogue and the buyers that come with it.
For large hubs running many scripts at once, with support that answers first.
A licensing and delivery service for Lua scripts. Instead of sending buyers a raw file, you give them a key; the script is verified at runtime, and you can revoke that key whenever you want.
Two lines, copied straight from your dashboard. The first sets their key, the second calls your loader endpoint:
getgenv().sol_key = "W9ALCrShLknPLEfS"
loadstring(game:HttpGet("https://api.solauth.cc/loader/8fq2xk"))()The key is the 16-character one you issued them; the ID is one of the loader URLs for that script. On a script set to free access the first line is dropped and only the loadstring remains.
It binds to the first machine that runs it, so a shared key simply stops working — and the attempt shows up in your logs. Real PC changes are handled with a HWID reset, which buyers can run themselves from Discord.
Your source never sits at a public URL. Raw uploads are refused until they've been virtualized, and a build is only released to a run that passed every check — anything unverified gets garbage back.
No — it loads fast. The check happens once at load, typically in under half a second, and nothing polls or runs per frame while your users play.
SolAuth is invite-only while we scale. With a code, registration takes a minute — link Discord, verify your email, and your API key is issued on the spot.
Support, key problems and HWID resets are all handled in our Discord server. Ask there and you'll get a real answer.
Join our Discord