i am impressed. no ai can ever write announements this bad
An Update on Heroku
51–60 of 366 posts
Re: An Update on Heroku
#52For those not as well-versed in corporate PR....Salesforce are going to do just the bare minimum to keep the service going until the revenue dries up (or some > 0 $$ threshold where it just doesn't financially make sense to keep it running).
Pour one out for Heroku as they were truly a revelation back in the day and one of the most magical experiences ever on first run.
Re: An Update on Heroku
#53I’ve been developing an open source Heroku alternative so we may never again be gouged for nice deployment pipelines.
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!
Re: An Update on Heroku
#54It 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…
Literally nobody who seriously uses Heroku wants to self-host their own Heroku.
Re: An Update on Heroku
#55This is such a weird press release that totally obscures what it's trying to say. Just use clear and concise language and treat your customers like adults.
Re: An Update on Heroku
#56It 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 overhiring.
Re: An Update on Heroku
#57"transitioning to a sustaining engineering model". I don't care what anyone says, it takes real talent to come up with lines like this.
Could have just said we will Keep the Lights on
Re: An Update on Heroku
#58Earlier quoted context omitted.
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…
Literally nobody who seriously uses Heroku wants to self-host their own Heroku.
We had an enterprise account on Heroku. We invested a little in Dokku and moved to self host it as of a few months ago.
We now have a kubernetes (k3s) backed Dokku self hosted on Hetzner. Significantly cheaper but pretty robust.
Just saying that it's not literally, but you are right, most people wouldn't be interested in self hosting.
Re: An Update on Heroku
#59It's a bit surprising, one would have thought that with the event of accessible coding through agents, such site deployment sites would prosper.
Re: An Update on Heroku
#60Heroku (YC W08) was acquired by Salesforce all the way back in 2010 [0], a little over 15 years ago. A lot of people forget that, and assume the acquisition was somewhat recent.
Pretty illuminating reading the thread from 2010, it was big news at the time.