BPB Panel: A Cloudflare Worker GUI for VLESS, Trojan, and Warp Subscriptions

What BPB Panel Actually Solves

BPB Panel addresses a specific pain: generating and managing proxy subscriptions for VLESS, Trojan, and Warp when you are behind an ISP that blocks domains or Warp services. Instead of hand-editing client configs, you deploy a GUI panel to Cloudflare Workers or Pages. The panel produces subscription links that clients like v2rayNG, Sing-box, Clash Meta, and AmneziaVPN can consume. The target user is someone with basic Cloudflare knowledge who wants a private, free proxy setup without paying for a VPS. The README stresses free and private, meaning no server cost beyond Cloudflare's free tier, and the panel is password-protected for authentication. This is not a general-purpose VPN; it is a configuration factory tailored to Cloudflare's edge network.

How the Panel Generates Subscriptions

The core mechanism is a Worker script that acts as an endpoint. The panel exposes a web interface where you set parameters like protocols, ports, clean IPs, DNS servers, and Warp endpoints. Based on those settings, it generates subscription URLs for different client cores. The README lists VLESS, Trojan, and Wireguard (Warp) as supported protocols. It also includes a private DoH server, which is a DNS-over-HTTPS endpoint that you can customize to point to an underlying DNS server. The routing rules are comprehensive: bypassing Iran, China, and Russia, blocking QUIC, porn, ads, malware, phishing, and bypassing sanctions. There is also a chain proxy feature that lets you add an upstream proxy (VLESS, Trojan, Shadowsocks, socks, or http) to fix your IP. This is a data flow where the Worker receives a request, applies routing and proxy logic, and returns a config. The documentation does not detail the internal code flow, but the feature list implies a modular design with separate handlers for each protocol and rule set.

Deployment via BPB Wizard and Configuration Keys

Getting started is via the BPB Wizard, a separate project that automates deployment. The README links to installation methods, configuration, usage, and FAQ pages on the project site. It mentions Workers and Pages deployments in a few seconds using the wizard. For configuration, the panel supports setting clean IPs-domains, proxy IPs, DNS servers, choosing ports and protocols, Warp endpoints, and more. There is no explicit command-line install in the README; it is a web-based wizard. After deployment, you access the panel, set a password, and configure your preferences. The subscription links are then generated for clients. The README does not list specific config keys, but it implies a JSON-like settings structure. Users who want manual control would need to inspect the repository's source or documentation. The wizard is the primary path, which lowers the barrier but also means you depend on that tool's maintenance.

Client Compatibility and Feature Gaps

The supported clients table is a key decision factor. It lists v2rayNG, MahsaNG, v2rayN, Streisand, Sing-box, husi, Clash Meta, Clash Verge Rev, FLClash, Wireguard, AmneziaVPN, and WG Tunnel. Fragment support is available on the first six clients but not on Clash Meta, Clash Verge Rev, FLClash, Wireguard, AmneziaVPN, or WG Tunnel. Warp Pro support is available on v2rayNG, MahsaNG, v2rayN, Streisand, Clash Meta, Clash Verge Rev, FLClash, AmneziaVPN, and WG Tunnel, but not on Sing-box, husi, or Wireguard. This is a real limitation: if you want both Fragment and Warp Pro, you cannot use Sing-box or husi. The table also shows minimum versions, so older clients may not work. The README does not explain why these gaps exist, but it likely relates to protocol extensions that each core implements differently. Users must match their client version to the feature set, which adds friction.

Known Limitations: UDP and Daily Request Quota

The README is explicit about two limitations. First, UDP transport for VLESS and Trojan on Workers does not handle properly, so it is disabled by default. This affects features like Telegram video calls, and UDP DNS is unsupported. DoH is enabled by default to compensate. Second, each Worker supports 100K requests per day for VLESS and Trojan, which the README says is suitable for 2-3 users. Warp configs are limitless, meaning they do not count against that quota. This is a hard constraint: if you plan to share with more than a few people, you will hit the cap. The UDP issue is inherent to Cloudflare Workers, not a bug in the panel. Users who need reliable UDP should look elsewhere. The quota is a Cloudflare free-tier limit, but the panel does not offer a way to bypass it; you would need multiple Workers or a paid plan.

Maintenance, License, and Upgrade Cost

The project is under GPL-3.0, which means any derivative work must also be open source under the same license. This is a consideration for commercial use. The repository is actively maintained, with the latest release v5.1.1 pushed on 2026-07-19. The release history shows frequent updates: v5.1.0 and v5.0.0 in the same month. This suggests a high maintenance cadence, which is good for bug fixes but also means you need to track releases to stay current. The README does not describe a migration or upgrade path, but given the wizard-based deployment, re-running the wizard may update the Worker. However, that could overwrite custom settings. There is no mention of backup or export features. Users should plan to reapply configuration after updates, or test in a staging Worker first. The dependency on the BPB Wizard for deployment is another maintenance point; if that tool breaks, you may need to manually edit the Worker script.

Alternatives and When BPB Panel Is the Wrong Tool

A real alternative is the original Cloudflare Workers VLESS proxy script by yonggekkk, which BPB Panel credits as a base. That script is a simple endpoint without a GUI, routing rules, or DoH. You configure it by editing environment variables in the Worker dashboard. The difference is approach: yonggekkk's script is minimal and requires manual setup for each client, while BPB Panel adds a full panel and subscription generation. For users who want a single config for one device, the script is lighter and has fewer moving parts. BPB Panel is the wrong tool if you need UDP support, if you are on a free Worker with heavy usage, or if you prefer a client-agnostic setup without the panel's opinionated routing. Another alternative is to run a VPS with Xray directly, but that costs money and requires server administration. BPB Panel's value is the zero-cost Cloudflare edge, but that comes with the quota and UDP trade-offs.

Editorial conclusion

Adopt BPB Panel if you need a free, self-hosted subscription manager on Cloudflare Workers or Pages, especially for VLESS, Trojan, and Warp with a private DoH and routing controls. Avoid it if you require reliable UDP transport or expect to serve more than a few users per worker, given the 100K daily request cap. Before deploying, verify your Cloudflare account's Worker limits and test that your chosen client supports the features you need, since Fragment and Warp Pro support vary by client. Confirm that the GPL-3.0 license fits your use case, and be ready to update the panel regularly as Cloudflare's platform changes.

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes