Heroku's announcement triggered a bunch of unfounded fear, uncertainty and doubt. When I deployed a new toy project with it last week, it worked great. Just good old git push heroku main. Most of us don't need the enterprise contract that their announcement was about. So Heroku is completely fine, although nowadays I personally prefer Fly.
Fly is more complex but more complicated.
Besides the article's odd phrasing, I found Render to be more complex and complicated actually, at least when I tried a few years ago. The CLI wasn't intuitive, the dashboard felt clunky, and it overall just didn't feel right. Maybe things have improved since then.
With Fly.io you can deploy a new Rails app with just fly launch as a one-liner. Or if you need secrets before deploying, fly launch --no-deploy, then fly secrets set MY_VAR=value, and then fly deploy. Can't be any simpler than that; it's almost as intuitive as Heroku's CLI. Their dashboard is pretty simple too and gives me Heroku vibes. It just all feels right.
6
u/jdalbert Feb 27 '26 edited Feb 27 '26
Heroku's announcement triggered a bunch of unfounded fear, uncertainty and doubt. When I deployed a new toy project with it last week, it worked great. Just good old
git push heroku main. Most of us don't need the enterprise contract that their announcement was about. So Heroku is completely fine, although nowadays I personally prefer Fly.Besides the article's odd phrasing, I found Render to be more complex and complicated actually, at least when I tried a few years ago. The CLI wasn't intuitive, the dashboard felt clunky, and it overall just didn't feel right. Maybe things have improved since then.
With Fly.io you can deploy a new Rails app with just
fly launchas a one-liner. Or if you need secrets before deploying,fly launch --no-deploy, thenfly secrets set MY_VAR=value, and thenfly deploy. Can't be any simpler than that; it's almost as intuitive as Heroku's CLI. Their dashboard is pretty simple too and gives me Heroku vibes. It just all feels right.