Comparison
Vampauth vs Platoboost for Lua key systems
Product informationSources dated September 2026 · Vampauth Team · Vampauth compatibility reviewed against the November 4, 2026 production release; competitor details retain their source dates.
If your main task is a monetized access link, compare the link/service workflow. If you also need to publish Luau payloads, route key groups and manage a team, inspect the current loader workflow. Old service counts and roadmap labels are not a current feature-parity test.
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.
The short version
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. Platoboost figures below are a retained September 2026 snapshot, not newly checked prices. A Platoboost service, a Vampauth project and a stored loader are different resource units; do not infer a capacity multiplier from their names.
Compare script auth, licensing and checkpoint monetization
Platoboost positioning, September prices and roadmap labels are retained from the earlier platoboost.app/pricing snapshot; they were not rechecked in this refresh. Vampauth v2/v2.0.1 details refreshed October 27, 2026 against release notes, current code and plan definitions.
| Feature | Vampauth | Platoboost |
|---|---|---|
| Plans | Free at core. Developer is $5/month and Pro is $15/month, available via Discord.Pro adds custom flow URLs; paid plans are not only numerical increases. | September snapshot: Hobby Free, Startup $49/month, Enterprise $199/month; current offer not verified |
| Projects / services | 10 projects on standard FreeProject/service/loader counts do not measure the same thing. | Retained snapshot described one Free service; current limits not checked |
| Key capacity | 10,000 licenses per project on Free | Current stored-key capacity not verified |
| Device policy | 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. | Auth advertised in retained sources; current binding/reset details not tested |
| Payload publishing | Modular loaders with Full VM payload protection or Off/passthroughA 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. | Current hosted-payload capabilities not established by retained pricing notes |
| Publishing allowance | Default protected-payload allowance: 5 new builds/week on Free, 10 on Developer, 15 on Pro. Reset Monday 00:00 UTC. | Current publishing allowance not verified |
| 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. | Native MCP setup not verified in the retained sources |
| Teams and Key Groups | Scoped project collaboration and group-based payload routing | Current team/group workflow not verified |
| Checkpoint earnings | Own-account Linkvertise, LootLabs or Work.ink links; no revenue share | Monetization advertised; verify current provider and payout terms |
| Flow-page ads / checkout | Flow pages remain ad-supported on every plan; no built-in payment processor claimedHistorical roadmap labels are not proof of current absence. | Some features were labeled Coming soon in September; present availability not checked |
| Analytics | Inspect checkpoint completions and failures, lifetime key usage and HWID resets, loader delivery/denial counters and active-session observations through the API and MCP. Lifetime and deployment-baseline counters are not date-filtered delivery history; delivery is not proof of completed execution. | Current metrics and reporting windows not verified |
| Discord and webhooks | Project panels, key operations and up to five configured webhooks/project | Current features and plan gates not checked |
Why choose Vampauth for Lua script whitelisting?
V2 changes the workflow around each key: modular loaders, scoped team collaboration and Key Groups, followed by v2.0.1 improvements to analytics, Discord panels and persistent presence. Current native MCP tooling brings authorized management into your AI client.
Modular loaders replace the old Scripts workflow
Choose the runtime checks and payload profile your project needs. Key checks, one-device binding and renewable session leases are configurable; disabling every runtime component serves the final payload directly without an access-checking stub.
Manage your workspace from an AI client
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.
Project teams and Key Groups
Delegate project work with granular permissions. Organize keys into groups and route groups to different payloads, while keeping management access scoped to the right projects.
Named analytics metrics, with clear boundaries
Inspect checkpoint completions and failures, lifetime key usage and HWID resets, loader delivery/denial counters and active-session observations through the API and MCP. Lifetime and deployment-baseline counters are not date-filtered delivery history; delivery is not proof of completed execution. V2.0.1 adds persistent presence and heartbeat state; presence is still an observation, not proof a game script finished running.
Publishing choices and explicit build accounting
Use double-layer Full VM protection for new protected payloads and required generated stubs, or Off/passthrough for plain or externally protected code. Configure key, HWID and session checks for your workflow. 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.
Follow the MCP setup guide, read the v2 and v2.0.1 release notes, and compare current plan allowances. Start with a project and a manual test key before changing your existing integration.
Compare the access-link task with the payload task
The retained Platoboost notes describe services and link/auth monetization. That can be the relevant starting point for a developer whose existing hosting and code protection already work. Verify the current API and provider requirements directly before choosing.
Vampauth v2 lets you configure how a loader checks access and selects a payload. Key Groups can route different licensed audiences to different payloads; a project is not simply another monetized link. Test this workflow with your real distribution needs rather than comparing only service counts.
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.
- Separate project, license, loader-slot and protected-build allowances
- Test a manual key before configuring optional checkpoints
- Keep key checking enabled for licensed delivery
What changed in Vampauth v2 and v2.0.1
V2 replaces the old Scripts workflow with modular loaders, scoped project teams and Key Groups for payload routing. V2.0.1 improves Discord panels and flow/loader analytics, and persists presence and heartbeat state independently of server memory. Current production offers pinned Stable/Main 1.0.0 and Beta 1.0.1 loader releases. Existing loaders do not follow channel-head changes automatically. A historical loader without a saved pin, or a new loader with no release selection, uses Stable 1.0.0. Replacements and URL rotations preserve the saved pin unless an explicit supported update selects another release. These releases version Vampauth delivery behavior, not a backup of your source revisions. Payload profiles, enabled checks and current plan entitlements still determine the behavior you get.
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.
- Scoped project teams and Key Groups
- Configurable runtime components and payload profiles
- Persistent presence is not proof of completed execution
- Pro-only custom flow URLs
Validate the current offer before moving users
A feature labeled Coming soon in an old screenshot may have shipped since. This page does not turn September roadmap labels, domain observations or historical prices into current reliability claims. Ask for the exact service, plan and integration you intend to use.
For a move to Vampauth, retain original source, create a test project, re-enter provider credentials privately and publish a harmless payload. Verify expiry, bans, device mismatch, group routing and checkpoint returns before sharing a new loader URL. Automatic key/history import and migration time are not established here.
- Compare actual current provider and SDK requirements
- Keep the previous integration available until testing succeeds
- Do not treat obfuscation as a guarantee against code inspection
A service-oriented monetization platform can fit developers who already host and protect their code. This comparison does not establish Platoboost's current feature absences, startup performance, uptime or security quality.
Platoboost vs Vampauth: Lua auth and key-system questions
Is Vampauth a free Platoboost alternative?
It can fit Roblox licensing and hosted-payload tasks. 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 Platoboost's current service workflow and limits directly rather than treating unlike resource units as equivalent.
What does Platoboost cost today?
The retained September 2026 snapshot listed Hobby Free, Startup $49/month and Enterprise $199/month. This refresh did not retrieve a current checkout or plan table, so those are historical figures rather than today's quote.
Are the old Coming soon features still unavailable?
That was a label in the retained September source. Present availability was not verified, so this page does not claim the features are still missing or that the service is unreliable.
What changed in Vampauth v2?
V2 replaces the old Scripts workflow with modular loaders, scoped project teams and Key Groups for payload routing. V2.0.1 improves Discord panels and flow/loader analytics, and persists presence and heartbeat state independently of server memory. Current production offers pinned Stable/Main 1.0.0 and Beta 1.0.1 loader releases. Existing loaders do not follow channel-head changes automatically. A historical loader without a saved pin, or a new loader with no release selection, uses Stable 1.0.0. Replacements and URL rotations preserve the saved pin unless an explicit supported update selects another release. These releases version Vampauth delivery behavior, not a backup of your source revisions. Payload profiles, enabled checks and current plan entitlements still determine the behavior you get. Current native MCP adds authorized management from compatible AI clients; the public setup guide explains the connection and verification steps.
Can I keep my ad-network accounts?
Vampauth checkpoint links use your own supported ad-network accounts, and the network pays you directly. Provider configuration and callback requirements still need testing. No automatic transfer of credentials or existing key history is promised.
Create a Lua script whitelist with Vampauth
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. Checkpoint earnings pay directly into your ad-network accounts.
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.
Create your free account