[seanwilson]

This highly depends on if your site is dynamic or static. If static, I would go with GitHub Pages or Netlify as they're free/cheap and easy to use. Static sites with this kind of hosting is also great in that they require practically zero maintenance.

If you have to run a dynamic site (less potential headaches if you avoid this), I would try to use something like Heroku. It's easily one of the simplest way to host a robust site that needs to scale without having to spend much time on admin and DevOps.

For the people recommending a VPS, DigitalOcean etc., you're talking about using a huge amount of your own time to make such a setup as robust, easy to use and low maintenance as Heroku. What about backups? Scripting server creation? Adding a load balancer and more servers? Security updates? Server security?

The more parts and scripts you have to put together yourself, the more things that can go wrong and the more time of yours it's going to consume. If you consider how much your own time is worth and how important your startup is to you, trying to save anything in the realm of $10 a month on a core part of your startup doesn't make any sense if this is going to cost you multiple hours of time a month.

[Lxr]

Honest question, what does Heroku offer over Elastic Beanstalk other than being more expensive? I switched to EB and it seems more flexible and a lot cheaper, and I haven't wasted hours on admin.

[seanwilson]

> Honest question, what does Heroku offer over Elastic Beanstalk other than being more expensive? I switched to EB and it seems more flexible and a lot cheaper, and I haven't wasted hours on admin.

I said "something like Heroku" and Elastic Beanstalk is similar.

[filp]

ElasticBeanstalk is a lot more flexible, since it's basically just a wrapper around existing AWS services.