[superasn]

Thanks for this comment. I was about tell my team to investigate Vultr as an option for our next website, but I guess we'll first do some more research into this.

We're still on AWS too. Currently spending about $50 / site which adds up quite quickly when you have 20+ sites. Our current breakup is something like (2 x t2.micro - one for website, one for cron created using Elastic Beanstalk, 1 x db.t2.micro for RDS + Elastic load balancer cost). I'm sure we can bring it down to $10 / site if we were to move to Vultr or Scaleway but it's a very small site to pay for the reliability AWS has provided to us all these years (apart the recent S3 outage). So guess we'll too just stick to AWS for now until.

[jlgaddis]

Why not just get a couple of bigger instances and run all your sites on them?

[superasn]

There are many reasons but a few from the top of my head are:

1) The whole system is running on Amazon's Elastic Beanstalk (via Docker). Beanstalk provisions 3 instances for every site (1 Web, 1 Worker/cron, and 1 RDS) for every app with ELB on front.

2) It makes installing updates easy and automatic using deployment scripts which we have on every site.

3) Everything (web/cron/database) is configured to scale up and down automatically, i.e. new servers start as per demand. This may not be possible otherwise.

[jrowley]

dev ops is hard!