Skip to navigation

First resource

A Cloud VM (virtual machine) is a server you rent by the hour: it has its own operating system, CPU, memory, disk and public IP address, and you control it over SSH like any Linux computer. It is the usual first resource on IBEE. This page takes you from an empty organization to a running VM you can log in to, and then shows how to delete it.

Which resource to start with

You want to…Start withGuide
Run a website, an app or a database on your own serverCloud VMThis page
Store files, backups or website assetsObject Storage bucketUpload your first object
Train or run AI models on a GPUGPU VMCreate a GPU VM. New organizations can’t create GPU VMs until their limit is raised.
Get a whole physical serverBare Metal ServerProvision a server

How it works

  1. You choose a location, a plan (the VM’s size and price) and an operating system.
  2. You add an SSH key, so only you can log in.
  3. IBEE checks your billing and limits, then builds the VM. Its status moves from Pending to Running.
  4. You connect with SSH. When you no longer need the VM, you delete it.

Before you begin

Check each item. The portal blocks the deploy if one is missing.

You needWhyHow
An IBEE account and an organizationResources belong to an organization’s workspace.Sign up, then create an organization.
A verified identityUntil you verify, Deploy VM reads Verify Identity.Verify your identity (about 2–3 minutes).
Credits in the walletThe first resource needs a completed purchase (at least ₹500 or $5) or promo credit of at least ₹500.Add billing.
A free CPU VM slotNew organizations (Starter plan) can run 1 CPU VM.Check Billing → Usage Limits.
The owner, Admin or Manager role, or write access to the workspaceOther roles don’t see Deploy VM.Ask your organization’s owner.
An SSH key (recommended)Lets you log in without a password.Create one in the portal while deploying, or on your computer (below).

To make a key on your own computer (macOS, Linux, or Windows PowerShell), run this and press Enter at each question:

ssh-keygen -t ed25519

It creates a private key, ~/.ssh/id_ed25519, which stays on your computer, and a public key, ~/.ssh/id_ed25519.pub, which you give to IBEE.

Launch a Cloud VM in the portal

1

Open Cloud VMs

Open a workspace, for example Production. In the sidebar, click Infrastructure → Cloud VMs, then click Deploy VM. The Deploy page opens.

2

Choose a location

Under Location, click a region tab and a location card, for example Amaravati (VGA · AP, IN). The first location is selected for you. See Regions and locations.

3

Choose a plan

Under Choose Plan, pick a plan. The tabs All, Standard and Performance filter the list. Each row shows vCPU (virtual processors), Memory, Storage, Bandwidth and the Price. For a first test, pick the smallest plan.

4

Choose an operating system

Under Operating System, stay on Templates, click a system such as Ubuntu, and choose an OS Version.

5

Add your SSH key

Under SSH Keys, open Select SSH Keys and tick your key. If you have none, click Add Key, then either:

  • Create Key Pair: enter a name and click Create & Download. The private key downloads once as a .pem file. IBEE stores only the public key, so keep that file safe: it can’t be downloaded again.
  • Import Key: paste the contents of your .pub file and click Import Key.
6

Leave the network settings as they are

Under Network Configuration, keep Public IP, the default. It gives the VM an internet address you can connect to.

7

Choose billing

Under Billing, keep Hourly: no commitment, metered in 15-minute usage windows. Monthly and Yearly are fixed commitments.

8

Name the VM

Under VM Details, enter a Hostname, for example my-first-vm. Use lowercase letters, numbers and hyphens only.

9

Deploy

Check the summary and price at the bottom of the page, then click Deploy. The portal shows VM deploy request accepted. and returns to the Cloud Virtual Machines list.

Check that it worked

In the Cloud Virtual Machines list, the VM’s status moves through Pending, Provisioning and Configuring to Running. The IP address appears once it is Running.

Connect to the VM

  1. Click the VM’s name to open it.
  2. On the Overview tab, find Connection Details. Until the VM is ready it says Credentials will appear here once your virtual machine is ready.
  3. Under SSH Key Connection, note the Username and Host, and copy the Connect Command.

