Quickstart

Servers

A Unio Cloud server is a KVM virtual machine with NVMe storage, a public IPv4 and 20 TB of traffic included. Billing is hourly and capped at the monthly price, so a server you delete after two days costs two days.

1. Launch a server

Open Create a server in the console and pick a type, an image, and your SSH keys. Everything else is automatic: your private network, the router to the internet, and a public IPv4 are created and attached for you. Servers are usually reachable in under a minute.

• Type: shared vCPU (u23, u33, u43, u53) for variable workloads, dedicated vCPU (d-series) for sustained load.
• Image: Debian 13 or Ubuntu 24.04, both cloud images with cloud-init.
• SSH keys: saved to your account under SSH Keys and offered at every launch. Without a key you cannot log in over SSH.
• Nested virtualization: the virtualization flag is exposed, so /dev/kvm works inside your server (CI runners, emulators, lab hypervisors). Available as-is and unsupported: nested guests run with reduced performance.

2. Log in

# the console shows your public IP right after launch
ssh root@203.0.113.10

# the image ships with your selected SSH keys already installed;
# the default users (debian / ubuntu) work too:
ssh debian@203.0.113.10

Every new server also gets a root password for the browser console, shown once in the dialog right after launch. It works only at the browser console (SSH stays key-based), which is exactly what you want when you have locked yourself out of SSH.

3. The browser console

On the server page, click Console to open a VNC session in a new tab. You see the boot sequence and get a login prompt, so you can fix a broken sshd, a bad firewall rule or an fstab typo without any working network service. Log in as root with the password from launch. If the screen looks frozen, press Enter: the login prompt is often just scrolled behind boot output.

4. Cloud-init

Paste a cloud-config into the Cloud config field at launch and it runs on first boot. Note that a custom cloud-init replaces our generated one, so include your own SSH keys (and password, if you want one) explicitly.

#cloud-config
package_update: true
packages:
  - docker.io
  - fail2ban
runcmd:
  - systemctl enable --now docker
  - ufw allow 22/tcp && ufw --force enable

5. Resize, rebuild, delete

• Resize moves the server to a different type. It reboots into the new size and then asks you to confirm or revert. Disks can grow, never shrink.
• Rebuild reinstalls the operating system from a fresh image. The local disk is erased; attached volumes survive.
• Delete destroys the server and its local disk permanently, and releases its public IP. Volumes and buckets are untouched. Billing stops the hour the server is gone.

Back up what matters. The local disk is fast but not durable against your own mistakes: use volumes or object storage for anything you cannot lose.

6. Firewall rules

The Security tab on a server lists its security groups and their rules. New projects start with SSH and ICMP open, everything else closed inbound. Add a rule (protocol, port range, source CIDR) to expose a service, for example TCP 443 from 0.0.0.0/0 for a web server. Rules apply immediately, no reboot.

7. What it costs

Servers are billed hourly from your prepaid credit at the published rate and never exceed the monthly price. A stopped server still occupies its disk and IP, so it keeps billing: delete it to stop paying. Watch your balance and history under Billing & credentials. If your balance hits zero, servers are suspended after a grace period, not deleted.