Skip to Content
Open Beta — managed Kubernetes, DNS & more are live.
🖧

Virtual machines (VPS)

Updated 2026-11-20
On this page

Virtual machines (VPS)

A virtual machine (VPS) is an on-demand server you fully control — pick a size and an operating system, and your instance is running in minutes, hosted in Canada.

Virtual machines are the foundation of Patrii Cloud. Each instance runs on redundant infrastructure with its own CPU, memory and disk, its own network interfaces, and full root/administrator access — run anything from a small web server to a database or a CI build agent.

Every aspect of an instance is under your control from the console or the API: power state, size, networking, snapshots and backups, the boot image, and a browser console for when SSH isn't available.

Screenshot — The Compute > Instances list showing running virtual machines with their status, size and IP address
The Compute > Instances list showing running virtual machines with their status, size and IP address

Key concepts

Instance — A single running virtual machine.

Flavor (size) — The CPU, memory and root-disk allocation an instance is created with.

Image — The operating-system template an instance boots from — a public image or one of your snapshots.

Keypair — The SSH public key injected at boot so you can log in without a password.

Security group — The virtual firewall that controls which ports are reachable.

Floating IP — A public address you attach to make the instance reachable from the internet.

Before you start

  • An SSH keypair in your project (Compute > Keypairs) so you can log in.
  • A network with a subnet; add a router if the instance needs outbound internet.
  • A security group that allows the ports you need (for example TCP 22 for SSH).
  • Enough compute quota in the project for the size you choose.

Step by step

  1. Open the create form

    Go to Compute > Instances and choose Create instance.

    Screenshot — The Create instance button on the Instances page
    The Create instance button on the Instances page
  2. Name it and pick an image

    Give the instance a recognizable name, then choose an operating-system image (Ubuntu, Debian, Rocky, Windows, …) or one of your snapshots.

  3. Choose a size

    Select a flavor sized for your workload. You can resize later, so start small if unsure.

    Screenshot — The size (flavor) selection step showing CPU, memory and disk for each option
    The size (flavor) selection step showing CPU, memory and disk for each option
  4. Attach networking and a keypair
    • Select the network the instance joins.
    • Choose the SSH keypair to inject for login.
    • Assign a security group that opens the ports you need.
  5. Launch and wait

    Review the summary and launch. The instance moves from Build to Active within a minute or two.

    Screenshot — An instance transitioning to the Active state
    An instance transitioning to the Active state
  6. Connect

    Attach a floating IP for inbound access, then connect over SSH with your private key — or open the built-in browser console.

    Screenshot — The browser VNC console open on a running instance
    The browser VNC console open on a running instance

Examples

Connect over SSH
ssh -i ~/.ssh/id_rsa ubuntu@<floating-ip>
Create an instance with the CLI
patrii image list
patrii flavor list
patrii server create \
  --name web-1 \
  --image <image> \
  --flavor <flavor> \
  --network private-net \
  --key my-key \
  --security-group web-servers \
  --wait
Create an instance with Terraform
data "patrii_images" "ubuntu" {
  name_regex = "^Ubuntu"
}

data "patrii_flavors" "balanced" {
  category = "balanced"
}

resource "patrii_instance" "web" {
  name            = "web-1"
  flavor_id       = data.patrii_flavors.balanced.flavors[0].id
  image_id        = data.patrii_images.ubuntu.images[0].id
  key_name        = patrii_keypair.deploy.name
  security_groups = [patrii_security_group.web.id]

  network {
    uuid = patrii_network.app.id
  }
}

Limits & specifications

Actions you can run on an instance at any time:

ActionWhat it does
Start / StopPower the instance on or off; a stopped instance keeps its disk and IP.
RebootSoft or hard restart of the OS.
ResizeMove the instance to a larger or smaller flavor.
RescueBoot a temporary recovery environment to repair the disk.
RebuildReinstall from an image, keeping the same IP and volumes.
SnapshotCapture the instance as a reusable image or scheduled backup.
ConsoleOpen a browser VNC console when SSH is unavailable.

Best practices

  • Log in with SSH keys, never passwords; keep your private key safe.
  • Open only the ports you need, restricted to trusted sources.
  • Schedule snapshots so you can roll back a bad change or recover from failure.
  • Right-size: start small and resize up when metrics show you need it.
  • Use a separate project per environment to isolate blast radius.

FAQ

I can't connect over SSH.
Confirm the security group allows inbound TCP 22 from your address, the instance has a floating IP, and you're using the keypair selected at launch.
The instance is stuck in Build or Error.
Open the console log for the cause, then try a hard reboot. If it persists, rebuild from a known-good image or contact support.
Will I lose data if I stop the instance?
No. A stopped instance keeps its root disk, attached volumes and IP; you only release the running compute.
How do I move to a bigger size?
Use Resize from the instance's actions menu and pick a larger flavor; the instance reboots into the new size.

Learn more

Everything you can do here in the console is also available through the Patrii Cloud API for automation and scripting.

Was this article helpful?
Thank you for your feedback. Still stuck? Contact us