Usually, companies migrate from Heroku to cut the cost as they grow, but there are other reasons too:
- The recent Heroku outages.
- Lack of flexibility to adjust the available CPU, as Heroku offers six basic dyno types. As a result when the company grows they need to deal with overhears.
- Heroku runs its servers on AWS, however, developers do not have access or control over the regions. This is an issue for the companies that deal with data requirements.
- It does not offer support for crons/jobs.
- Heroku default environment does not offer static IPs. (Private Spaces are only available on the Heroku Enterprise subscription.)
Have a look at cloud66.com, it creates an environment like Heroku but on your servers on any cloud. This creates many benefits, including persistent storage and support for all available regions of your cloud provider of choice. But it also makes a big difference in availability: your application is not dependent on Cloud 66’s availability and won’t go down. Disclaimer:I work at Cloud 66.
- The recent Heroku outages. - Lack of flexibility to adjust the available CPU, as Heroku offers six basic dyno types. As a result when the company grows they need to deal with overhears. - Heroku runs its servers on AWS, however, developers do not have access or control over the regions. This is an issue for the companies that deal with data requirements. - It does not offer support for crons/jobs. - Heroku default environment does not offer static IPs. (Private Spaces are only available on the Heroku Enterprise subscription.)
Have a look at cloud66.com, it creates an environment like Heroku but on your servers on any cloud. This creates many benefits, including persistent storage and support for all available regions of your cloud provider of choice. But it also makes a big difference in availability: your application is not dependent on Cloud 66’s availability and won’t go down. Disclaimer:I work at Cloud 66.