Albeit restricted to only a few places worlwide compared to its peers in the cloud segment, I am yet to find another provider capable of delivering a score over 5000 (Geekbench) in a benchmark on a single CPU machine, and each machine costs $6 a month. For homelab and experienced users who don't need DBaaS or IaaC's, it's a pretty straightforward choice. A more comprehensive review of Vultr's HF machines can be found here.

Chose Hetnzer over DigitalOcean and Linode because Hetzner provides much cheaper VPS with much better specs. DigitalOcean might seems like a good choice at first because of how popular it is. But in reality, if all you need is a simple VPS, you won't benefit much from the their oversubscribed datacenters which often underperform other competitors. Linode is also a good choice. They have cheaper options and performs slightly better than DigitalOcean. In the end, choosing a more affordable host helps you save money. That's important when you're running a tight ship.

While Media Temple is more expensive than DigitalOcean, sometimes it is like comparing apples and oranges. DigitalOcean provides what is called Virtual Private Servers ( VPS ). While you seem to be on your own dedicated server, you are, in fact, sharing the same hardware with others.

If you need to be on your own dedicated server, or have other hardware requirements, you do not really have as many options with DigitalOcean. But with Media Temple, the skies the limit ( but so is potentially the cost ).

DigitalOcean was where I began; its USD5/month is extremely competitive and the overall experience as highly user-friendly.

However, their offerings were lacking and integrating with other resources I had on AWS was getting more costly (due to transfer costs on AWS). Eventually I moved the entire project off DO's Droplets and onto AWS's EC2.

One may initially find the cost (w/o free tier) and interface of AWS daunting however with good planning you can achieve highly cost-efficient systems with savings plans, spot instances, etcetera.

Do not dive into AWS head-first! Seriously, don't. Stand back and read pricing documentation thoroughly. You can, not to the fault of AWS, easily go way overbudget. Your first action upon getting your AWS account should be to set up billing alarms for estimated and current bill totals.