Top
Best
New

Posted by lstoll 12 hours ago

An Update on Heroku(www.heroku.com)
289 points | 218 commentspage 4
dluan 6 hours ago|
so EOL announcement without saying when it will be, but eventually.

we've been loyal heroku customers for over a decade. should have switched off long ago, but as a small team, it was too valuable. such a shame.

Lammy 2 hours ago||
Headline includes the term “update” == always bad news.
czhu12 11 hours ago||
I’ve been developing an open source Heroku alternative so we may never again be gouged for nice deployment pipelines.

https://canine.sh

It supports all the quality of life features like opening a shell via a cli, which I found was one of my favorite parts of Heroku (canine run —myproject /bin/bash)

Been fortunate enough to get a sponsorship from the Portainer folks, which allows me to maintain and develop full time!

davepeck 5 hours ago||
Watching their public roadmap to see what happens. Right now, it looks about the same as it has for a while: useful new features and expected maintenance, moving along at a reasonable if not blistering clip.

https://github.com/orgs/heroku/projects/130

nubg 6 hours ago||
Title should be updated to "Sunsetting Heroku".
slices 11 hours ago||
Just about to set up a new app to deploy to Heroku, but this does not seem promising. Render seems like the next logical move, but curious where others are looking for alternatives.
Tankenstein 11 hours ago||
I moved to render years ago and have been very happy with the decision. It feels like heroku, if it never got acquired by salesforce and kept improving.
quentindanjou 11 hours ago|||
Railway for backend APIs. Render for front-end apps. That's my current go-to.

Although I would consider, _when possible_, using Vercel or Netlify.

nightpool 11 hours ago|||
Why/when do you use Railway over Render?
quentindanjou 9 hours ago||
When bandwidth matters, when you don't want to over or under provision, when you need multiple seats: if you make a project with a small team, Render is going to be quite expensive because of the cost of each seat while Railway offers unlimited seats for they paid plans. Just the whole pricing is different, I found myself more leaning into Railway when doing calculations.
nop_slide 11 hours ago|||
why split, you could use railway and render for both front end and back end
quentindanjou 9 hours ago||
Sorry, I wasn't saying you should split, I wanted to say that depending on what type of apps you are more leaning into one makes a bit more sense than the other. Render with their own CDN is quite good for frontend apps. In comparison, the whole config and auto scalling/provisioning of Railway makes it easier for backend app.

Of course you can do both with both of these services.

hboon 11 hours ago|||
Yes, Render if you want something similar.
guzik 11 hours ago||
yes,, render feels like the most natural next step right now (similar mental model). Still kind of nostalgic about Heroku, had really good times with it.
craigkerstiens 9 hours ago||
It sounds like there were pretty broad layoffs which impacted a lot more than just a focus on enterprise contracts. It wasn't "just" a few enterprise sales people. Engineering may have indeed been the least impacted, but this sounds like biggest round of layoffs to hit Heroku since its inception, not just some right sizing from over hiring.
xnx 11 hours ago||
Not at all surprising, but a real shame. Nothing that I know of has come close to the ease of the "Deploy to Heroku" button.
aristofun 4 hours ago||
Who cares about heroku in 2026? It’s a dead horse
diqi 4 hours ago|
What does this even say?
More comments...