An Update on Heroku
271–280 of 366 posts
Re: An Update on Heroku
#272I've been building Frost https://github.com/elitan/frost, open source and self-hosted. Same idea, git push to deploy, automatic SSL, custom domains, but on your own VPS. Docker-native, no vendor lock-in, no pricing surprises.
The angle that's a bit different: it's designed for AI coding agents. Simple config they write correctly, clear errors, no K8s complexity to hallucinate. You give your agent the install URL and it sets up the whole server.
Re: An Update on Heroku
#273Wow, I have to admit that I have not heard anyone in the past 2 years or so to be on Heroku so it makes sense. I think they handled it quite well knowing that there most likely have been a steady decline of users. Generally I would avoid promoting myself but in this situation I think it fits the topic. I'm co-founder of a Platform-as-a-Service based in Europe named Ploi Cloud [0]. We focus on web applications working…
is this linked with Ploi.io?
Re: An Update on Heroku
#274Earlier quoted context omitted.
This! It absolutely boggles my mind that nothing else exists to fill this spot. Fly and others offer varying degrees of easier-than-AWS hosting, but nobody offers true PaaS like Heroku, IMHO.
vercel goes a step further, and (when configured this way) allocates a new hostname (eg feature-branch-add-thingg.app.vercel.example.com) for new branches, to make testing even easier.
Re: An Update on Heroku
#275Earlier quoted context omitted.
If any Heroku customer is reading this and not immediately going "we need to move off Heroku ASAP" all future problems are their own fault.
Honestly if you're still using Heroku today it's because you haven't really caught up with what's going on around you
Re: An Update on Heroku
#276Earlier quoted context omitted.
I was working for Slicehost at the time, we were a tiny team working our butts off in a loft office in downtown St. Louis, with a few remote employees. To my understanding there was a runway-growth problem. Could the founders raise and spend (efficiently) enough money quickly enough to keep the business viable? It would be a big gamble and the alternatives were to shut down (no way!) or sell. So they sold. Rackspace…
All I can say is thank you. I learned to manage servers because of Slicehost and the articles on it back then. I remember being excited by the merger because well, Rackspace had such a fantastic reputation at the time. People still tell stories about their service. The Rackspace Cloud was just up against an absolute monster in AWS and never really became competitive.
Re: An Update on Heroku
#277Earlier quoted context omitted.
What's the best alternative?
If you like VPS, Hetzner with Dokploy. It works great, the UI has essentially all the features of Fly or Render that you'd use for deployment, like preview build URLs and environments.
What do you think about Caprover? https://github.com/caprover/caprover
Or uh.. Dokku https://github.com/dokku/dokku
Right now I am using Coolify but so far it has not been exactly reliable
Re: An Update on Heroku
#278As somebody whose first day working at Heroku was the day this acquisition closed, I think it’s mostly a misconception to blame Salesforce for Heroku’s stagnation and eventual irrelevance. Salesforce gave Heroku a ton of funding to build out a vision that was way ahead of its time. Docker didn’t even come out until 2013, AWS didn’t even have multiple regions when it was built. They mostly served as an investor and le…
It remains the greatest engineering team I've ever seen or had the pleasure to be a part of. I was only there from early 2011 to mid 2012 but what I took with me changed me as an engineer. The shear brilliance of the ideas and approaches...I was blessed to witness it. I don't think I can overstate it, though many will think this is all hyperbole. I didn't always agree with the decisions made and I was definitely ther…
> the greatest engineering team I've ever seen
How do these two things reconcile in your opinion? In my view , doing something quickly is the easy part , good engineering is only needed exactly when you want things to be maintainable and scalable, so the assertions above don’t really make much sense to me.
Re: An Update on Heroku
#279Re: An Update on Heroku
#280Earlier quoted context omitted.
How does render compare to fly.io? Does anyone has experience running production rails apps on these?
https://render.com/articles/render-vs-fly-io