Create a Server on Cloudflare
Install an Zugoid Server in your own Cloudflare account from the browser, claim it as Owner and open it.
The official installer at zugoid.com/create creates a new Server in your Cloudflare account. It runs in your browser, uses your own Cloudflare authorization and installs only a published, checksum-verified release. It takes a few minutes.
Before you start
- A Cloudflare account with a verified email address. If the email is not verified, the installer asks you to verify it and reconnect.
- Optional: R2 enabled on the account. With R2 the Server gets a private files bucket and a separate backups bucket. Without it, the Server uses basic file storage and backups download to your device. See What the installer creates.
Tip
For safety, give each Server its own Cloudflare account. A free account is enough. This is a recommendation, not a requirement.
1. Connect Cloudflare
- Open zugoid.com/create and choose the On Cloudflare tab.
- Select Connect Cloudflare.
- Sign in to Cloudflare and approve the requested permissions. Cloudflare access explains each one.
- Back on the installer, choose the account under Cloudflare account.
The card shows how long the Cloudflare access and the installer session last. The installer session lasts one hour. Your Servers keep running when this connection ends.
2. Configure the Server
- Select Create a Server.
- Fill in the form:
- Server name: up to 80 characters. You can rename the Server later in Settings; this never changes Cloudflare resources.
- Release version: the published release to install.
- Leave Keep Cloudflare access on this Server checked if you want the Server to update itself from its own Settings. Uncheck it if you prefer the Server to keep no Cloudflare credential. See Updates.
- Select Deploy Server.
3. Wait for the deployment
The form and the deployment fill the whole screen until the Server is deployed. The installer shows its phases: Configure your Server, Start deployment, Wait for Cloudflare verification and Ready, with details for each step.
Before it creates anything, the installer downloads the selected release and verifies its checksums. A missing or mismatched checksum stops the installation without creating a Server.
Every step can be resumed. If something fails, fix the cause (for example reconnect Cloudflare) and select Resume deployment. A retry reuses the same Server ID and resources. Pause and start another keeps the unfinished installation in your installer session so you can resume it later with Resume setup.
A new Server starts on your account's workers.dev hostname. Its status may show Waiting for HTTPS… for a short time while Cloudflare prepares the address.
4. Claim the Server as Owner
When the deployment ends, the installer shows a Finish setup on your Server button. If you select Done instead, the Server's row under Your Servers shows Setup required and the same button.
- Select Finish setup on your Server. It opens the Server's
/setuppage in a new tab, on the Server's own address, so your browser can save the password for that site. - Choose a Username and a Password. Your name and Email are optional, and you can add an email later.
- Select Sign in as owner.
The setup link carries a private, single-use claim. Nothing else can claim the Server. After you claim it, the claim is deleted.
Once you have claimed the Server, its row shows Open. To reach it from another Server you use, see Connect to a Server.
If you lost the setup link
If you closed the tab or the installer session expired before you claimed the Server:
- Open zugoid.com/create and select Reconnect Cloudflare.
- Select Refresh Servers.
- On the Server's row, select Finish setup on your Server or Recover setup link.
Recovery works only while the Server has no Owner and no login Accounts. It never resets an existing Owner.