5 ms·
"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 fo
by simonw 9mo ago
"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.
- dmathieu 9mo agoIt means: go elsewhere, they're dead.
- an0malous 9mo agoWhat's the best alternative?
- syx 9mo agoMoved from heroku to fly.io three years ago and I don’t regret it, great platform occasionally goes down and requires a bit of attention but the support forum is great
- actsasbuffoon 9mo agoI had an issue with one of my Sprites (Fly.io also runs sprites.dev) and the CEO responded to me personally in less than 10 minutes. They got it fixed quickly. I was a free customer at the time. I pay for it happily now.
- an0malous 9mo agoIt didn't seem quite as fire-and-forget as doing `Heroku create` when I tried to use it 3-4 years ago, especially the database setup. Do you use their Postgres offering?
- syx 9mo agoNo my one is a simple ruby sinatra app with no DB. Yeah unfortunately it wasn’t super reliable as heroku but they’re getting better at keeping the instances up
- mindwok 9mo agoFly.io are absolute G’s. The product is awesome and the tech blogs they write are fantastic.
- sm123 9mo agoBuild.io came out of this exact problem a few years ago (I joined in 25Q4) - trying to be what Heroku could have been if it had continued to evolve. We offer the same default simplicity/speed, but with the ability to go deeper once teams hit scale, cost, or workflow limits. Plus a pricing model that stays understandable and improves as teams scale rather than punishing them for it. Fair warning: the website is pretty light right now. It’s mostly a placeholder while we prep a broader push over the few months. Happy to answer questions here if helpful.
- satvikpendem 9mo agoNot to be confused with builder.io, or worse, builder.ai
- llIIllIIllIIl 9mo agoDo you care to show prices? The true benefit of heroku for me was really predictable pricing model. Build.io website doesn’t have it on mobile site at all. I don’t want to look at demo, i want to hook up my credit card, set a monthly budget and explore
- runako 9mo agoFWIW it doesn't look like pricing or details of the service offerings are available on the desktop site, either.
- sm123 9mo agollIIllIIllIIl & runako give me an email on steven[at]build.io and I'll share. As mentioned, we stripped the site back while we overhaul and we certainly didn't expect this today!
- naniwaduni 9mo agoTo be clear, you just answered "Do you care to show prices?" with No.
- 9mo ago
- satvikpendem 9mo agoIf you like VPS, Hetzner with Dokploy. It works great, the UI has essentially all the features of Fly or Render that you'd use for deployment, like preview build URLs and environments.
- BoorishBears 9mo agoVery close to the worst alternative for people who actually need Heroku, but it won't stop people from plugging it to death and back.
- satvikpendem 9mo agoEh, no, depends on why you used Heroku in the first place. Way back when, I used it because the UI was dead simple and it Just Worked™. If I can replicate that with a VPS and have a good UI around it that takes care of everything, it's functionally the same to me.
- BoorishBears 9mo ago"Depends on what you used it for" applies to just about any platform. Realistically, self-hosting the PaaS defeats the purpose of a PaaS for the crowd Heroku was attracting.
- satvikpendem 9mo agoHeroku was one of the first to have that seamless UX, only after which others like Fly or Render or Railway came to copy it. I wager people were primarily attracted to that user experience and only minimally cared that it was fully hosted versus not, because there was also AWS at that time.
- BoorishBears 9mo agoHow do you think self-hosting affects that seamless UX they value.
- runako 9mo agoDigital Ocean App Engine has the easy setup and GUI management that made Heroku popular.
- moorow 9mo agoWe saw this coming (like most people) a while ago when Heroku started flaking without status updates, and moved part of our workload to Fly. We ended up moving off Fly as well (significant unreliability and just some very strange network load balancer issues that would cause us downtime) and went to Railway, and that's been fantastic so far. We've moved our whole workload onto it.
- deleted 9mo ago[deleted]
- bendangelo 9mo agoKamal works well
- patrickdavey 9mo agoKamal is basically self hosting though right? So you have to take care of keeping the underlying os patched etc. With heroku you only needed to think about git push.. ?
- JamesSwift 9mo agoHoly crap is this underselling how poorly this announcement is structured. Not only does it not provide clarity, it words things in such a way that it just begs more questions. “There are no changes for now”....
- Daviey 9mo ago"sustaining engineering model" ie, life support.. bit rot will set in, they are dead.
- teaearlgraycold 9mo ago> including helping organizations build and deploy enterprise-grade AI in a secure and trusted way. Baffling
- Macha 9mo agoIt saves face with investors to say you're shuttering a product to focus on the hot new thing as a strategic decision than to say you're shuttering it because your actions have led it to be unviable.
- le-mark 9mo agoReminds me of when blockchain was in literally everything. So the wheel turns.
- paxys 9mo agoIf any Heroku customer is reading this and not immediately going "we need to move off Heroku ASAP" all future problems are their own fault.
- toyg 9mo agoThat 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 9mo agoThe 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 9mo agoI 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.
- raverbashing 9mo agoHonestly if you're still using Heroku today it's because you haven't really caught up with what's going on around you
- nathanappere 9mo agoWhat's a better offering that makes it easier to push projects in production?
- altairprime 9mo agoAs a former enterprise person, this clearly states “exiting growth cycle into low-staffing maintenance mode”; Salesforce must have bought them to kill a price-beating competitor to multi-year Salesforce PaaS contracts, same as Okta did with Auth0. Investors are typically-majority short-sighted and only care about growth-cycle revenue, so once they reached market saturation, they were ripe and duly reaped. So long, Heroku.
- carefree-bob 9mo agoYou are saying the plan was to buy a "price-beating competitor", invest in them for 16 years, and then finally pull the rug out now?
- didgeoridoo 9mo agoReminds me of https://youtu.be/T2BY8zZ1CTM?si=XDroWqVD-pElN9si https://youtu.be/T2BY8zZ1CTM?si=XDroWqVD-pElN9si
- carefree-bob 9mo agothat was great!
- altairprime 9mo ago[flagged]
- altairprime 9mo agoThey’re not competition if you own them! Typepad continued for over a decade after it was purchased. Auth0 is still in maintenance mode afaik. It can last as long as revenue pays for the FTE to maintain it, or until corporate reallocated the FTE to higher revenue-per-FTE-hour opportunities.
- bigfatkitten 9mo agoAuth0 still has a ton of people working on it at Okta. If they’re facing execution problems, it’s not due to a lack of resources.
- naniwaduni 9mo agoOh, they're very clear, just not explicit.
- rchaud 9mo agoWhat's not to get? The product is being bumped down in terms of priority so they can focus on AI word salad solutions. They are waiting for enough customers to end their contracts before they discontinue the product altogether.
- conductr 9mo agoWas clear to me. If I was looking at using them, I wouldn’t. If I was already using them, I’d stop. They seem dedicated to supporting the slow extinction so it doesn’t have to be a fire drill exit, but how do you sleep at night knowing they’re playing with matches.
- ubertaco 9mo agoI worked at Pardot around the time Salesforce started using this same language in internal announcements about Pardot. Our Pardot leadership translated for us and provided the necessary context: Pardot is being killed. The plan was to start building the product that would replace it, stop selling new contracts, rename Pardot in the meantime so the change wouldn't be as noticeable, and in a timeline of "by 10 years from now" Pardot wouldn't exist anymore. This is Salesforce for "last call for the lifeboats, we're gonna capsize the boat."