Virtual Machines - Hikube

Reliable VMs,
100% hosted in Switzerland.

High-availability infrastructure across three Swiss data centres. Automatic restart on failure, replicated storage, data under Swiss jurisdiction. Deploy in minutes.

3 DCs

Independent Swiss data centers

<5 min

Automatic restart after failure

64 vCPU

Maximum per VM

256 RAM

Maximum RAM per VM
Why Hikube

A sovereign infrastructure

For Swiss and European companies, hosting their data with a US hyperscaler creates real jurisdictional risks. Hikube offers a high-performance alternative with no compromise on sovereignty.

A 100% Swiss cloud, why it matters:

Faced with the US Cloud Act and GDPR and nFADP compliance requirements, hosting your VMs in Switzerland is no longer a luxury, it's a necessity for any company handling sensitive data. Your data stays under Swiss jurisdiction, one of the most protective in the world.

Triple replication across 3 independent sites (Gland, Lucerne, Geneva) guarantees service continuity even if an entire data centre fails.With no manual intervention on your side.

A credible alternative to AWS, Azure and GCP for workloads that require data sovereignty, regulatory compliance or independence from US providers.

Frame 11509
What you deploy on Hikube:
markup-cropped

Migration from VMware or Proxmox

Import of custom VMDK, QCOW2 and ISO images. Move over without rewriting your applications.

markup-cropped

AI workloads with dedicated GPU

Attach an L40S, A100 or H100 GPU directly to a VM via PCI Passthrough. Exclusive access to the hardware and native performance.

markup-cropped

Legacy applications and specific OS

Windows Server, Linux distributions with a custom kernel, software that can't be containerised... Deploy the exact OS and dependencies you need.

markup-cropped

Isolated and regulated environments

Finance, healthcare, public sector. Your VMs run in an isolated tenant, on infrastructure whose exact geographic location you know.

Available configurations

Three families for every workload profile

The vCPU/RAM ratio determines the right family for your workload. Every family is available from small to 8xlarge.

S series

Standard - ratio 1:2

CPU-intensive workloads with low memory requirements.

s1.small 1 vCPU - 2 GB
s1.medium 2 vCPU - 4 GB
s1.large 4 vCPU - 8 GB
s1.xlarge 8 vCPU - 16 GB
s1.3large 12 vCPU · 24 GB
s1.2xlarge 16 vCPU - 32 GB
s1.3xlarge 24 vCPU · 48 GB
s1.4xlarge 32 vCPU - 64 GB
s1.8xlarge 64 vCPU · 128 GB

U series

Universal- ratio 1:4

A balanced ratio. The right starting point for most applications.

u1.medium 1 vCPU - 4 GB
u1.large 2 vCPU - 8 GB
u1.xlarge 4 vCPU - 16 GB
u1.2xlarge 8 vCPU - 32 GB
u1.4xlarge 16 vCPU - 64 GB
s1.8xlarge 32 vCPU - 128GB

M series

Memory - ratio 1:8

High-memory instances for RAM-hungry applications.

m1.large 2 vCPU - 16 GB
m1.xlarge 4 vCPU - 32 GB
m1.2xlarge 8 vCPU - 64 GB
m1.4xlarge 16 vCPU - 128 GB
m1.8xlarge 32 vCPU - 256 GB

Quick guide

Compute-intensive → s1 - General-purpose → u1 - Databases and analytics → m1
Network & Access

Connect the way you want

Each VM gets a private IP on an isolated network. External exposure is optional and can be configured in two modes to match your security requirements.

PortList

Automatic firewall - dedicated IP

Only the ports you list are exposed. The firewall is applied automatically at service level, for a minimal attack surface with no extra configuration.

WholeIP

Dedicated public IP - All ports

A public IP is assigned directly to the VM, and all ports are reachable. You must configure a firewall inside the VM itself.


Three ways to access your VM once deployed:


  • SSH
    Via virtctl ssh or directly via the external IP with your usual SSH client.

  • Serial console
    Low-level access directly to the VM, independent of network status. Useful if SSH connectivity is lost.

  • VNC
    Graphical interface via secure tunnel. Especially useful for Windows VMs or desktop environments.

WholeIP - firewall mandatory inside the VM

In this mode, all ports are open to the Internet. Configure ufw, iptables or nftables inside the VM to protect your services.
getting started

Deploy in minutes

Two resources to create: a system disk (VMDisk) from an Ubuntu, Debian, Rocky or other image, and a VM (VMInstance) that references this disk, defines the configuration and injects your SSH key.

The cloudInit field lets you install packages, create users and run scripts on first boot, without manual login.

With storageClass: replicated, your disk is replicated across all 3 datacentres from creation.

yaml

kind: VMInstance
metadata:
name: vm-instance
spec:
instancelype: u1.xlarge # 4 vCPU, 16 GB
instanceProfile: ubuntu
running: true
external: true
externalMethod: PortList
externalPorts:
- 22
- 443
disks:
- mon-disque
sshKeys:
- "ssh-ed25519 AAAA... user@host"
cloudInit: |
#cloud-config
packages:
- nginx
- htop
runcmd:
- systemctl enable nginx

AVAILABLE IMAGES

Supported operating systems

Pre-configured and optimised images for each distribution. Specify the image in your VMDisk or import a custom image from an HTTP URL.

UBUNTU

22.04 - 24.04

DEBIAN

12 - 13

ROCKY LINUX

8 - 9 - 10

ALMALINUX

8 - 9

CENTOS STREAM

9 - 10

WINDOWS

2022 · 2025

ID format

ubuntu-2404, debian-12, rocky-9, almalinux-9. For VMware (VMDK), Proxmox (QCOW2) or custom ISO images, use the VMDisk manifest.
FAQ

Cloud Instances FAQ

What happens if the server hosting my VM goes down?

The platform detects the failure and automatically restarts your VM on another available server, in the same datacenter or another. Downtime is limited to the VM reboot typically under 5 minutes. Your data stays intact thanks to disk replication across multiple physical nodes.

Which instance family should I choose?

The S family (1 vCPU for 2 GB RAM) suits CPU-intensive workloads with little memory: CI/CD, compilation, computation. The U family (1:4) is the right starting point for most applications: web, APIs, lightweight databases. The M family (1:8) is built for RAM-hungry workloads: SAP HANA, analytics, large Redis caches, data warehouses.

What's the difference between PortList and WholeIP?

PortList exposes only the ports you list, with an automatic firewall. This is the recommended mode for production - you keep precise control over what's reachable from outside.

WholeIP assigns a public IP directly to the VM with all ports open. No automatic firewall - you must configure one inside the VM. Useful for VMs acting as gateways or VPNs, or for development where you need full access.

Can I migrate my VMware or Proxmox VMs to Hikube?

Yes, Hikube supports importing VMDK (VMware), QCOW2 (Proxmox/OpenStack) and custom ISO images. Your existing VMs migrate without rewriting any applications.

How do I customise my VM at first boot?

Use the cloudInit field in the VMInstance manifest. Cloud-init runs at first boot and lets you install packages, create users, inject SSH keys and run shell commands. No manual login is needed for initial configuration.

Is my data really in Switzerland?

Yes, entirely. Hikube's infrastructure is hosted in 3 datacentres in Switzerland (Gland, Lucerne, Geneva). Your data never leaves Swiss territory. Native RGPD and nFADP compliance guaranteed. We can provide a DPA and complete your compliance questionnaires on request.