Why teams use it

Full control, no shared cores.

Tower gives you dedicated vCPU and memory per instance, root access from first boot, attachable block disks, and the same predictable SKU model as our other compute lines,so capacity planning and procurement stay straightforward.

dedicated VMready
Computededicated vCPU
MemoryECC RAM
Storagedistributed disk
AccessSSH from boot

Under the hood

Dedicated silicon, distributed block disks.

Instances run on enterprise-grade AMD EPYC hardware with ECC memory. You are not sharing a kernel with strangers; noisy neighbours are kept out of your performance envelope by design.

Root and data disks live on our distributed block service, low-latency storage suited to databases and I/O-heavy workloads rather than a single point of failure on one machine.

Public and private connectivity options follow the same regional networking model as the rest of Tower, so VMs sit naturally beside databases, sites, and containerised apps in hybrid architectures.

compute layerdedicated vCPU SKU
memory layerECC RAM allocation
storage layerdistributed block disk
network layerpublic and private routes
access layerSSH root from boot
Capabilities

What you get on Day One

Curated OS images, SSH from boot, attachable disks, and integrated backup workflows,without running your own data centre.

Full root access

SSH in from first boot. Install packages, tune the kernel where your image allows, and bring supported custom images when your plan includes them. You own the guest; Tower owns the rack.

Flexible sizing

Choose vCPU and memory SKUs that match real workloads,from small dev boxes to larger production profiles,with clear limits so performance stays predictable.

Attachable block storage

Add data disks for databases, build caches, and log-heavy services. Disks persist across reboots and attach through the same Tower APIs you use elsewhere on the platform.

Automated backups

Backup retention policies integrate with Tower backup services. Restore through the portal or API instead of manual disk copies.

Technical reference

Configuration & Platform Details

A concise reference for architecture reviews, procurement, and security questionnaires.

Platform specifications

Isolation model
Dedicated virtual hardware per instance with fixed vCPU and memory allocations. No oversubscription of purchased cores to other tenants.
Compute platform
AMD EPYC based regions with ECC memory for workloads that need a full OS boundary.
Persistent storage
Distributed block disks with online growth where the guest OS supports it. Designed for database and high I/O use cases.
Networking
Regional public and private connectivity consistent with other Tower compute products. Interconnect options vary by plan and region.
Operating systems
Curated OS image catalog with supported custom images where included by plan.
Operational split
Tower maintains the physical fleet, storage service, and platform APIs. Customers maintain the guest OS, packages, and data inside the VM.
Backups
Integrated backup retention policies with restore flows in the portal and API.

Pricing

Compute

Loading VM SKUs…

Loading SKUs...