Netlify do everything that I had used Heroku for, for free.
In nearly one click too, instead of a dozen levers.
Why companies move off Heroku (besides the cost)
21–30 of 230 posts
Re: Why companies move off Heroku (besides the cost)
#22Other than Dokku how many other PaaS solutions can be run on your own hardware?
Re: Why companies move off Heroku (besides the cost)
#23Alternatives to Heroku besides Porter?
Fly.io and Render have been pretty impressive to use on personal projects.
Re: Why companies move off Heroku (besides the cost)
#24One thing this article is missing is the arbitrary "400MB slug size" that heroku limits your application to if you want to deploy.
Re: Why companies move off Heroku (besides the cost)
#25I don't know if I'm seeing things, but Heroku seems to be more expensive than GCP.
I get a 8 GB RAM Postgres instance for 200$ on Heroku. On GCP I get a 4CPU 26GB RAM Postgres instance for 280$ (Cloud SQL).
What's the USP Heroku provides?
Re: Why companies move off Heroku (besides the cost)
#26I'm historically a huge Heroku defender. Been using it for a decade now, and my company still uses it despite being quite large and getting a lot of traffic. It's always been a great product and the early Salesforce days they DID ship a ton of new stuff and improve rapidly (despite a narrative that they didn't). Like, it got REALLY GOOD the years after acquisition. That being said... it's insane that we haven't been…
> we haven't been able to deploy for over two weeks
What is stopping you? Are you unable to type `git push heroku master`?
Re: Why companies move off Heroku (besides the cost)
#27Small nit: I believe this is incorrect:
> More recently, all Git-based deployments (which is to say, virtually all deployments) to Heroku were blocked and review apps were halted for all users as a result of a GitHub OAuth token leak.
It should read "all GitHub-based deployments". You can still deploy with `git push heroku main`.
Re: Why companies move off Heroku (besides the cost)
#28As someone that was there at Heroku after the acquisition, I don't think you can state that since the acquisition it's been consistently downhill. There isn't much debate that things have stagnated in the last 5-7 years which is a longer story on why probably. Some examples of innovation that happened and were launched after the acquisition: buildpacks (at the time of acquisition Heroku was still Ruby only), Heroku P…
https://render.com is my favorite in this space
Care to explain why you like these choices?
Re: Why companies move off Heroku (besides the cost)
#29Small nit: I believe this is incorrect: > More recently, all Git-based deployments (which is to say, virtually all deployments) to Heroku were blocked and review apps were halted for all users as a result of a GitHub OAuth token leak. It should read "all GitHub -based deployments". You can still deploy with `git push heroku main`.
Ah yup good catch - just updated the article
Re: Why companies move off Heroku (besides the cost)
#30Other than Dokku how many other PaaS solutions can be run on your own hardware?
- piku https://github.com/piku/piku
- caprover https://caprover.com/