Create a GPU VM
Creating a GPU VM gives you a Linux server with an NVIDIA GPU attached, ready for AI, rendering or video work. The portal’s Deploy page is a single form with a running cost summary and the Deploy button in the bottom bar. It works like the Cloud VM Deploy page, with GPU plans and GPU-compatible images.
Which options to choose
How it works
- You choose a location, a GPU plan, a Linux image, SSH keys and the network, and click Deploy.
- The portal checks your billing state and wallet balance, then queues the VM. It shows Provisioning, then Running.
- Billing starts when creation finishes. A create that fails isn’t billed.
- You sign in, run
nvidia-smi, and install the NVIDIA driver if the image doesn’t include it.
Before you begin
- An IBEE account with a verified identity, and write access to the workspace.
- Credit in your wallet for the GPU plan’s hourly price (Billing and usage).
- An SSH key. You can also create one on the Deploy page.
- GPUs are limited per location. The Deploy page only lets you pick as many VMs as there are free GPUs.
Create a GPU VM in the portal
Select a location
Under Location, pick a region tab and a data center. GPU models differ between locations.
Choose a GPU plan
Under Choose Plan, select a plan. Each row lists the GPU model and its Memory, plus vCPU, RAM, Disk, and the price per month and per hour. GPU VMs are billed Hourly; the monthly figure is the hourly rate × 731 hours.
Select the operating system
Under Operating System → Templates, pick a family card, then a version from OS Version. Only GPU-compatible images are listed. You can also start from Snapshots or Backups of another GPU VM. ISOs aren’t available: the tab shows “No ISOs available for this account.”
Add SSH keys
Open Select SSH Keys and pick one or more saved keys, or click Add Key to create or import one. Without a key, the VM gets a generated password, shown under Overview → Connection Details.
Configure the network
Under Network Configuration, choose Public IP (default), Private + NAT or Private only, and a VPC and subnet if needed. Under Firewall, pick a group or leave it empty to attach the default group, which allows SSH (22), HTTP (80), HTTPS (443), RDP (3389) and ports 8000–8080. See Networking for VMs.
Create a GPU VM with the CLI
GPU VMs use ibee gpus (Cloud VMs use ibee vms). Export an API token with the vm.read and vm.write scopes and your workspace ID first:
The CLI sends only what you pass: copy the vCPUs, memory, disk, GPU model and GPU count from the plan, and the OS from the image. --billing-interval HOURLY (or MONTHLY) makes the CLI read the plan and send its billing selection, as the portal does. The command prints an operation_id; run ibee ops get OPERATION_ID until status is succeeded or failed. To check capacity first, call GET /compute/plans?vm_type=gpu&site_id=SITE_ID&include_availability=true&workspace_id=...: each plan’s availability is available, unavailable or unknown. The check is advisory and doesn’t hold a GPU for you.
The API operation is POST /compute/gpu-vms, with an X-Idempotency-Key header. It takes the same fields as a Cloud VM create plus gpu_model and gpu_count, and accepts Linux images only (os_type: linux).
Verify
When the VM shows Running, sign in with the command from Overview → Connection Details:
nvidia-smi prints a table with the GPU model, its memory, the driver version and the CUDA version the driver supports. If you see nvidia-smi: command not found, install the driver as below.
Install the NVIDIA driver
Some images come without an NVIDIA driver. On Ubuntu, install the recommended driver and restart:
After the restart, sign in again and run nvidia-smi. Install the CUDA toolkit or a framework such as PyTorch only if your software needs it; GPU monitoring needs only the driver.
Manage your GPU VM
The VM’s page has Actions (Start, Stop, Reboot, Delete; Console shows Soon) and these tabs:
A stopped GPU VM is billed at the full hourly rate. Delete it when you’ve finished, and take a snapshot first if you want to come back to it.
