Possibly but particuarly on a small team there is a cost to operational complexity even if you're comfortable. If the team could be developing features but is d

Possibly but particuarly on a small team there is a cost to operational complexity even if you're comfortable. If the team could be developing features but is dealing with an infrastructure problem that could easily be dealt with via an abstraction layer then you still lose overall developer productivity. And Heroku was never a great solution once you reached a reasonable level of scale because it became expensive and your Heroku infrastructure became subject to unexpected issues in resource sharing within shared instances. Shared instances are a problem across all cloud providers but pure-AWS-sans-Heroku is easier and has more options to switch to private instances.