ojame

We've been on self service and we've been on enterprise contracts. In the last 2 years I believe we've cycled through about seven account managers. Heroku as a concept might not be dead, but if you release an incredibly empty announcement saying there's no new enterprise contracts and existing ones may be renewed, enterprise Heroku is absolutely dead and I'd suggest it means Heroku as the current product is dead too.

Any Heroku user that has been at the level of an enterprise user before, or who currently is, would be ringing alarm bells at the current situation. It doesn't matter about the internal good will of employees - if you have a blog post hanging your enterprise customers out to dry (ironically as enterprise customers we have received zero communication from Heroku about this) after a year of terrible stability - you're really doing a great job of killing the whole thing.

> Heroku remains an actively supported, production-ready platform, with an emphasis on maintaining quality and operational excellence

Anyone that has used Heroku for a while will know that it is far less reliable today than it has been at nearly any point in its history (it's the least reliable since its first year of existence, imo). There is very little "operational excellence" left as an organization. All you need to do is look at how they communicated (or extreme lack-thereof) a critical outage that lasted for hours last year[1]

As an organization, we've put up with terrible reliability over the last couple of years, and swallowed cost increases every renewal and we've always been committed. That's changed in the last few days - we've tried out Railway and Northflank, and we'll continue to try out a few other services until we find the one that fits. We're lucky, we have about 9 months left on our contract and that gives us enough time to move.

What the user you're replying to is saying the Bun acquisition looks silly as a dev tool for Node. However if you look at their binding work for services like s3[0], the LLM will be able to interact directly with cloud services directly (lower latency, tighter integration, simplified deployment).

The status page itself is either saying nothing is wrong, or points to an error page[0]. The incident itself[1] hasn't been updated, which is pretty frustrating.

We can't submit a support ticket because, well, it requires the authentication procedure as well.

We use worker queues, and the queues are getting blown out because heroku can't action anything. We're having our microservices yo-yo now, which suggests things are getting worse, now better.

I've always been a huge Heroku advocate, but the last 5 years have been death by a thousand cuts.

My experiences differ depending on the above, I've mostly use Render or an alternative for side projects now (just due to cost/forgettability). As a daily user of Heroku professionally - it's clear Heroku isn't a priority for Salesforce. Heroku has struggled to maintain any form of product development and, if anything, has become more unreliable over the last year or two.

As an add-on developer, my communication with Heroku has been fantastic. You can assume so because it's a direct revenue stream and feature expander - but my experience with other platforms isn't (iOS has slow/poor communication and docs, Chrome's extension support is non-existent and often not backwards compatible etc.). It's kind of re-ignited my love affair with Heroku, like it was pre-salesforce.

Overall I can't see us moving from Heroku unless costs demand us to - it's just too 'easy' to stay. Vendor lock in is real and I'm okay admitting that.