I have no JavaScript, only HTML and CSS files and a few Clojure files which run the API.
It's hard to beat Netlify and Vercel for static content. They make it easy and you'll be up and running in seconds.
I know you said Clojure, but it's worth mentioning: if you do choose to make a JavaScript/TypeScript backend, Vercel + Next.js's API routes is a great option. With that combination you'll have a GitHub integrated CI/CD build (if you need it) and serverless functions behind a custom domain with SSL in minutes.
Or Netlify or Cloudflare Pages for static content. Both offer server less functions for a fee as well.
Used all of them and liked all of them
Digital Ocean is a bit better on UI but pricing wise Linode was the best (until they removed their lowest priced plans)
* Heroku -> Best choice for backend dev;
* Vercel -> Best choice for React/ NextJS dev;
* Digital Ocean -> Best for all small product;
* Netlify -> Best for Jamstack;
* Github -> Best choice for Portfolio of Dev.
Many domain hosting also has a web hosting service. Their offers are lucrative compared to AWS/ GCP/ Azure.
If your really want a VPS, they also provide an inexpensive fully managed VPS solution.
I got really tired of keeping the OS and patches up to date; I just want to get to coding. I also hate CPanel-based hosting.
I believe Pair.com is a good solution when you don't want an unmanaged VPS but you don't want to pay for Heroku et al either.
They're based in PA, though. So probably not the best if you're in the West coast.
New services are often free for testing, sometimes even afterwards (their S3 is still first 75GB free).
I love documentation and web UI of Digital Ocean, but find their pricing a bit to high for tiny projects. Linode is also amazing.
I appreciated the way they took the minimal action necessary that isolated the problem, instead of just nuking my entire account, and all its data, like I read that Digital Ocean did in a similar situation, only it wasn't an unimportant side project, it was someone's entire ongoing business. I have no affiliation with Linode except being a satisfied customer, but this experience this is why Linode is my first choice, all else being equal.
PaaS: heroku, render
I feel digital ocean gets out of your way. AWS especially feels like you are in an AWS rabbit hole for a lot of stuff. After spending an hour trying figuring out how to give a specific IAM user read write access to a bucket. I said fuck it and just decided not to use S3 to backup my Wordpress site
Vultr is all you'll need for inexpensive and reliable VMs. My experience with Vultr has been much better than Linode and DigitalOcean. RamNode is also great in terms of performance.
Been hearing good things about Render's unified cloud too. Worth checking out.
Check out Low End Box for other recommendations.
Pricing and specs are similar to DO, and bandwidth is good.
As for which host to choose, this was the advice I had got 10+ years back, and it still holds true:
1. Check how long they have been in business: You want to look for stability in a hosting company. Older hosts means they have a more stable business and more experience.
2. Check their reputation and support: Do they take their security seriously, have they ever been breached? How is their support - will they respond quickly to your needs?
3. Verify if they run their own data centres: Many small webhosting companies are resellers that just hire servers or instances from other larger providers and manage the software. Or some just resell a white label service while everything is managed by the larger host company.
4. Check if they "oversell": A server can serve only so many instances of a VPS or website. Many webhosting companies oversell the resources they have on the gamble that not all their clients will use the full resource they are buying. If you are running a business you don't want that kind of uncertainity when you expect to scale.
5. Check if they offer the tech you need: FreeBSD servers used to be really popular once, now Linux servers are the rage. Or you may prefer Windows for your .net app. Or even an Oracle DB (if you have money to burn unnecessarily). Or you may prefer a specific version of an OS / DB / software for a particular web app or SaaS you have developed. Different hosts offer different technology. Verify your requirement with the webhost before you commit to them.
Apart from these, other things one may want to consider - if you want "managed service" (where the hosting company manages your software - installation and updation of system software, monitoring your servers etc.) or "unmanaged services" (where you are the system and db admin and monitor and manage the server instance). Or if you want data centres in a particular geographical location. Or if they offer the kind of billing cycle you want and so on. You may also want to find out how generous they are when you hit the server limits of your paid plans - do they shut down your instance without warning, or do they allow an exception for the rare unexpected peak in traffic and resources when your website is slashdotted or appears on HN?
The usual US based hosts that were then highly recommended, based on these ideas, for small projects were:
- Pair (www.pair.com - one of the oldest competent small-to-medium webhosting companies)
- Rackspace (www.rackspace.com - medium-to-large).
- Linode (www.linode.com - came much later, but gained a lot of reputation with their affordable unmanaged VPS hosting services and the easy platform they offered to manage them.)
Having tried all 3, I still personally prefer and recommend Pair and Linode.
Later Digital Ocean (www.digitalocean.com) and Vultr (www.vultr.com) arrived on the scene with more competitive pricing and better hardware and tech than Linode (for a while). DigitalOcean is also good and seems to have gained a good reputation so far. Rackspace lost the interest of the hobbyist crowd when they started focusing more on corporate clients.
you can host static pages and your typical MVC app as separate apps. even database.
all very turnkey