We 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.
replydeleted
replyMoved 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
replyI 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.
replyI was a free customer at the time. I pay for it happily now.
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?
replyNo 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
replyFly.io are absolute G’s. The product is awesome and the tech blogs they write are fantastic.
replyKamal works well
replyIf 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.
replyVery close to the worst alternative for people who actually need Heroku, but it won't stop people from plugging it to death and back.
replyEh, 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.
reply"Depends on what you used it for" applies to just about any platform.
replyRealistically, self-hosting the PaaS defeats the purpose of a PaaS for the crowd Heroku was attracting.
Heroku 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.
replyHow do you think self-hosting affects that seamless UX they value.
replyAs I said, the correct software on top handles it all for you. I don't think you've actually tried Dokploy.
replyDokku is better. And neither is what Heroku's bread and butter customer needs.
replyBut alas, my interest in painstaking explaining why self-hosting is fundamentally incompatible with a product who's value prop was "nothing to install" is waning.
Have a good one.
You and I simply have different opinions on what Heroku's value proposition was, because, again, AWS was also right there and also was "nothing to install." Therefore Heroku was used primarily for its dead simple UX, something which is replicated even in a self-hosted environment, because, again, the value prop was never about PaaS or self-hosting, it was always about the user experience.
replyHave a good weekend.
Digital Ocean App Engine has the easy setup and GUI management that made Heroku popular.
replyBuild.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.
replyWe 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.
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
replyllIIllIIllIIl & 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!
replyTo be clear, you just answered "Do you care to show prices?" with No.
replyFWIW it doesn't look like pricing or details of the service offerings are available on the desktop site, either.
replyNot to be confused with builder.io, or worse, builder.ai
reply