An Update on Heroku • Hacker News Board

Re: An Update on Heroku

#31

Post by bluedino » Fri, Feb 06, 2026, 4:09 PM UTC

Sad day. Was such an amazing product and gave a start to so many companies back then.

Re: An Update on Heroku

#32

Post by ProfessorZoom » Fri, Feb 06, 2026, 4:09 PM UTC

more like herok-who?

Re: An Update on Heroku

#33

Post by nop_slide » Fri, Feb 06, 2026, 4:11 PM UTC

quentindanjou wrote: post #14

slices wrote: post #2

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.

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

Re: An Update on Heroku

#34

Post by prodigycorp » Fri, Feb 06, 2026, 4:11 PM UTC

This may be the worst piece of corporate communication that I've ever seen.

Re: An Update on Heroku

#35

Post by PanMan » Fri, Feb 06, 2026, 4:11 PM UTC

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.

Re: An Update on Heroku

#36

Post by earless1 » Fri, Feb 06, 2026, 4:12 PM UTC

g8oz wrote: post #5

"transitioning to a sustaining engineering model". I don't care what anyone says, it takes real talent to come up with lines like this.

From a business perspective, this means they will not be investing in innovation on the platform anymore. Instead, they will focus their efforts on maintaining the current operations and keeping the lights on.

Re: An Update on Heroku

#37

Post by an0malous » Fri, Feb 06, 2026, 4:15 PM UTC

dmathieu wrote: post #26

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.

It means: go elsewhere, they're dead.

What's the best alternative?

Re: An Update on Heroku

#38

Post by CPLX » Fri, Feb 06, 2026, 4:17 PM UTC

BillinghamJ wrote: post #6

Seems strange not to just... say nothing and merely remove any mentions of an enterprise offering from the website. All this blog post can do is make people nervous and lead to customers moving elsewhere. Revenue will drop, and further compound their desire to not invest in the platform. What's the benefit/upside in publishing such an article?

I think they’d be happy if all the customers moved on. They just don’t want to upset enterprise customers.

Re: An Update on Heroku

#39

Post by Robdel12 » Fri, Feb 06, 2026, 4:18 PM UTC

Salesforce is the worst, lol

Re: An Update on Heroku

#40

Post by culi » Fri, Feb 06, 2026, 4:18 PM UTC

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 (Rust) (2022) https://github.com/moghtech/komodo