What happens after you order a server: build steps explained

After you pay, your server is built automatically and reports its progress on the Billing page under your servers. You do not need to do anything while it runs, and the page updates itself roughly every fifteen seconds.

This guide covers what you choose at checkout, what each build step means, and what to do when a build takes longer than it should.

At checkout

Three things can appear in the subscribe dialog, depending on the plan and current capacity.

Region. If more than one region has stock for that plan, you pick one and each option shows how many are left. If only one region has stock, it is selected for you and no picker appears. If none do, the plan shows as sold out and there is nothing to pay.

Stock counts are per plan, not a shared pool. Capacity that fits one large plan is the same capacity that fits several smaller ones, so a plan can be available in a region while a larger plan in that same region is not.

Promo code. Enter it and choose Apply before paying. A valid code shows the discount and the amount actually due now. An invalid one says so and nothing is charged. If a code covers the first invoice in full, there is nothing to confirm and the subscription activates directly.

Payment. Card and US bank account are both accepted. Card details are entered on Stripe's own payment form, so the card number never reaches gummies.cloud.

The build

Once payment succeeds, the order appears as a card with a progress bar and the name of the current step. The steps run in this order:

clone -> allocate -> configure -> start -> agent-wait
      -> install -> install-deps -> mint -> token-drop
      -> enroll-wait -> done

Roughly, the first four prepare and start the virtual machine, agent-wait waits for the machine to come up and report in, the install steps put the panel software in place, and mint, token-drop, and enroll-wait enrol the finished machine into the panel so it appears in your account.

Most of a build is waiting on those two handshakes. A card sitting on agent-wait or enroll-wait for a short while is normal, not stuck.

Extra steps may appear that are not in this list. The build is allowed to grow, so treat the sequence as the shape of the process rather than a fixed checklist.

The states a server can be in

State	What it means
Building your server	The build is running, no action needed
Running	Finished, with a link to open it in the panel
Setup is taking longer than usual	The build stalled and is being retried
Upgrade pending	You changed plan, the machine has not been moved yet
Suspended	Running but not reachable, usually a billing or policy matter
Terminated	The server has been removed

When a build stalls

Setup is taking longer than usual does not mean the order failed or the money is gone. Builds that stop partway are retried, and the state exists so the delay is visible to you instead of only to us.

The card carries a Get help with this server link. It opens a ticket with that server already attached, which is faster than describing it from memory. The same link appears on a suspended server.

If a build has been in that state for a while, use the link. There is no need to order a second server, and doing so bills a second subscription.

When it is ready

A finished server shows Running and an Open your server link into the gummysnacks panel at panel.gummies.cloud, which is where the console, files, and metrics live. From there the ordinary Minecraft work begins:

Moving a world from another host is a separate procedure worth reading before you start: how to transfer a Minecraft server to a new host.

Sources and review

Reviewed August 17, 2026 against the current billing-portal implementation: the checkout dialog's inventory and promo handling, the provisioning build-step list, and the order states rendered on the server card. Behavior described here is what the portal does today and may be refined before public launch.