1. Heroku is slipping into a maintenance‑only mode
The announcement is widely read as a signal that Salesforce will stop selling new enterprise contracts and will only keep the existing service running.
“Enterprise Account contracts will no longer be offered to new customers.” – Salesforce post
“They’re basically saying ‘we’re going to keep the lights on’ but not how.” – codegeek
2. The community is scrambling for alternatives
With Heroku’s future uncertain, developers are pointing to Render, Railway, Fly.io, and self‑hosted options as the next best choices.
“Render for front‑end apps. That’s my current go‑to.” – quentindanjou
“Railway for backend APIs.” – quentindanjou
“Fly.io are absolute G’s.” – mindwok
3. Corporate doublespeak is a major pain point
Many commenters feel the announcement is full of vague, jargon‑laden language that obscures the real change.
“This reads more like ‘we won’t deliberately turn the lights off… but they’re probably gonna break on their own eventually’.” – ceejayoz
“The post is full of corporate doublespeak.” – g8oz
4. A historical lens on Heroku’s rise and decline
The discussion is peppered with recollections of Heroku’s early glory, the 2010 Salesforce acquisition, and the subsequent loss of momentum.
“Heroku was acquired by Salesforce in 2010.” – simonw
“Heroku had its time but then stagnated heavily.” – sebiw
“Heroku pioneered the ‘git push deploy’ model.” – bgentry
5. Cost and pricing anxiety
Users lament the removal of the free tier, unpredictable pricing, and the perception that Heroku is now too expensive compared to newer PaaS options.
“Heroku’s free tier removal broke trust.” – anyfactor
“Heroku is expensive.” – ryantgtg
“Railway offers unlimited seats for paid plans.” – quentindanjou
These five themes capture the core concerns and reactions in the thread.