Skip to main content

Getting Started With Your Cloud Server: From Checkout to First Deploy

  • Wednesday, 10th June, 2026
  • 10:00am

New to NetVO cloud servers? Here is the complete path from placing your order to serving your first application — it takes about ten minutes.

1. Pick the right plan

For a personal project or small API, an Essential instance (shared x86 cores) is the sweet spot. Running production databases or latency-sensitive workloads? Choose a Fusion plan — its AMD EPYC™ cores are 100% dedicated to you, so there are no noisy neighbors. Container-native teams love our Arc ARM64 line: excellent performance per dollar and native ARM Docker images.

2. Checkout and provisioning

After payment is confirmed, provisioning is fully automated — your server is typically online in under 60 seconds. You will receive the IP address and root credentials in your welcome email, and can always find them in the client area under Services.

3. First login

ssh [email protected]

On first login, update the system and set the hostname:

apt update && apt full-upgrade -y
hostnamectl set-hostname app01.example.com

4. Harden before you build

Follow our post “10 Essential Steps to Secure a New Linux Server” — at minimum: create a sudo user, switch SSH to key auth, enable UFW and fail2ban. Five minutes well spent.

5. Deploy something

A quick example — static site with Caddy (automatic HTTPS):

apt install -y debian-keyring debian-archive-keyring apt-transport-https
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | gpg --dearmor -o /usr/share/keyrings/caddy.gpg
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' > /etc/apt/sources.list.d/caddy.list
apt update && apt install caddy -y

Point your domain's A record at the server IP, set your site in /etc/caddy/Caddyfile, and Caddy fetches a TLS certificate automatically.

6. Know your safety nets

  • Snapshots & backups are available on all cloud plans — enable them from the client area before you need them.
  • DDoS protection is already active; nothing to configure.
  • Upgrades are one click and prorated — start small, scale when traffic arrives.

Stuck at any step? Open a ticket — our engineers answer 24/7.

« Back