Hubfly spaceDocs
Console

Box · Guide

Create your first Box

Choose an image and size, set a safe login method, then follow provisioning until your VM is ready.

1. Create a Box project

In Dashboard, create a project and select Box as its platform. Choose a region that offers Box. A Box project is the home for its virtual machines, data volumes, and network resources.

  • Check Box eligibility and available balance if project creation is refused. Region selection determines the image catalog and host capacity.
  • A project can contain multiple Boxes. Names are labels you choose; resource IDs are the stable identifiers used by the API.

2. Choose the image and size

Select an available Linux cloud image from the regional catalog. The create dialog offers Starter (1 vCPU, 1 GiB RAM, 20 GiB disk), Balanced (2/4/50), Compute (4/8/100), Pro (8/16/200), and a custom size.

  • The API takes memoryMib and rootDiskGib, so 4 GiB of RAM is 4096 MiB. The create dialog currently caps custom sizes at 16 vCPUs, 32 GiB RAM, and 400 GiB root disk.
  • Pricing is based on CPU, RAM, and storage; read the current pricing endpoint or review step for the actual rate. Do not hardcode a rate in automation.
  • The initial CPU and memory choice also affects the topology reserved for later live growth. See resizing before selecting a very small starting shape.

3. Configure access and initialization

Use an SSH public key, a generated password, or both. Paste a full public key, never your private key. You can also provide cloud-init YAML for supported managed Linux images.

  • If you request a generated password, reveal and save it once. A password cannot be recovered from the Box list later.
  • Cloud-init config runs inside the guest. A guest script error can leave the VM powered on but initialization failed; inspect initialization status and console output.
  • Keep a known-good access path while changing SSH or firewall settings. The console can help recover guest network or login configuration.

4. Wait for readiness

Creation returns a Box ID and operation ID while host provisioning continues. The Box list shows the resource; the operation record tells you whether provisioning finished.

  • Wait for succeeded, failed, partial, or canceled. Check the initialization view separately before relying on cloud-init completion.
  • For an application, bind it to the guest's network interface and publish it with an HTTP domain or TCP/UDP port mapping. A running VM does not automatically expose every guest port.
  • Use Box metrics and console after provisioning to confirm your app actually started.

Automating this workflow

See the matching Box API endpoints for exact request fields and response schemas. Host operations can continue after an API request returns.

Back to the Box guide · All Box API groups

Something unclear or out of date? Emailsupport@hubfly.spaceBack to top