An Update on Heroku • Hacker News Board

Re: An Update on Heroku

#21

Post by sebiw » Fri, Feb 06, 2026, 4:00 PM UTC

sc68cal wrote: post #18

sebiw wrote: post #8

> helping organizations build and deploy enterprise-grade AI in a secure and trusted way > Enterprise Account contracts will no longer be offered to new customers Seems contradictory or I just don't understand how they do product management. My opinion: Heroku had its time but then stagnated heavily in keeping up with what was going on around it. With the rise of Container as a Service platforms there now were a mult…

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.

Re: An Update on Heroku

#22

Post by jcytong » Fri, Feb 06, 2026, 4:00 PM UTC

[flagged]

Re: An Update on Heroku

#23

Post by nightpool » Fri, Feb 06, 2026, 4:01 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/when do you use Railway over Render?

Re: An Update on Heroku

#24

Post by sebiw » Fri, Feb 06, 2026, 4:01 PM UTC

dainiusse wrote: post #13

Was this written by llm?

Dogfooding their future products!

Re: An Update on Heroku

#25

Post by gdulli » Fri, Feb 06, 2026, 4:05 PM UTC

jcytong wrote: post #22

[flagged]

Why is this so cringe? That's not the typical way AI writing is bad.

Re: An Update on Heroku

#26

Post by dmathieu » Fri, Feb 06, 2026, 4:05 PM UTC

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.

Re: An Update on Heroku

#27

Post by easton » Fri, Feb 06, 2026, 4:05 PM UTC

I just got some Heroku socks like two months ago at an event, they must've killed it at the start of the year. Weird.

Re: An Update on Heroku

#28

Post by swader999 » Fri, Feb 06, 2026, 4:07 PM UTC

They will still raise prices when renewal time comes around.

Re: An Update on Heroku

#29

Post by SparkyMcUnicorn » Fri, Feb 06, 2026, 4:08 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?

> lead to customers moving elsewhere

Since they're no longer accepting new enterprise clients, maybe this is intentional.

Re: An Update on Heroku

#30

Post by petcat » Fri, Feb 06, 2026, 4:08 PM UTC

simonw wrote: post #7

I wonder how much money Salesforce would need to sell what's left of Heroku to a better steward.

My understanding is that Heroku is just an AWS reseller. I don't know if there's a lot of value in a PaaS piggy-backing on another PaaS anymore. Especially for Salesforce.