Ask HN: Are you leaving Heroku?

It seems like Heroku has been dying on a vine. The platform is still incredible and unmatched in Developer Experience, but recent security incidents (along with a severely prolonged resolution), downtime, and (just yesterday) a DNS-related issue is making me reconsider and quite possibly will move some mission-critical apps to AWS.

Are you migrating away from Heroku? If so, which cloud provider are you using (AWS, Google Cloud, Azure, etc)? What's your stack and what service are you migrating to (ECS, Elastic Beanstalk, etc)?

3 years ago, I tried Heroku and was quite impressed by it. Although the price is prohibitive for a hobby project that needed resources but wasn't generating any revenue, I had to start seeking other options.

Ended up developing my own Heroku but focused on Django deployments.

Three years later, it works like a charm and has many happy folks who thank me for making it.

Meet Appliku: https://appliku.com

I was pretty unhappy with the outage last night. All the user blogs for https://bearblog.dev went down for about an hour and a half (and I had so many emails to respond to this morning).

I'm looking to move Bear over to either a Digital Ocean droplet (I have the staging server running on one with SQlite and Litestream running, and believe it could actually scale well), or to Fly.io (to be seen).

Short answer: no.

Every year I try out new things (fly, render), but stick with heroku because I'd rather focus on building products and not devops.

I'm a solo dev making $700k a year on my projects. I'm happy to pay the extra cost for things to just work.

If there is a catastrophic issue though, I do have backups elsewhere that I will use.

Honestly you should checkout open source + self-host alternatives like porter (https://github.com/porter-dev/porter). I tried it in a project before and the developer experience was surprisingly good.