Comparison

A PolSec alternative for Lua auth and script whitelisting

Product informationSources dated October 29, 2026 · Vampauth Team · Vampauth compatibility reviewed against the November 4, 2026 production release; competitor details retain their source dates.

Start publishing for free. Keep control of your keys.

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

Get 20 script slots, 10,000 keys per project and 5 new protected builds every week on Free. Choose Full VM payload protection or Off/passthrough, issue keys with or without HWID binding, and manage your workspace through browser-authorized MCP.

Start free on Vampauth See pricing

Compare PolSec and Vampauth Lua key-system access

Official pricing, documentation and published interface source checked October 29, 2026. Weekly and monthly allowances retain their published periods.

Feature	Vampauth	PolSec
Pricing	Free · Developer $5/month	Premium $5/month
Free protected publishing	5 new builds/week	Premium required by the standard Free publishing interface¹
Stored keys	10,000/project on Free	Unlimited on all plans
HWID-free keys	Included on Free	Enterprise $80/month
Workspace management	Browser-authorized native MCP	API-key REST

¹ This describes the ordinary Free account role. The public client separately references Basic/Ad System roles with a 20/month default; current eligibility for those roles remains unresolved. This is not a claim that all free or specially granted accounts are excluded.

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

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.

Publish your first protected Lua script on Free

Start with 20 script slots per account, 10,000 keys per project and 5 new protected payload builds per week. Developer is $5/month when you need higher allowances.

PolSec Premium advertises 60 obfuscations per month at $5/month. Its standard Free publishing interface prompts an upgrade; the separate Basic/Ad System roles are qualified beneath the table. Weekly and monthly build allowances keep their original periods.

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.

Full VM payload protection or Off/passthrough on every Vampauth plan
Compatible unchanged builds and source-free URL rotations do not spend a new protected-build unit
Keep your original source locally for replacements

Choose whether a license binds to a device

Vampauth Free supports device-bound licenses and FFA keys without HWID binding. With HWID checks enabled, a non-FFA key binds to one device on successful use; an authorized reset preserves its expiry and usage history.

PolSec documents per-key HWID-free access as an Enterprise control. An HWID-free key still requires a license; it is distinct from a keyless project or disabling the loader's key check.

Issue HWID-free keys on Free
Keep one-device binding for licenses that need it
Manage expiry, bans and device resets from your workspace

Manage your key system through browser-authorized MCP

Connect a compatible AI client through browser sign-in and consent. Scoped native MCP actions manage projects, keys, loaders and provider configuration without copying an account API token into the client setup.

PolSec's documented management setup uses an account API key as a bearer token for REST requests. This compares documented setup, not the absence of other PolSec interfaces.

Read key state without activating unused keys
Authorize only the project access and actions your client needs
Keep current project permissions and resource allowances in effect

Connect your own checkpoints when you are ready

Start with a manual test key, then connect your own Linkvertise, LootLabs, Work.ink and LinkUnlocker accounts. Vampauth takes 0% of creator checkpoint earnings. Its small key-flow banners are a separate revenue stream and do not reduce provider payouts.

Use the dashboard's loader snippet and test valid access, expiry, bans and device rules before sharing it. Keep your original source; this comparison does not establish automatic key import or source portability.

Four implemented checkpoint providers
0% taken from creator checkpoint earnings
Test a single project before replacing your existing integration

This selected comparison covers entry pricing, ordinary-Free publishing, key capacity, HWID-free keys and management setup. The Free restriction is a published-interface finding, not an authenticated backend or security test.

PolSec vs Vampauth: Lua auth and key-system questions

Is Vampauth a free PolSec alternative?

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. 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.

Can ordinary PolSec Free accounts publish protected scripts?

As checked October 29, 2026, PolSec's published interface blocks protected script creation and source rebuilds for the ordinary Free role and prompts an upgrade to Premium. Its client separately references Basic/Ad System roles with a 20/month default, but current eligibility for those roles remains unresolved. The interface finding is not a claim that every free or specially granted account must pay.

What do PolSec's paid plans cost?

PolSec advertises Premium at $5/month with 60 obfuscations/month, Commercial at $20/month with 150/month, and Enterprise at $80/month with unlimited obfuscations subject to fair use, checked October 29, 2026. These are advertised monthly offers, not tested checkout totals. Vampauth's Free build allowance is weekly, not a converted monthly quota.

Can I issue keys without HWID binding on Vampauth Free?

Yes. An FFA key bypasses hardware binding and is available on Free. PolSec's documentation reserves per-key HWID-free access for Enterprise, advertised at $80/month. HWID-free keys and project keyless access are different controls.

What happens to my original source after publishing?

Vampauth keeps final artifacts rather than a separate original-source backup; Off/passthrough output contains the submitted code. PolSec's privacy policy says source submitted for obfuscation is processed transiently and discarded after processing. Keep your own source copy. These descriptions do not establish audited deletion or automatic source portability.

How do I manage Vampauth from an AI client?

Use a compatible remote MCP client with browser sign-in and consent. Scoped actions cover projects, keys, loaders and providers; read-only management actions do not activate keys. PolSec documents API-key REST management. That documentation is not evidence that PolSec lacks MCP.

What changed in Vampauth v2 for developers switching key systems?

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. Start with the current dashboard loader workflow, keep your original source and test key and device policies before switching.

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.

Create your free account