BPB Wizard: installing a Cloudflare Workers panel without the manual steps

A wizard for one specific panel, on one specific platform

BPB Wizard exists to remove the manual part of putting the BPB Panel on Cloudflare. The stated aim is to facilitate the installation of BPB Panel efficiently and to prevent user mistakes during deployments, which is a narrow and honest description of what a deployment wizard is for.

The panel it installs is a Cloudflare Workers and Pages project, and the wizard itself is written in two languages for two reasons. The web edition is TypeScript, built as a Cloudflare Worker with the workers type definitions and the cloudflare client library, and it is deployed directly from this repository. The CLI edition is Go, using the cloudflare-go client, and it is built with a GitHub action.

That split is the interesting design decision in the project. The same deployment logic is offered as something that runs in your browser against someone else's server, and as something that runs on your machine. Everything else about the tool follows from which one you pick.

The web edition trades a Private Link for a hosted step

The web edition is reached at a single address, wizard.bpb-panel.workers.dev, and its job is to turn a manual deployment into a one-click operation.

Here is the mechanism. After a deployment finishes, the web edition generates a Private Link, and that link enables one-click installation per Cloudflare account. In other words, the setup work happens once in the browser, and the resulting link lets you install the panel on a Cloudflare account in a few seconds without repeating the steps. The web edition can be used for a single account, and it keeps no storage of its own, which is the privacy claim the project makes about that path.

The cost is that the deployment runs on infrastructure you do not control. Your Cloudflare credentials pass through a hosted worker, and the artefact you keep, the Private Link, is tied to the account that generated it. That is a reasonable trade for a one-off setup, and a poor one for a team that would rather not hand a third party a token with permission to create workers and pages on their account.

The CLI edition keeps the logins on your operating system

The CLI edition is the opposite arrangement, and the project states the difference plainly. The CLI stores your logins on your operating system, and it supports multiple accounts' installations, so several Cloudflare accounts can be managed from one machine. The multi login feature is listed first among the project's features, and the detail that makes it usable is that token entry is only needed the first time on each device.

The deployment methods are the same in both editions. Both Pages and Workers deployments are supported, so the choice is about where the panel runs rather than about how the wizard runs.

The cross-platform claim is specific too. The CLI works on Windows, Android through Termux, macOS and Linux, and the wizard is built as a static binary with CGO disabled, which is what makes a single artefact portable across those systems.

If your concern is where your Cloudflare credentials live, the CLI is the edition to choose. If your concern is doing the setup once and handing it to other accounts, the Private Link from the web edition is the more convenient path, though it also means a hosted component in the middle.

The CLI can only be started through its install scripts

Installation is a single command on Unix-like systems, which covers Termux on Android, Linux and macOS.

bash <(curl -fsSL https://raw.githubusercontent.com/bia-pain-bache/BPB-Wizard/main/install.sh)

On Windows the same job is done in PowerShell.

irm https://raw.githubusercontent.com/bia-pain-bache/BPB-Wizard/main/install.ps1 | iex

Two details sit around those commands. On Android, the project asks you to install Termux from its GitHub source rather than from Google Play, so the Termux release used is the one the wizard expects. And there is a restriction worth reading twice: Wizard CLI edition can only be used by these scripts, and standalone execution is not permitted.

That last rule is the one that shapes how you can use the tool. You cannot download a binary and run it on your own, which rules out air-gapped installs, running it from a pinned copy, or embedding it in your own automation. It also means the tool's behaviour is tied to whatever the install script fetches at the moment you run it, so the main branch URL in the command is a moving target by design.

Building the Go CLI yourself

The CLI is a normal Go program with a Makefile, so building it locally is straightforward. The Makefile takes the version from a VERSION make variable, stamps it into the binary through a linker flag on main.VERSION, and builds with CGO disabled and the trimpath option, which keeps local paths out of the artefact.

The output layout is worth knowing if you script around it. The build writes a directory under bin named after the application, the operating system and the architecture, containing the wizard executable, and it copies the LICENSE file into that directory alongside it. The distribution directory then gets a zip for Windows and macOS and a tar.gz for everything else, so the archives match how each platform expects to receive a binary.

The module itself is small in dependency terms. It requires Go 1.26.5, with the Cloudflare Go client and the Google UUID package as direct dependencies and a handful of indirect tidwall JSON helpers behind them. The web edition is a separate Node project with TypeScript, the Cloudflare Workers type definitions and the cloudflare package, and the wrangler.toml at the root is what describes the worker deployment.

GPL-3.0 and a release rhythm that comes in bursts

The licence is GPL-3.0, and for this project the practical implication is about the artefacts rather than the source. The repository ships installer scripts that download and run a binary, and it produces release archives containing the executable together with the LICENSE file. If you redistribute a build of the wizard, the copyleft terms of GPL-3.0 apply to that redistribution, and the Makefile's habit of shipping the licence file next to the binary is a reminder of that. Whether any particular use of the tool triggers an obligation is a question for your own counsel.

The release history is short and recent. Version 3.0.0 was published on 2026-07-19, followed by 3.0.1 on 2026-07-20 and 3.0.2 on 2026-07-23, and the last push to the repository was on 2026-07-23. The project is not archived, so it is maintained, but the visible activity is concentrated rather than spread evenly across the year.

That matters slightly because of the install commands. Since both scripts point at the main branch of the repository, the version you get is the current one, and a burst of releases is what determines what that is. Reading RELEASE.md before an upgrade is the sensible move.

What the wizard does not do for you

The scope is narrow, and the boundaries are worth stating before you spend an afternoon on it.

The wizard handles installation of the panel. It does not describe itself as a monitoring or management console for a running panel, even though the project description mentions deployment and management, and the README lists deployment methods rather than runtime controls. If you expected a dashboard for a live panel, this is the wrong tool.

The web edition also has a narrow best case. The Private Link it produces is tied to a Cloudflare account, and the value of it drops once the panel is installed, which makes it a setup accelerator rather than a permanent link into your account.

The CLI edition's restriction is the sharper limit. It cannot be run standalone, so it cannot be pinned, air-gapped or scripted into a pipeline that expects a fixed binary. For a one-person setup on a laptop that is a small price. For an infrastructure team that wants reproducible provisioning, it is a real one, and the alternative is deploying the BPB Panel yourself, by whatever means, without the wizard.

And there is a prerequisite in both cases that no wizard can remove. You need a Cloudflare account, and the credentials you supply are what the tool acts with.

Editorial conclusion

BPB Wizard fits someone setting up the BPB Panel on a Cloudflare account who wants the deployment steps handled rather than typed, whether that is a single account through the browser wizard or several accounts through the CLI with tokens that never leave the device. It does not fit an air-gapped setup, a team that wants to audit the deployment by hand, or anyone who needs to run the tool from an offline copy, since the CLI edition is documented as usable only through its install scripts. Verify three things first: that your Termux install came from the GitHub release rather than Google Play, because the project asks for that explicitly, that you understand which Cloudflare account the browser wizard will create the Private Link under, and that the deployment method you pick, Pages or Workers, is the one your account and your panel configuration expect.

Frequently asked questions

Official sources

1. bia-pain-bache/BPB-Wizard on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases