Skip to navigation

Cloud VMs

A Cloud VM (virtual machine) is a server you rent by the hour. It runs on IBEE’s hardware, but to you it looks like a normal computer: it has its own vCPUs, memory, a disk, an operating system you choose (Linux or Windows) and, usually, a public IP address you can reach over the internet. You create one in the portal, with the ibee CLI or with the API, and you sign in to it with SSH (Linux) or Remote Desktop (Windows).

New here? Follow Launch your first VM: create a VM, connect to it, and delete it again.

When to use a Cloud VM

You want to…UseWhy
Run a website, API, app backend, database, or dev environmentCloud VM (this page)Self-service, billed by the hour, resizable later
Train or serve AI models, render video, or run other GPU workGPU VMSame as a Cloud VM, plus an NVIDIA GPU
Have a whole physical server to yourself (no other tenants, physical cores)Bare metal serverOrdered through the sales team, billed monthly
Store files, backups or media that apps read over HTTPObject StoragePay per GB stored; no server to manage
Add disk space that survives deleting the VMBlock StorageA separate disk you attach to a VM

How it works

  1. You pick a location, a plan (vCPU, memory, disk), an operating system image and how the VM connects to the network.
  2. IBEE creates the VM. Its status shows Provisioning and then Running. Billing starts when creation finishes; a create that fails is not billed.
  3. You connect with the username and address shown under Overview → Connection Details.
  4. You delete the VM when you no longer need it. Only deleting stops the hourly charge.

Before you begin

  • An IBEE account with a verified identity. Deploying servers is locked until verification is complete.
  • Write access to the workspace. Members with read-only access can see VMs but not the Deploy VM button or the Actions menu.
  • Credit in your wallet. The portal checks your billing state and balance before it creates anything. See Billing and usage.

Key facts

QuestionAnswer
Where can I run one?Amaravati (VGA) and Hyderabad (HYD), India. The Deploy page lists only the locations open to your organization. See Regions and locations.
What sizes are there?Two families, Standard and Performance, from 1 vCPU / 2 GiB RAM / 50 GB disk up to 64 vCPU / 256 GiB RAM / 400 GB disk. See Instance types.
How many can I create at once?Up to 5 VMs in one deploy. The limit can be lower when capacity or free public IP addresses in the location run short, and your plan can cap the total number of VMs.
What is the default username?Linux: the image’s distribution name, for example ubuntu on Ubuntu. Windows: Administrator. The exact value is under Overview → Connection Details.
How is it billed?Hourly by default: no commitment, usage collected in 15-minute windows and charged for the time the VM exists. Some plans also offer a Monthly commitment.
Am I billed while it is stopped?Yes. A stopped VM is billed at the same hourly rate as a running one, from creation until it is deleted. Delete the VM to stop the charge.
Which ports are open?The default firewall group allows inbound TCP 22 (SSH), 80 (HTTP), 443 (HTTPS), 3389 (RDP) and 8000–8080, and all outbound traffic. Every other inbound connection, including ping, is dropped. See Networking for VMs.
Can I make it bigger later?Yes. Settings → Change Plan changes vCPU, memory and disk. The disk can grow but never shrink. See Resize a VM.
Is there a browser console?Not yet. The Console control shows Coming soon. Use SSH or RDP.

Find your VMs

In the portal sidebar, open Infrastructure → Cloud VMs. The Cloud Virtual Machines list shows each VM’s Instance, OS, Location, IP Address and Status. Use Search or filter VMs… to find one, the sort menu to order by Created, Name, Status or OS, and click a row to open the VM.

From the API, GET /compute/cloud-vms returns one page of VMs: 10 by default, up to 100 with limit, and offset for the next page.

Status reference

StatusMeaning
Pending, Provisioning, ConfiguringThe VM is being created.
RunningThe VM is on.
Starting, Stopping, RebootingA power action is in progress.
StoppedThe VM is off. Disks, IP address and settings are kept, and billing continues.
Resizing, RestoringA plan change or a restore is in progress.
DeletingThe VM is being deleted.
ErrorThe last operation failed. Check Activity logs.

Lifecycle of a VM

StageWhat you doWhere
DeployPick location, plan, OS, SSH keys, network, billing term and hostname.Create a VM
ConnectSign in with SSH or RDP; open the ports your app needs.Networking for VMs
Store dataAttach a Block Storage volume for data that should outlive the VM.Attach volumes
OperateWatch metrics; start, stop and reboot.Monitoring · Power actions
ProtectTurn on scheduled backups or take snapshots.Backups · Snapshots
ScaleMove to a bigger or smaller plan.Resize a VM
RetireDelete the VM, optionally keeping its IP address.Power actions

Glossary

TermMeaning
vCPUA virtual processor core. Plans list how many the VM gets.
PlanA fixed size: vCPUs, memory (GiB), root disk (GB) and included outbound data per month.
Image (template)The operating system the VM is created from, such as Ubuntu 24.04.
Root diskThe disk the operating system boots from. Its size comes from the plan.
Public IPAn internet address other computers use to reach the VM.
VPCA private network of your own, for traffic between your VMs.
Firewall groupA set of rules that decides which inbound connections reach the VM.

Troubleshooting

You seeWhat it meansWhat to do
Billing needs attention when you deployYour billing state or wallet balance doesn’t cover the VMClick Add Credits, top up, then deploy again.
CPU VM limit reached: … Change your plan or remove a VM before deploying another.Your organization has reached its maximum number of Cloud VMsDelete a VM you don’t need, or ask to raise the limit.
ssh: connect to host … port 22: Connection timed outThe VM isn’t running yet, or a firewall group blocks port 22 from your addressWait for Running, then check the VM’s firewall group.
The bill grows although the VM is stoppedStopped VMs are billedTake a snapshot if you need the data, then delete the VM.