Deploying without having to hire an extra person for DevOps, Just do a git push and your app is deployed this helps businesses to deliver new features to users faster with less resources.

Heroku makes it easy to deploy applications, and you can do it in many ways. either using their cli or syncing with the repo whether on Github or Gitlab. Another cool feature of Heroku is the ability to add any addons with a simple click, beyond this their documentation is well written and they have a free version that works well for small apps, another cool feature is the metrics and analytics on the traffic your site is getting.

There is no easy way of switching account, let's say you have a person account and a work account, also some errors are cryptic sometimes which makes it hard to debug what went wrong.

Wonderful developer / DevOps experience. In ~6 years of using the service we've hardly seen any issues attributable to Heroku itself (rather to AWS which they buiding their service on top of).

Very simple to deploy and configure. Allows developers to manage deployments and serverside configuration without the need for a dedicated DevOps team. Apart from just running applications their Heroku Postgres offering is rock-solid (and last I checked: the largest Postgres cloud deployment in the world).

- Support for 0 downtime deploys via "preboot" is too rudimentary. Preferably it would verify that the deployed code actually managed to boot before routing traffic. Also no built in support for canary deploys. - Could use more dyno types (ie. instance types) to fit more use-cases. However introducing more options would also complicate the product and business model so understandable that it's kept simple. - Somewhat overpriced. - For security focused enterprise organisations the lack of fine grained security settings might be an issue.

For what we use Heroku for, its very good. We were using Heroku as a proxy server and currently with Heroku Dynos for running our apps.

I think some of the issues we started seeing with Heroku did not have a lot to do with them but I think rather how software development was starting to go, for example we were deploying our API server on Heroku as a proxy and using other platforms for the frontend, but there has been some consolidation recently where a few other tools have started to feel easier to deploy and build on than Heroku.

I would say the ease of usage without much ambiguity is a catch for me. Have hosted a couple of web applications during the days of the free tier and also most recently but overall, it's a good experience.

Within the context of my usage, there's not much to like least about it.