← Back to context

Comment by paxys

21 days ago

If any Heroku customer is reading this and not immediately going "we need to move off Heroku ASAP" all future problems are their own fault.

11 comments

paxys

Reply
franciscop  21 days ago

I loved Heroku, but moved away a couple of years back. Tried 3 major "alternatives" (dokku, Render, Fly.io), and the big clouds, and the only thing that made me happy at the end was Coolify. I do keep Netlify for FE-only projects though.

oth001  20 days ago

I get what you're saying but the onus is (and should) definitely be on the company to inform customers - and there's many laws to that effect.

  • stackskipton  20 days ago

    What laws? As long as they fulfill Heroku fulfills the obligation in any contracts they have made, no law has been broken.

    If you are paying month to month and actually check the Terms of Services of those services, most of them can shut down instantly without notice as long as they stop billing you.

toyg  21 days ago

That has been the case for a very long time at this point, the Salesforce acquisition was a death knell. The only stuff i have left on Heroku are zombie projects I don't care about.

  • simonw  21 days ago

    The Salesforce acquisition closed in 2010, when Heroku was barely three years old.

    A whole lot of Heroku's best features shipped after they were acquired. They had a pretty good run under Salesforce for the first few years.

    It would be interesting to hear a full oral history of when and where things went wrong after that. I expect the original founders leaving was a major factor.

    • ameliaquining  21 days ago

      I think a lot of people are under the misconception that the Salesforce acquisition happened a lot later than it really did. In particular, I think people often implicitly date it to the late-2010s-ish period when Heroku's product emphasis got more visibly enterprisey, and in particular when it started putting integrations with Salesforce's other products front and center.