Top
Best
New

Posted by lstoll 7 hours ago

An Update on Heroku(www.heroku.com)
211 points | 163 comments
reactordev 1 minute ago|
[delayed]
chris_marino 41 minutes ago||
This news from Heroku does not come as any surprise to the people that were there (as I was). Lots of moving parts and second guessing (that I won't share), but one thing I will say is: Incentives matter.

The seeds of this outcome were planted years ago when sales comp plans changed. When a sales rep can hit their target by simply converting the way an existing customer gets billed, none of them look for new business. Don't need new leads. Don't need to win competitive deals. But finding new customers and losing opportunities are the only things that signal/drive innovation. But from a budgeting perspective, why increase investment in a product that already hits/exceeds their sales targets?

Over time sales targets get met, but the product doesn't advance. By the time all existing customers that can convert have converted, the product is no longer competitive. Like bankruptcy, it comes gradually, then suddenly.

itay-maman 10 minutes ago||
It took me several reads to distill their post to this one sentence: "Enterprise Account contracts will no longer be offered to new customers"

I'd be glad to stand corrected but AFAICT this is the only sentence that describes the change. All other say "nothing is changing in [some area]".

Trying to downplay something to that extent immediately raises suspicious that this something (the change) is much more profound that what is stated.

simonw 6 hours 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.

paxys 44 minutes 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.
naniwaduni 8 minutes ago|||
Oh, they're very clear, just not explicit.
altairprime 44 minutes ago|||
As 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.
Daviey 5 hours ago|||
"sustaining engineering model"

ie, life support.. bit rot will set in, they are dead.

dmathieu 6 hours ago|||
It means: go elsewhere, they're dead.
an0malous 6 hours ago||
What's the best alternative?
runako 14 minutes ago|||
Digital Ocean App Engine has the easy setup and GUI management that made Heroku popular.
satvikpendem 1 hour ago||||
If 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 49 minutes ago||
Very 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 47 minutes ago||
Eh, 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.
syx 6 hours ago||||
Moved 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 5 hours ago|||
I 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.

mindwok 58 minutes ago||||
Fly.io are absolute G’s. The product is awesome and the tech blogs they write are fantastic.
an0malous 5 hours ago|||
It 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?
sm123 5 hours ago|||
Build.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.

llIIllIIllIIl 1 hour ago|||
Do 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
sm123 2 minutes ago|||
llIIllIIllIIl & 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!
runako 15 minutes ago|||
FWIW it doesn't look like pricing or details of the service offerings are available on the desktop site, either.
satvikpendem 1 hour ago|||
Not to be confused with builder.io, or worse, builder.ai
JamesSwift 5 hours ago|||
Holy 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”....
teaearlgraycold 1 hour ago||
> including helping organizations build and deploy enterprise-grade AI in a secure and trusted way.

Baffling

Macha 21 minutes ago||
It 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.
bearjaws 2 hours ago||
The downfall of Heroku should be studied, they had lightning in a bottle and blew it.

Salesforce acquired them and just let it die, baffling.

codegeek 1 hour ago||
Nothing to study. A common scenario when a mega corp acquires an incredibly successful startup and then lets it die. Happens more often than not. This is why I chuckle when I see an acquisition and the founders claim "Nothing is changing. We are not going anywhere" . There may be exceptions but the moment a hugely successful company like heroku gets acquired, you know it's most likely game over. To their credit, they survived 15 years after acquisition but barely.
bmenrigh 47 minutes ago||
Often "nothing is changing" ends up being more literal than the founders realize or intend. Acquisitions by big companies tend to slow the development to a crawl as development bureaucracy takes over. When a great product is practically frozen in time it stops being great in 5-15 years as the rest of the world passes them by.
brightball 12 minutes ago||
Yea, this is accurate in my experience.
sleight42 1 hour ago|||
Often seems like there's no defeat that Benioff can't steal from the jaws of Victory.
brightball 1 hour ago|||
I remember feeling the same way about Slicehost back in the day after Rackspace acquired them. Loved Slicehost. Not too long after though, Digital Ocean appeared with everything I loved about Slicehost and has kept getting better ever since.

I feel like that's Fly.io now. They took all of the great things about Heroku but also dramatically improved and added new capabilities...while improving on pricing, particularly for lower traffic stuff. Love Fly.

nicoburns 27 minutes ago|||
> They took all of the great things about Heroku but also dramatically improved and added new capabilities

I also love Fly, but they were missing easy managed databases (which always seemed like the main reason to use Heroku to me). And now they have them they're very expensive (even compared to Heroku). Which is a shame because their compute is very cheap.

tptacek 6 minutes ago|||
If there was one thing we would all decide differently here at Fly.io, like if you gave us a time machine, is how we did databases. Someday Kurt and I will write the post about how those decisions came to pass and how they played out.

We're doing Managed Postgres now (MPG), which is what we should have done to begin with, but it took us for-ev-er to get here.

brightball 17 minutes ago|||
For what it's worth, I've been very happy using Crunchydata PostgreSQL with Fly.
prmph 19 minutes ago||||
Not sure why people love fly.io over all the other competitors so much. I myself prefer render.com, for the simplicity and predictability of their billing, and their deployment model is so intuitive
michaelsbradley 1 hour ago|||
I was working for Slicehost at the time, we were a tiny team working our butts off in a loft office in downtown St. Louis, with a few remote employees.

To my understanding there was a runway-growth problem. Could the founders raise and spend (efficiently) enough money quickly enough to keep the business viable? It would be a big gamble and the alternatives were to shut down (no way!) or sell. So they sold.

Rackspace wanted to take Matt’s and Jason’s know how (plus customer base) and go big, really big! That defocused our efforts a bit, plus there were corporate integration headaches (though not too bad). Eventually Linode, already a competitor, and later Digital Ocean filled the void.

brightball 1 hour ago||
All I can say is thank you. I learned to manage servers because of Slicehost and the articles on it back then.

I remember being excited by the merger because well, Rackspace had such a fantastic reputation at the time. People still tell stories about their service. The Rackspace Cloud was just up against an absolute monster in AWS and never really became competitive.

michaelsbradley 54 minutes ago||
Thank you for the kind words, brought back some fun and interesting memories. I spent a lot of time helping to write and edit those articles, as did my coworkers, glad they helped you!
o_m 1 hour ago|||
What is there to be studied? Once a company is acquired you bounce. There is usually a two year grace period before you start feeling the pain as a customer, which should give you the time to migrate.
anamexis 1 hour ago||
Salesforce acquired Heroku 15 years ago.
cpursley 41 minutes ago|||
And Heroku has stagnated for at least 13 of those years...
carimura 1 hour ago|||
Time flies. I do think the vision lasted pretty long post acquisition, maybe 5 years or so, but then the inevitable seemed... inevitable.
chimeracoder 1 hour ago|||
> Salesforce acquired them and just let it die, baffling.

This is a common misconception, but it's actually not true. The reality is even more bizarre.

Most of Heroku's successful years came after the acquisition, not before. Heroku was acquired extremely early in its lifecycle, and Salesforce does actually bear responsibility for investing in it and making it the powerhouse it became. Most of what people remember as the glory days of Heroku came long after the acquisition. And in fact, at the time of acquisiton, Heroku was nowhere near as competitive as a product as it later became.

It was only much later on that Salesforce began to pull the supports out from underneath it, leaving it to fall behind and become what it is today.

The narrative of "BigCo™ acquires startup, then leaves it to wither and die" is a trope because it is very commonly true, but it's actually not what happened in this particular case.

pjmlp 1 hour ago|||
It is a typical acquisition by the book, always goes the same way after three to five years.
OGEnthusiast 1 hour ago||
Downfall? The founders and VCs made tens of millions of dollars. That’s the success condition for them.
windowshopping 40 minutes ago||
This literally says nothing - are we supposed to infer that they are putting the product into maintenance mode and will no longer be developing new features for it? This is a masterpiece of corporate nullspeech.
shepherdjerred 38 minutes ago|
> with an emphasis on maintaining quality and operational excellence rather than introducing new features

it sounds pretty clear that it's in maintenance mode

dwaltrip 17 minutes ago||
It’s clear enough but they aren’t going out of their way to make it obvious. It’s definitely fluffed up / corporately sanitized.
g8oz 6 hours ago||
"transitioning to a sustaining engineering model". I don't care what anyone says, it takes real talent to come up with lines like this.
bityard 1 hour ago||
In a company I used to work for, "sustaining engineering" was the team of developers that handled all of the bugs and issues reported by customers on old-but-still-technically-supported versions of the products. (The ones who worked on current versions of the products where just "engineering.")

So basically heroku will fix whatever is broken, but don't expect any new features or development.

earless1 6 hours ago|||
From a business perspective, this means they will not be investing in innovation on the platform anymore. Instead, they will focus their efforts on maintaining the current operations and keeping the lights on.
paxys 39 minutes ago|||
Heroku has been running in this mode for a long time. The only difference is they made it official.
the_real_cher 1 hour ago||||
From a business perspective the have brought it out to the field with a shotgun.
awestroke 1 hour ago|||
As opposed to the relentless innovation they have demonstrated in the past 5+ years? /s
codegeek 1 hour ago|||
I am sure that the guy whose name is on the Post didn't even write this himself. Probably some corporate writer using LLM :).
slices 1 hour ago||
I would love to see the prompt that led to that word salad
throwoutway 5 hours ago|||
Could have just said we will Keep the Lights on
ceejayoz 3 hours ago||
This reads more like "we won't deliberately turn the lights off… but they're probably gonna break on their own eventually".
danudey 1 hour ago||
The lights will stay on until they burn out or the power goes off, or someone bumps the light switch or steals the light bulbs.
kenforthewin 6 hours ago|||
We've been optimizing for decades to engineer the bullshit-generating super-soldiers required to craft modern PR statements.
selimthegrim 6 hours ago|||
It's like PBS, they are going to beg for your money now with a sustaining engineering membership
sarreph 6 hours ago||
Surely it's a typo and they meant "sustainable"?

Otherwise IMO such an odd word choice. Definition:

>> providing physical or mental strength or support

shortsightedsid 6 hours ago|||
Sustaining is used in Engineering to mean that it's now post-GA and there is no further development. The platform is not End of Life but there are no more features planned.
sebiw 6 hours ago|||
Sustaining as in sustaining their shareholders.
collimarco 21 minutes ago||
I have moved all Rails apps away from Heroku in the last years. It was great 10 years ago, but then became expensive, full of bugs and with terrible support. All our Rails apps (Pushpad, Newsletter.page, etc) are running on Cuber gem + DigitalOcean Kubernetes... In the last years we achieved 100% uptime (five nines), zero subtle bugs and huge cost savings.
WildGreenLeave 2 hours ago||
Wow, I have to admit that I have not heard anyone in the past 2 years or so to be on Heroku so it makes sense. I think they handled it quite well knowing that there most likely have been a steady decline of users.

Generally I would avoid promoting myself but in this situation I think it fits the topic. I'm co-founder of a Platform-as-a-Service based in Europe named Ploi Cloud [0]. We focus on web applications working on NodeJS and PHP but would be open to other platforms if people need it. Heroku has always been a source of inspiration to me so if you are looking for an alternative and care about it having a strong European presence please check it out. (We do have a US location too!)

0: https://ploi.cloud

esher 27 minutes ago|
The original Heroku often gets praised here. Rightfully so. It inspired many. We started our PHP PaaS [0] 13 years, ago. Most of the others from that area are long gone. PagodaBox, CloudControl, PhpFog …

[0] https://www.fortrabbit.com

More comments...