Free plan guide
Free Lua key system for Roblox script whitelisting
Product informationSources dated October 2026 · Vampauth Team · Vampauth compatibility reviewed against the November 4, 2026 production release; competitor details retain their source dates.
Vampauth has a separate Free plan, plus paid Developer and Pro plans. Use Free for Roblox script whitelisting, Lua authentication and license management without a trial timer. It includes 10 projects, 10,000 licenses per project, 20 script slots and a default allowance of 5 protected payload builds a week. Your checkpoint earnings stay in your own ad-network accounts.
Protection choices on every plan
Double-layer Full VM protection for new protected payloads and required generated stubs. Off/passthrough supports plain or externally protected code. Runtime checks are configurable. Default protected-payload allowance: 5 new builds/week on Free, 10 on Developer, 15 on Pro. Reset Monday 00:00 UTC.
Native MCP management
Connect a compatible AI client through Model Context Protocol (MCP) to manage projects, keys, loaders and providers. Connection scopes, current project permissions and resource allowances still apply; read-only actions do not activate keys.
0% revenue cut — always
Checkpoint links point to your accounts. Vampauth never takes a share. Free at core, with optional higher-limit plans.
Free Lua auth and script-whitelisting allowances
| Resource | Free allowance |
|---|---|
| Monthly price | $0 |
| Projects per account | 10 |
| Licenses per project | 10,000 |
| Checkpoints per project | 10 |
| Script slots per account | 20 |
| Default protected-payload builds | 5 per week |
| Maximum delivered payload | 8 MiB; input limits also apply |
Free Lua auth, licensing and checkpoint rewards
A free Lua auth system still needs a clear access policy. Issue test keys manually, choose expiry and optional device restrictions, then publish a loader with key checking enabled. Add checkpoint rewards when users should earn access. The Roblox key-system guide explains script whitelisting and authentication in more detail.
- With HWID checks enabled, a non-FFA license key binds to one device on successful use. An authorized reset clears its device binding while preserving key expiry and usage history.
- Manual key issuance, expiry, bans and authorized resets
- Keyless access when you deliberately do not require a key
- 0% revenue cut — your links, your money
- Linkvertise / LootLabs / Work.ink checkpoint links
- Full VM payload protection or Off/passthrough; runtime checks are configurable
- Hosted loaders and a standalone key-check API
- Discord bot + webhooks
- Project and loader analytics
How the weekly obfuscation allowance works
Default protected-payload allowance: 5 new builds/week on Free, 10 on Developer, 15 on Pro. Reset Monday 00:00 UTC. A new protected payload build uses one weekly allowance unit. Compatible unchanged builds, source-free URL rotations, metadata-only edits, passthrough payloads, downloads and executions use no protected-payload allowance. Failed publishing preserves the active build.
Check the dashboard for your effective account allowance. Read the hosted Lua/Luau publishing guide before choosing an obfuscation profile, and the HWID guide for device-bound licenses.
When to consider Developer or Pro
Free includes 10 projects, 10,000 licenses per project, 20 script slots and a default allowance of 5 new protected payload builds per week. Developer is $5/month and Pro is $15/month, available via Discord. Pro also includes custom flow URLs.Compare the full pricing table before choosing a plan; Free is a plan, not a claim that every optional feature is free.
Head-to-head with the alternatives
- Vampauth vs Luarmor — licensing and publishing workflows
- Vampauth vs Panda Auth — token model and resource allowances
- Vampauth vs FlowAuth — plan scope and checkpoint features
- Vampauth vs JNKie — hosting and resource allowances
- Vampauth vs PolSec — Free publishing and HWID-free keys
- Vampauth vs Platoboost — monetization and licensing approaches
Create your first project on Free
Register, create a project and issue a test key. You can assess the licensing workflow before connecting checkpoint providers or choosing a paid plan.
Free key system — FAQ
Is there a key system that is actually free?
Yes. Free includes 10 projects, 10,000 licenses per project, 20 script slots and a default allowance of 5 new protected payload builds per week. Developer is $5/month and Pro is $15/month, available via Discord. Pro also includes custom flow URLs. Free includes licensing, HWID binding and checkpoint flows without a trial timer.
What's the catch with a free key system?
Creators use links from their own Linkvertise, LootLabs or Work.ink accounts and receive checkpoint earnings directly from those providers, subject to each provider's terms. Vampauth takes 0% of creators' checkpoint earnings. Vampauth earns separate advertising revenue from small banner ads displayed on its key-flow pages (flow URLs); these ads do not reduce creators' checkpoint payouts. The Free plan has no subscription charge.
How does Vampauth's free tier compare to competitors' free plans?
Compare project count, license capacity, script slots, protected-payload allowance and plan-specific features separately. Weekly and monthly allowances are not interchangeable. Our comparisons identify their source dates; confirm current terms with each provider rather than assuming every free tier has the same restrictions.
Can I upgrade later if my project grows?
Free includes 10 projects, 10,000 licenses per project, 20 script slots and a default allowance of 5 new protected payload builds per week. Developer is $5/month and Pro is $15/month, available via Discord. Pro also includes custom flow URLs. Flow-page ads apply to every plan. Your dashboard shows the effective allowance if your account has an override.
Can I protect a project that runs without keys?
Yes. Keyless delivery is supported. New protected builds use double-layer Full VM protection for the payload and generated loader stub when runtime components require one. An unobfuscated option (Off/passthrough) preserves submitted code, including code protected by your own obfuscator; a newly published stub still uses Full VM. New Light publishing is unavailable; existing historical payloads may remain deliverable or be reused by eligible source-free URL rotations. Disabling all runtime components serves the final payload directly without a stub or access checks. The same current protection choices are available on every plan. Default protected-payload allowance: 5 new builds/week on Free, 10 on Developer, 15 on Pro. Reset Monday 00:00 UTC. A new protected payload build uses one weekly allowance unit. Compatible unchanged builds, source-free URL rotations, metadata-only edits, passthrough payloads, downloads and executions use no protected-payload allowance. Failed publishing preserves the active build.