Live data from Hacker News

An Update on Heroku

heroku.com

351–360 of 366 posts

Re: An Update on Heroku

#351
I work at Encore so I'm biased.

We've had a bunch of people migrate over from Heroku in the last couple years, especially after they killed the free tier.

The main difference from other alternatives is that you don't write any infrastructure config - you just declare what you need in your code (databases, cron jobs, pubsub, etc) and Encore handles provisioning it in your AWS/GCP account (works locally as well where local is 1:1 to your prod env). So there's no Terraform to maintain or Docker setup to mess with.

If you're looking to move off Heroku it's pretty straightforward, most folks get their app running in an afternoon. Happy to help if you run into anything: https://encore.cloud

Re: An Update on Heroku

#352

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.

Any write up on this?

Re: An Update on Heroku

#353
post #239
post #231

Earlier quoted context omitted.

Digital Ocean is run into the ground? I've been with them for a long time and recently just launched new stuff. Still a pretty nice experience and a pretty decent price.

Yes, they haven’t updated their infrastructure in a long time. Pricing hence isn’t competitive. With each new generation they fall behind.

Maybe? I could see that happening.

I could also see them being compared with companies still using venture capital to give stuff away for free. In that case, I'm OK with that tradeoff. I'm not really excited about changing my infrastructure every few years to keep getting a free lunch.

The Digital Ocean app platform I recently migrated to is a lot newer than the "rent a VPS" model that they've had forever. Yes, it's not free like the Vercel and Cloudflare Workers I've also used recently. But it also doesn't force my app into a weird shape or to use their preferred language.

On a continuum where AWS sits at one boring+expensive end of the spectrum, and all the subsidized-pricing "we might not be here tomorrow" PaaSes sit at the other, I like the in-between spot where DO sits.

Re: An Update on Heroku

#354

Earlier quoted context omitted.

What's a better offering that makes it easier to push projects in production?

In 2026, every major cloud provider has a service that lets you just hand it a Docker container and let it figure out how to run it.

[dead]

Re: An Update on Heroku

#355

Earlier quoted context omitted.

You 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?

They’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.

Auth0 is constantly releasing new features, including a new major offering now for AI agents. Plus is still very active in the development community, with open source like OpenFGA, frameworks, contributions to standards and so much more.

Not sure where the maintenance mode is coming from...

Re: An Update on Heroku

#358
post #353
post #239

Earlier quoted context omitted.

Yes, they haven’t updated their infrastructure in a long time. Pricing hence isn’t competitive. With each new generation they fall behind.

Maybe? I could see that happening. I could also see them being compared with companies still using venture capital to give stuff away for free. In that case, I'm OK with that tradeoff. I'm not really excited about changing my infrastructure every few years to keep getting a free lunch. The Digital Ocean app platform I recently migrated to is a lot newer than the "rent a VPS" model that they've had forever. Yes, it's…

> Maybe? I could see that happening.

It already is. Besides dedicated options (which are just as expensive) - those shared cores are so old the performance compared to current line AWS models is so far out that it isn't competitive.

> I could also see them being compared with companies still using venture capital to give stuff away for free. In that case, I'm OK with that tradeoff.

That's not the point. They are more expensive compared to hyperscalers.

Re: An Update on Heroku

#359

Seems strange not to just... say nothing and merely remove any mentions of an enterprise offering from the website. All this blog post can do is make people nervous and lead to customers moving elsewhere. Revenue will drop, and further compound their desire to not invest in the platform. What's the benefit/upside in publishing such an article?

> lead to customers moving elsewhere Since they're no longer accepting new enterprise clients, maybe this is intentional.

Then why mince words, and why accept new non-enterprise clients - just be clear it's maintenance-only and existing customer-only.

Re: An Update on Heroku

#360
post #278

Earlier quoted context omitted.

It remains the greatest engineering team I've ever seen or had the pleasure to be a part of. I was only there from early 2011 to mid 2012 but what I took with me changed me as an engineer. The shear brilliance of the ideas and approaches...I was blessed to witness it. I don't think I can overstate it, though many will think this is all hyperbole. I didn't always agree with the decisions made and I was definitely ther…

> by 2012 we were drowning in tech debt and scaling challenges. > the greatest engineering team I've ever seen How do these two things reconcile in your opinion? In my view , doing something quickly is the easy part , good engineering is only needed exactly when you want things to be maintainable and scalable, so the assertions above don’t really make much sense to me.

An organization without “tech debt” is not good at prioritizing.
Post reply on HN