Add resources to a custom VPS (vCPU, memory, disk)

The Resources card, on a custom VPS's overview, shows what your VPS has today (vCPU, memory, SSD system disk, SATA data disk) and, when our team has opened the feature for your account, lets you add to it yourself. Resources only go up: the card never offers less than the VPS has, and a disk is never made smaller.

Every technical and administrative contact sees the card. Prices (price now, price after, days left invoiced) are shown only to the contacts who see the billing (administrative or full access); a technical contact sees the sizes and what applies at once or at the restart, without any amount. Only contacts with administrative or full access can add resources, because it is billed.

Add resources

1. Open the VPS under Services, then the Resources card.
2. Drag the slider of each resource to grow. Each slider starts at the current size and goes no lower; its steps are those of your offer.
3. Read under each slider what will really happen (see below), then the price box:
   • Price now and Price after, per period;
   • what is due for the rest of the period already paid, for example « 10 days out of 30, invoiced X excl. tax once the resources are added ».
4. Type the VPS's name to confirm, then click Add the resources.

Nothing is billed before the resources are in place on the VPS. It usually takes seconds; when it takes longer, the card shows Resources being added and your billing contacts get a « Resources being added » e-mail. Once the resources are in place, the invoice of the days left goes out, with its payment link, and your billing contacts get the « Resources added » e-mail summing up what changes, the new price and what applies at once or at the restart.

If our platform cannot add the resources, nothing is billed: the price stays as it was, the card shows The last addition could not be done and our team is told. You may ask again later. When it fails after the automatic tries, your billing contacts get a « Resources not added » e-mail.

The price added is that of the grid your VPS was sold with: if our prices change later, your additions keep your unit prices.

What applies at once, and what waits for a restart

The card says, for each resource, what our platform can do without stopping your VPS. We never promise « no downtime » when it is not true.

• Memory: added at once on the systems we tested (Debian 12 and Debian 13). Otherwise, at the next restart.

• vCPU: added at once on a VPS installed with Debian 13. On a VPS installed with Debian 12 — including a Debian 12 later moved to Debian 13 by an upgrade in place — they apply at the next restart: the system the VPS was installed with is what counts. These vCPU are plugged in at once but stay inactive until the restart: restart the machine (from the portal or from inside the system). The card says which of the two applies to your VPS.

• System or data disk grown: the disk grows at once, but the partition and the filesystem keep their size. They grow at the next boot (cloud-init), or at once with:

  sudo growpart /dev/sda 1
  sudo resize2fs /dev/sda1
  

  (adapt the disk and partition: lsblk shows them; xfs_growfs / instead of resize2fs for an XFS filesystem).

• New SATA data disk: added raw, usually at once. Format and mount it before use: see the article "Using the data disk of my VPS".

The « Changes waiting for a restart » banner

What cannot apply while running waits for a restart. The card then shows Changes waiting for a restart until the VPS has been restarted from your client area.

• Click Restart now to apply, then type the VPS's name: our platform stops it and starts it again, and the changes apply. The VPS's services are cut for a minute or two.
• For memory, a disk or vCPU our platform keeps waiting, a restart started from inside the system (reboot over SSH) is not enough: it does not read the configuration again. Use the card's button, or Reboot in the Power card.
• vCPU plugged in and waiting (a VPS installed with Debian 12, the card says so) become active at the next restart of the machine: restart the machine (from the portal or from inside the system). After a restart from inside the system, the card may still show the banner: it goes at the next restart started from the portal.
• The button shows only to contacts allowed to control VMs.

When there is no room

A VPS stays on its physical server. When that server has no room for the size chosen, the card says so (« No room on this VPS's server ») and offers Ask our team instead: the request reaches our team, who move the VPS and then add the resources (see Asking for more resources for your VM). The same goes for sizes beyond what the card offers.

Good to know

• Five additions an hour at most. Each one is noted in your team's activity log.
• A VPS that is suspended, on trial or whose renewal is stopped gets no resources from the card. When an invoice is overdue, our team adds the resources once it is settled.
• To remove resources, write to us: the card does not do it, and what was invoiced is only cancelled by a credit note from our team.