Skip to content
Vexelia
Contact us

Get a VPS running

From a new account to your first SSH login.

Built, not open to the public yet

This feature is built and has been tested against simulated hosts and a test database. It has not yet been proven on real hardware, and nothing here can be ordered today.

Not there yet

  • The first public region and its image list are not published yet.

Before launch. The panel is not open to the public yet, so you cannot follow these steps today. They describe the flow as it will work at launch.

1. Create an account and verify your email

Register with your email address and a password. We email you a link to verify the address. You can add an authenticator app or a passkey under Account, Security, and you should.

2. Add an SSH key

Add the public key you sign in with under SSH keys. The create page needs at least one key: keys are installed for root.

3. Add credit, or use a card

Vexelia is prepaid. Under Billing, Add funds, put credit on your account. Credit is used first; any rest is charged to your card. See Billing, invoices and tax.

4. Create the server

The create page is one page. Choose, in order:

  1. Location. Closer to your users means lower latency.
  2. Image. The system installed on the disk.
  3. Type. vCPU, memory and disk. The price is shown before you order.
  4. Networking. Every server gets a public IPv4 and IPv6 address, both included.
  5. SSH keys. Pick the keys to install.
  6. User-data. Optional. A #cloud-config document or a script that runs once as root on first boot.
  7. Name. Lowercase letters, digits and hyphens. It becomes the hostname.

The summary shows the price, how much comes from your credit and what is due now. When you confirm, the panel shows the setup steps until the server is ready. If a card needs 3-D Secure, you confirm it with your bank first.

5. Sign in

ssh root@YOUR_SERVER_IP

If SSH does not work, open the browser console from the server page. It reaches the server without the network. From the same page you can start, stop and restart the server, boot a rescue system, or rebuild it onto another image. A rebuild erases the disk.

Next