The VPS market mostly competes on three axes: price, polish, and locations. DigitalOcean leads on polish at a typical-market price. Hetzner leads on price at decent polish. Vultr's spot is "more locations than either, at prices closer to DigitalOcean than to Hetzner." If geography matters to you — if you have users in Seoul, Mumbai, São Paulo, Sydney all at once and don't want all of them on the wrong side of the planet from your server — Vultr's footprint is the differentiator.
Concretely: Vultr has data centers in cities like Tokyo, Seoul, Singapore, Sydney, Melbourne, Mumbai, Bangalore, Tel Aviv, Stockholm, Madrid, São Paulo, Mexico City, Johannesburg. Some of these aren't on AWS, none are on DigitalOcean, and Hetzner's exactly five locations don't cover any of them. For a small global product, "small VPS in the right city" is sometimes worth more than "powerful VPS half a planet away."
This tutorial walks the Vultr purchase, which is shaped like DigitalOcean's (so most of the operational steps transfer), and points out the parts that are different — the marketplace images, the per-hour billing nuances, and the specific places it makes sense to pick Vultr over either of the other two.
What you'll learn
- Vultr's plan structure: Regular, High-Performance, High-Frequency
- Picking a data center for your audience
- SSH keys and server creation
- The Vultr Marketplace for one-click app installs
- When DigitalOcean or Hetzner is the better fit
Step 1: Pick a plan family
1
Three tiers, mostly pick the middle
Vultr's plan families:
- Cloud Compute (Regular Performance): Intel CPUs. Cheap entry tier at $2.50/month for 512MB. The $2.50 tier is genuinely small but exists; $5–6 gets you 1GB, which is enough for many small things.
- High-Performance (HP): Newer AMD EPYC CPUs, faster than Regular at the same price point. Pick this tier by default if available in your chosen region — it's where Vultr is most competitive.
- High-Frequency (HF): Optimized for single-thread performance (3.8+ GHz). For workloads that benefit from raw single-thread speed (older PHP apps, certain databases). Niche.
Cloud GPU plans exist too if you need them. Skip on first server.
Step 2: Pick a region
2
The reason to be here
Vultr lists every region with current capacity and feature availability. The notable ones not at other providers:
- Seoul, Tokyo, Osaka — Japan/Korea coverage.
- Mumbai, Bangalore, Delhi — three Indian cities (Hetzner has none).
- Sydney, Melbourne — Australian coverage.
- São Paulo, Mexico City — Latin America (US clouds typically have just São Paulo).
- Johannesburg — only African data center among the players in this guide.
If your users are in any of these markets, Vultr is often the only good choice in the indie-VPS tier. Cheaper than AWS in the same region; much closer to users than DigitalOcean.
Step 3: SSH key, image, create
3
Standard VPS creation
Add your SSH key under Account → SSH Keys (same key from your Mac you used for any other VPS). Then Deploy New Server:
- Server type: Cloud Compute (HP if available).
- Location: from Step 2.
- Image: Ubuntu 24.04 LTS, or one of the Marketplace images if you want a pre-installed stack (Docker, WordPress, etc.).
- Plan: the smallest tier you'll need — you can resize up later (down is harder).
- SSH Keys: the one you just added.
- Hostname: something memorable.
Click Deploy Now. The server is provisioned in 30–60 seconds.
Vultr Marketplace: the image picker has a "Marketplace Apps" tab with pre-built images (Docker, WordPress, GitLab, Plex, etc.). Useful if you want a one-click stack rather than installing from scratch. They're maintained by the community; check the last-updated date on the image before relying on it for production.
Step 4: SSH in, harden
4
Same as any VPS
The first-ten-minutes routine is identical to DigitalOcean or Hetzner:
ssh root@<server-ip>
apt update && apt upgrade -y
adduser deploy
usermod -aG sudo deploy
rsync --archive --chown=deploy:deploy ~/.ssh /home/deploy
ufw allow OpenSSH && ufw enable
# After verifying deploy user works: disable root SSH login
The OS is plain Ubuntu; every Linux tutorial that targets Ubuntu works without translation.
Step 5: Billing — by the hour, but the way
5
The "destroy doesn't always stop billing" trap
Vultr bills by the hour, like AWS. Destroying a server stops compute billing. But:
- Snapshots stored separately keep accruing storage fees after the source server is gone. Delete unwanted snapshots explicitly.
- Reserved IPs cost ~$3/month if you allocated one and detached it without releasing.
- Backup snapshots (if you enabled the auto-backup option) keep going on a separate clock.
Check the Billing page monthly. Vultr surfaces orphaned resources clearly — but only if you look.
Step 6: When to skip Vultr
6
Two honest cases
- You don't need exotic geography. If your users are in North America or Western Europe, DigitalOcean's polish and Hetzner's prices are each more compelling than Vultr's "in between."
- You want bleeding-edge docs and a strong tutorial ecosystem. Vultr's docs are fine; DO's are clearly better. The community on Stack Overflow is larger for DO too. If you'll spend lots of time Googling, that ecosystem matters.
Step 7: Point your domain
7
Standard A record
At your DNS provider: A record, name @ or app, value = your Vultr server's IPv4. See Connect your domain to a server. Within minutes, your name reaches Vultr.
Some niche features cost extra. IPv6 is free, but custom ISO uploads, BGP sessions, and reserved IPs all add small per-month costs that don't show up in the headline plan price. If you ramp up usage of these, check the bill before you assume nothing changed.
What's next