On your computer, run the command. With a key made by ssh-keygen:

ssh -i ~/.ssh/id_ed25519 USERNAME@HOST

With a key the portal created and you downloaded, first restrict the file so SSH accepts it, as Private Key Permissions shows:

chmod 400 ~/Downloads/my-key.pem
ssh -i ~/Downloads/my-key.pem USERNAME@HOST

Replace USERNAME and HOST with the values from Connection Details. The first time, type yes to trust the server. You then see the VM’s command prompt.

Delete the VM when you’re done

Deleting a VM can’t be undone. The VM and all data on its disk are destroyed. Copy anything you need off it first.

  1. Open the VM and click Actions → Delete.
  2. In Delete Virtual Machine, type the VM’s name to confirm.
  3. To keep the VM’s public IP address, tick the box to reserve it. Otherwise it is released.
  4. Click Delete VM.

Attached data volumes are detached, not deleted.

Do the same with the CLI

The IBEE CLI runs the same steps from a terminal. Install it (Python 3.10 or later), set your API token and workspace ID, then look up the IDs and create the VM:

pip install ibee-cli
export IBEE_TOKEN="YOUR-API-TOKEN"
export IBEE_WORKSPACE_ID="907479"
ibee compute sites # copy a site_id
ibee compute plans --vm-type cloud --site-id SITE_ID # copy a plan ID
ibee compute images --vm-type cloud --site-id SITE_ID # copy an image ID
ibee vms create --name my-first-vm --site-id SITE_ID --plan-id PLAN_ID --template-id IMAGE_ID \
--os-type linux --os-distro ubuntu --cpu 2 --ram-mb 4096 --disk-gb 50 \
--billing-interval HOURLY --ssh-keys "$(cat ~/.ssh/id_ed25519.pub)"
ibee ops get OPERATION_ID # repeat until status is succeeded
ibee vms list

Copy --cpu, --ram-mb and --disk-gb from the plan (the example is perf.1.c2.m4) and --os-type and --os-distro from the image. Create prints an operation_id at once and the VM is built in the background.

Delete it when you’re done (release gives up its automatically assigned public IP):

ibee vms delete VM_ID --public-ip-action release --yes

Limits and timing

ItemValue
CPU VMs on a new organization (Starter plan)1. See Limits & Quotas to raise it.
GPU VMs on a new organization0
Hourly billingMetered in usage windows of 15 minutes
First purchase before your first resourceAt least ₹500 (INR) or $5 (USD), unless you have promo credit of at least ₹500
Hostname charactersLowercase letters, numbers and hyphens

Troubleshooting

You seeWhat it meansWhat to do
Verify Identity instead of Deploy VMYou haven’t verified your identity.Verify your identity.
No Deploy VM button at allYour role can’t create resources in this workspace.Ask the organization’s owner for write access.
Billing needs attention with Add at least ₹500 to your wallet before creating your first cloud VM.You haven’t made a first purchase or received promo credit of at least ₹500.Click Add Credits. See Add billing.
Your available wallet balance does not cover this cloud VM. Add credits and try again.The balance is too low for this plan.Add credits, or choose a smaller plan.
CPU VM limit reached: 1 used of 1 allowed. Change your plan or remove a VM before deploying another.Your plan’s CPU VM limit is used up.Delete a VM you don’t need, or ask for a higher limit under Billing → Usage Limits.
No plans available for this location and category.No plan in this tab is offered at this location.Switch to the All tab or another location.
Talk to Sales on a planThe plan is out of stock.Pick another plan.
The status shows ErrorThe VM couldn’t be built.Delete it and deploy again. If it happens again, contact support.
Permission denied (publickey) when connectingSSH didn’t offer the key that was added to the VM, or the username is wrong.Use the Username from Connection Details and point -i at the matching private key.
UNPROTECTED PRIVATE KEY FILE!The private key file can be read by other users.Run chmod 400 on the key file, then connect again.
Connection timed outThe VM isn’t Running yet, the address is wrong, or a firewall blocks port 22.Wait for Running, check Host, and check your firewall rules.