Comparison
Vampauth vs Keybrew for Lua auth and script whitelisting
Product informationSources dated September 2026 · Vampauth Team · Vampauth compatibility reviewed against the November 4, 2026 production release; competitor details retain their source dates.
Comparing Keybrew with Vampauth? Start with the licensing behavior, source requirements and operations your project needs. Earlier notes identified Keybrew through community distribution; they do not establish its current onboarding, pricing, documentation or feature limits.
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. Vampauth publishes its loader, management and MCP workflow for inspection. Keybrew's current offer remains unverified here; missing retained documentation is not evidence that a capability is absent.
Documented Lua key-system features and evidence gaps
Keybrew identity/positioning uses retained September 2026 community notes, without a newly verified official plan or documentation source. No current no-website or no-feature claim is made. Vampauth v2/v2.0.1 facts refreshed October 27 from release notes, current code and plan definitions.
| Feature | Vampauth | Keybrew |
|---|---|---|
| Onboarding | Web registration and Free project creation | Current signup/community requirements not verified |
| Plans and resource limits | 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. | Current prices and stored-key/project limits not verified |
| Public integration workflow | Current loader, signed key-check, management API and MCP setup guides | Current official documentation destination not established by retained notes |
| HWID binding | 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. | Current binding and reset policy not verified |
| Publishing and hosting | Modular loaders; 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 publishing/hosting contract not verified |
| Protected-build allowance | Default protected-payload allowance: 5 new builds/week on Free, 10 on Developer, 15 on Pro. Reset Monday 00:00 UTC. | Current build 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 established in retained sources |
| Teams and Key Groups | Project permissions and group-based payload routing | Current collaboration and payload routing not verified |
| Checkpoint earnings | Own-account provider links; no Vampauth share of network earnings | Current providers and payout terms not verified |
| 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 dashboard/API metric coverage not verified |
| Discord and webhooks | Project panels, key management and up to five configured webhooks/project | Current bot and webhook capabilities not verified |
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 a documented workflow, not assumptions about a community
A community-distributed service may provide useful onboarding and support. A website, a Discord presence or the absence of a source in our retained notes does not prove how reliably it operates or which features its customers can use.
For Keybrew, obtain the current provider URL, contract and plan details from the operator before deciding. On Vampauth, use the public docs and setup guide to inspect how keys, loaders and management actions fit together. A configured client still needs an actual successful tool call to verify connection.
- Check exact expiry and device-reset semantics
- Compare actual plan allowances and required credentials
- Keep credentials private during setup
Vampauth v2 adds more than a different key limit
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.
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.
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.
- Modular loaders replace the old Scripts-tab integration
- Scoped team access and Key Groups for separate audiences
- Pro adds readable custom flow URLs
- Delivery and presence counters have explicit limits
Test a small project before changing the distributed loader
Keep your original source, create a Vampauth project and issue a manual test key. Choose the required loader components and payload profile, then verify successful and denied access before adding optional checkpoints.
Inspect any Keybrew export and the destination's accepted data before assuming key values, HWIDs, expiry or history can transfer. This page establishes neither automatic import nor minute-long migration. Staying with a service that fits your existing workflow can be the right choice.
- Test expiry, bans, device mismatch and group routing
- Re-enter provider settings privately
- Distribute the replacement endpoint only after verification
A community service may suit developers with an established relationship and a working integration. This page does not infer Keybrew's current quality, limitations or security from the availability of public sources.
Keybrew vs Vampauth: Lua auth and key-system questions
Is Vampauth a free Keybrew alternative?
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. Whether it fits depends on your actual loader, provider and migration requirements. Keybrew's current allowances were not verified here.
What does Keybrew currently cost?
Current prices and entitlements were not established by the retained community notes. Ask the provider for its actual offer. Developer is $5/month and Pro is $15/month, available via Discord.
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 tooling exposes scoped management actions, with separate read/write permissions and normal publishing allowances.
Does this comparison prove Keybrew has no docs or MCP?
No. It records the limits of the retained sources, not a current product-wide absence. A present documentation link or MCP setup statement needs its own source check.
Can I import my existing Keybrew keys?
Automatic import and preserved history were not established in this review. Inspect an actual export and supported destination contracts, then test keys, expiry and hardware behavior in a separate project 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.
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