For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
LoginGet Started
DocsAPI ReferenceChangelog
DocsAPI ReferenceChangelog
    • Home
  • Getting Started
  • Infrastructure
    • GPU VMs
    • Cloud VMs
      • Create a VM
      • Instance types
      • OS images
      • Custom images
      • Resize a VM
      • Power actions
      • Networking for VMs
      • Attach volumes
      • Monitoring
    • Object Storage
    • Block Storage
  • Network & Security
    • Load Balancer
    • DNS
    • CDN
    • Firewalls
    • SSL Certificates
  • Tools
    • Backups
    • Snapshots
    • ISOs
    • SSH Keys
    • API Tokens
    • Secret Manager
    • Container Registry
  • Platform Fundamentals
    • Projects and tenancy model
    • IAM
    • Networking overview
    • Billing and usage
    • Limits and quotas
    • SLA and reliability
  • Tutorials
    • Deploy a web app
    • Host a static website with object storage
    • Run an AI model on a GPU VM
    • Set up a load-balanced architecture
    • Backup and disaster recovery
    • Multi-region deployment
  • Migration Guides
    • Migrate from AWS
    • Migrate from GCP
    • Migrate from Vultr and Linode
    • Move S3 workloads to IBEE Object Storage
    • VM image migration
  • Reference
    • Pricing
    • Regions
    • Limits
    • Error codes
    • Service level agreement
  • Support
    • Contact Support
    • Create a request
    • Troubleshooting guides
    • Visit ibee.ai
LogoLogo
LoginGet Started
On this page
  • Standard VMs — Network Bandwidth
  • Performance VMs — Network Bandwidth
  • Reading the columns
  • Choosing a family
  • Naming convention
  • What’s included
  • Resizing between plans
  • Related pages
InfrastructureCloud VMs

Instance types

Was this page helpful?
Edit this page
Previous

OS images

Next
Built with

IBEE Cloud VM instance types come in two families: Standard for balanced everyday workloads and Performance for compute-optimized workloads that need higher CPU density. Every instance type ships with included disk and bandwidth.

Standard VMs — Network Bandwidth

Reliable virtual machines with balanced vCPU and memory — the right default for most production workloads. Each plan ships with a private-network ceiling that scales with size and a default 100 Mbps public-network NIC.

PlanPrivate NetworkPublic NetworkUpgradable Public
std.1.c2.m8Up to 5 Gbps100 Mbps (default)On request to sales
std.1.c4.m16Up to 10 Gbps100 Mbps (default)On request to sales
std.1.c8.m32Up to 20 Gbps100 Mbps (default)On request to sales
std.1.c16.m64Up to 25 Gbps100 Mbps (default)On request to sales
std.1.c32.m128Up to 40 Gbps100 Mbps (default)On request to sales
std.1.c64.m256Up to 40 Gbps100 Mbps (default)On request to sales

std.1.c4.m16 is the most popular choice for new production deployments.

Performance VMs — Network Bandwidth

Compute-optimized virtual machines with stronger CPU density, for workloads that need faster processing per core. Each plan ships with a private-network ceiling proportional to size and a default 100 Mbps public-network NIC.

PlanPrivate NetworkPublic NetworkUpgradable Public
perf.1.c1.m2Up to 2 Gbps100 Mbps (default)On request to sales
perf.1.c2.m4Up to 5 Gbps100 Mbps (default)On request to sales
perf.1.c4.m8Up to 10 Gbps100 Mbps (default)On request to sales
perf.1.c8.m16Up to 20 Gbps100 Mbps (default)On request to sales
perf.1.c16.m32Up to 25 Gbps100 Mbps (default)On request to sales
perf.1.c32.m64Up to 40 Gbps100 Mbps (default)On request to sales
perf.1.c64.m128Up to 40 Gbps100 Mbps (default)On request to sales

perf.1.c4.m8 is the most popular Performance plan.

Reading the columns

ColumnMeaning
Private NetworkMaximum bandwidth between VMs in the same region over the IBEE backplane.
Public NetworkDefault outbound bandwidth on the public NIC. Inbound is unmetered.
Upgradable PublicThe public NIC can be raised above 100 Mbps — contact IBEE sales to request a higher tier.

vCPU, RAM, and disk for each plan are encoded in the plan name (see Naming convention).

Choosing a family

Pick Standard if…Pick Performance if…
Workload is memory-balanced (typical web/API/database)Workload is CPU-bound and scales with cores
You want the broadest fit for productionYou need higher per-core throughput
You expect mixed CPU and RAM usageRAM is comfortable but CPU is the bottleneck

For GPU-accelerated workloads (training, inference, rendering), see GPU VMs.

Naming convention

Plan names follow <family>.<gen>.c<vCPU>.m<RAM-GiB>:

  • std.1.c4.m16 — Standard family, generation 1, 4 vCPU, 16 GiB RAM.
  • perf.1.c8.m16 — Performance family, generation 1, 8 vCPU, 16 GiB RAM.

The generation number changes when the underlying hardware platform is refreshed.

What’s included

Every plan includes:

  • NVMe root disk sized per plan
  • Outbound bandwidth allowance per plan; inbound is unmetered
  • Public IPv4 address with reverse DNS
  • Snapshot and backup eligibility (Backups, Snapshots)
  • Console access in the IBEE Cloud portal

Storage beyond the included disk is added separately as Block Storage.

Resizing between plans

You can move a running VM to a larger plan from Settings → Change Plan. The VM is briefly stopped, resources are upgraded, and it restarts on the new plan. Disk size grows with the new plan; CPU and RAM are updated atomically. See Resize a VM.

Related pages

  • Launch your first VM
  • Create a VM
  • Resize a VM
  • GPU instance types
  • Regions and locations