Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

An Update on Heroku

heroku.com

Post reply on HN
Print view View original

61–70 of 366 posts

Re: An Update on Heroku

#61

Post by PanMan »

culi wrote: post #40
PanMan wrote: post #35

It really surprises me there isn’t a modern heroku alternative that supports the same.. things. Like build pipelines, routing included, multiple worker types. AWS is way less batteries included. And none of the competitors seems to offer the same kind of service, last time I looked.

I think there's a couple decent alternatives out there: https://alternativeto.net/software/heroku/ There are also a lot of cool "self-hosted Heroku" alternatives - Coolify (PHP) (2020) https://github.com/coollabsio/coolify - Dokku (Go) (2013) https://github.com/dokku/dokku - Dokploy (TypeScript) (2024) https://github.com/Dokploy/dokploy - CapRover (TypeScript) (2017) https://github.com/caprover/caprover - Komodo (Rus…

Thanks for the reply! Most of these (also on the alternativeto) are self-hosted, which is different from having heroku do it. Also most only support webservers, while the majority of our servers aren't web..

Re: An Update on Heroku

#62

Post by sm123 »

an0malous wrote: post #37
dmathieu wrote: post #26

Earlier quoted context omitted.

It means: go elsewhere, they're dead.

What's the best alternative?

Build.io came out of this exact problem a few years ago (I joined in 25Q4) - trying to be what Heroku could have been if it had continued to evolve.

We offer the same default simplicity/speed, but with the ability to go deeper once teams hit scale, cost, or workflow limits. Plus a pricing model that stays understandable and improves as teams scale rather than punishing them for it.

Fair warning: the website is pretty light right now. It’s mostly a placeholder while we prep a broader push over the few months. Happy to answer questions here if helpful.

Re: An Update on Heroku

#63

Post by JamesSwift »

simonw wrote: post #10

"We know changes like this can raise questions, and we want to be clear about what this means for customers." Proceeds to not be clear about what this means for customers.

Holy crap is this underselling how poorly this announcement is structured. Not only does it not provide clarity, it words things in such a way that it just begs more questions. “There are no changes for now”....

Re: An Update on Heroku

#64

Post by actsasbuffoon »

syx wrote: post #47
an0malous wrote: post #37

Earlier quoted context omitted.

What's the best alternative?

Moved from heroku to fly.io three years ago and I don’t regret it, great platform occasionally goes down and requires a bit of attention but the support forum is great

I had an issue with one of my Sprites (Fly.io also runs sprites.dev) and the CEO responded to me personally in less than 10 minutes. They got it fixed quickly.

I was a free customer at the time. I pay for it happily now.

Re: An Update on Heroku

#65

Post by sm123 »

sebiw wrote: post #21
sc68cal wrote: post #18

Earlier quoted context omitted.

It's such a shame, because they had one of the best services out there. Being able to push via Git and end up with a running deployment was a killer feature. It may not have been the first (Elastic Beanstalk was way older but when it first came out it was Java only iirc, ick) but it was incredibly popular. Seeing them now chasing AI as a "me too" after being acquired by Salesforce just shows that huge companies will…

Yup, their Git Push Deployment was really a killer concept and a huge gateway for people just writing good apps not needing to care about infra and still being able to get a production-ready setup.

Couldn’t agree more. That “git push and you’re live” moment removed a huge amount of accidental complexity, and it’s been the guiding experience behind what we’re building at Build.io.

Re: An Update on Heroku

#66

Post by craigkerstiens »

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.

Re: An Update on Heroku

#68

Post by Daviey »

simonw wrote: post #10

"We know changes like this can raise questions, and we want to be clear about what this means for customers." Proceeds to not be clear about what this means for customers.

"sustaining engineering model"

ie, life support.. bit rot will set in, they are dead.

Re: An Update on Heroku

#69

Post by an0malous »

syx wrote: post #47
an0malous wrote: post #37

Earlier quoted context omitted.

What's the best alternative?

Moved from heroku to fly.io three years ago and I don’t regret it, great platform occasionally goes down and requires a bit of attention but the support forum is great

It didn't seem quite as fire-and-forget as doing `Heroku create` when I tried to use it 3-4 years ago, especially the database setup. Do you use their Postgres offering?

Re: An Update on Heroku

#70

Post by quentindanjou »

nop_slide wrote: post #33
quentindanjou wrote: post #14

Earlier quoted context omitted.

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.

why split, you could use railway and render for both front end and back end

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.

Post reply on HN