Cloud VPS

1. 01Pick a plan. Six sizes, Nano, Solo, Pro, Ultra, Max and Ras, run from one vCPU to sixteen, each with its own RAM, SSD and bandwidth. Live figures are on the pricing page.
2. 02Pick an image. Ubuntu, Debian, Fedora, CentOS, Rocky Linux, AlmaLinux and openSUSE are available as server images, and several of them again as desktop images with a graphical environment.
3. 03Choose how to authenticate: add an SSH public key, or set a password.
4. 04Add extra SSD beyond the plan’s own disk if the workload needs it, up to 500 GB at 100 ETB per GB a month.
5. 05Attach a public IPv4 address if the server has to be reachable from the internet, at 300 ETB/mo.

Provisioning finishes in well under a minute.

• Start, stop and restart from the console.
• Resize to a larger or smaller plan, or change the extra storage. Billing follows the change.
• Rebuild to reinstall a fresh image on the same server. The address is kept and a new root password is issued.
• Delete to remove the server. Charging stops the moment it is gone.

Every server carries a live metrics view: CPU, memory, disk, in and out, and uptime. Nothing has to be installed inside the machine to get it.

• Take a backup by hand at any time, with an optional note saying why.
• Turn on automated backups, choosing the hour they run and how many days to keep.
• Restore from any completed backup in one action.
• Delete old backups once they stop being useful.

Servers can be grouped into projects, each with a name and an emoji, and moved between them as a setup grows.

A server is charged by the minute. The plan carries a monthly price, the hourly rate is worked out from it, and the minute rate from the hour, so a machine that ran for an afternoon costs an afternoon and never more than its month. Deleting it stops the charge at that minute.

Extra storage and a public IPv4 address are charged alongside the plan, at 100 ETB per GB a month and 300 ETB/mo, on the same per-minute basis.