Creating a Resource

Every new server, GPU instance, dedicated machine, transit port, colocation block, or addon goes through the same order flow in the portal. This page walks through the universal path - from clicking Order new in the sidebar to seeing the resource provisioned.

For the per-product specifics (which sliders are on the VPS Configure step, what the dedicated-server stock board looks like, etc.) jump to the matching product page in the ordering section.

• Pick the right organization. Resources can't be moved between organizations after they're created. Switch the org switcher at the top of the sidebar before you start the order.
• Pick the right project. The order will be placed into whichever project you started the flow from. To start in a different project, expand a different one in the sidebar.
• Add a payment method to the organization. Card, PayPal, and crypto (BitPay) work for new orders. ACH bank-transfer payment methods can't be used to place a new order - they only pay existing invoices. 
• Add an SSH key to your account if you plan to use one (most VPS / dedicated orders ask for one). 
• Have the Resources role (or be an owner / admin). Read-only and billing-only members can't place orders.

There are two equivalent entry points into the catalog:

From a project. In the sidebar, expand the project you want the new resource to belong to. At the bottom of the expanded project list, click Order new.

From the topbar. If the page you're on has an Order new button in the topbar, click it. Same effect - opens the catalog with the current project pre-selected.

The catalog opens at /order/type showing a grid of product tiles:

• VPS (Cloud)
• VDS Perfomance (Cloud)
• GPU Cloud (GPU Cloud)
• Instant Metal (Metal) 
• Block Storage (Storage)
• GPU Metal (Custom quote required. Metal)
• Bare Metal (Custom quote required. Metal)

Each tile is a brief description of the product. Click the tile for the product you want - that opens the product-specific order flow.

If the product you want is out of stock at every location, the tile is visibly disabled with a "Notify me" link instead.

Every product's order flow has the same three steps along the top of the page:

1. Plan: pick the spec.
2. Configure: pick everything else (location, OS, hostname, SSH key, quantity).
3. Payment: pick the payment method and place the order.

The current step is highlighted in the stepper at the top. You can step backward at any time. Stepping back never loses your selections - they're remembered until you place the order.

The org and project the order will belong to are shown in the top-right corner of every step. Click them to switch before placing the order.

The Plan step is where you pick the spec - CPU, RAM, disk, bandwidth, GPU model (if applicable).

Depending on the product type, you'll receive one or two configuration options:

Pre-sized plans (default). A list of plan cards, each with the headline spec and monthly price. Click a card to select it; the selected card is highlighted.

Custom spec (tab at the top of the step): Sliders for each spec axis - CPU cores, RAM, disk, bandwidth, IPv4 count. The monthly total updates live as you drag.

A few things about the plan step:

• Plans out of stock at every location are disabled.
• Plans with limited stock at specific locations look fine here - they'll flag the limitation when you pick a location on the next step.

When you're happy, click Continue at the bottom of the page. You move to Configure.

The Configure step is where you set everything that isn't part of the plan.

Common fields across products:

• Location: the data centre. Each option shows a flag and city name. Out-of-stock locations are greyed out.
• Operating system (Cloud, GPU Cloud, Metal): pick a Linux distribution or Windows version. Grouped by family with version sub-choices.
• Quantity: order more than one identical resource in a single transaction. Bumping the stepper expands the Hostname field into a list, prefillable with patterns like web-{n}.
• Hostname: what the resource will be called. Must be lowercase letters, digits, hyphens; at least 3 characters. Used as the system hostname inside the OS.
• SSH key: pick a saved key from your account or paste one in inline. Skip this only if you're setting a password instead.
• Credentials: set the initial password for the default user. Optionally also set a custom username instead of the distribution default.

When everything's filled in, click Continue. If the button shakes briefly, a required field is missing - scroll up to find the flagged one (usually outlined red).

The Payment step has two halves:

• Left: your saved payment methods, with one selected. Card, PayPal, and crypto are eligible for new orders; ACH methods are shown as disabled with an explanation.
• Right: the order summary with line-by-line breakdown (plan, extras, IPv4s, bandwidth, VAT) and the total at the bottom.

What you can do here:

• Apply credits. If your org has credit available, tick Apply credits to consume it before charging your payment method. If credits cover the total, no card charge happens.
• Switch payment method. Radio buttons on the left.
• Edit billing address. If your address has changed since you added the org, click the small Edit next to it in the summary.

When you're ready, click the Place order button at the bottom. Its label includes the total - e.g. Place order - $42.50.

What happens next depends on the payment type.

The charge runs immediately. As soon as it succeeds:

1. The order appears in your resource list under the matching category (Cloud, Metal, etc.) with a Provisioning badge.
2. The portal polls in the background while the resource is being set up. Most deployments take 5–10 seconds from a cached image.
3. When provisioning finishes, you're redirected to the resource detail page where you can manage it.

Crypto is asynchronous - the resource isn't provisioned until the blockchain confirms the payment.

1. Clicking Place order redirects you to BitPay's hosted checkout in a new tab.
2. The order is created in Awaiting crypto payment state in your resource list. A badge on the row links to the pending-order page.
3. Once BitPay reports the transaction confirmed (usually 5–15 minutes), provisioning kicks off automatically and the order moves into the same flow as a card order.
4. If you don't pay within 24 hours, the order auto-cancels and the invoice is voided. You can also cancel or switch the payment method yourself from the pending-order page.

A successful order does several things at once:

• The new resource appears in the sidebar under the right project / category.
• An invoice is generated for the prorated portion of the current billing cycle, marked Paid.
• A confirmation email goes to the org's billing recipients.
• The order is logged in Organization Settings > Activity 

Three common failure modes:

• Card declined / 3DS failed. The payment step shows an inline error and the order isn't placed. Pick a different method or contact your card issuer.
• Out of stock by the time payment ran. The portal retries from the order summary; if stock is gone, you get a clear "no longer available" message and your card isn't charged.
• The portal can't reach the provisioning backend. The order is queued and provisioning resumes when the backend recovers - you don't need to do anything.

If something looks stuck for more than 15 minutes (an order in Provisioning state without progress), open a support ticket from Support > New ticket.