I've been running an extremely low-traffic, low-resource site on Heroku for the past few years. I use a paid hobby web dyno ($7/month) and a $9/month Postgres 'instance', but leverage the free Redis tier for use as a session store.
Generally speaking, Heroku provides a pretty simple, seamless platform to build on. There are much more cost-effective options I could've used for the $16/month I'm throwing at Heroku, but it's provided me the sort of experience I'm after and runs the stack without a whole lot of fuss on my side. Heroku pretty much invented the git-push-to-deploy workflow and that makes for pretty seamless DX.
With my personal GitHub account attached to my employer's organization though, and after Heroku's recent breach, the push-to-deploy magic's gone. I can't re-connect my GitHub account without also giving Heroku the keys to my employer's kingdom (is this intentional, Heroku?), and with no free Redis tier, I'm looking at a $31/month bill for what I could retool to run on a couple Lambdas and DynamoDB for less than a buck a month. As thorny as CodePipeline is, it'll get me back to the push-to-deploy workflow I was previously enjoying on Heroku. Or I can get over to Fly.io and pay...nothing?
I'm no big fish for Heroku, and despite their numerous 'hobby' plans I realize I'm not their core demo, but it'd sure be nice to have a real explanation as to this move.
Generally speaking, Heroku provides a pretty simple, seamless platform to build on. There are much more cost-effective options I could've used for the $16/month I'm throwing at Heroku, but it's provided me the sort of experience I'm after and runs the stack without a whole lot of fuss on my side. Heroku pretty much invented the git-push-to-deploy workflow and that makes for pretty seamless DX.
With my personal GitHub account attached to my employer's organization though, and after Heroku's recent breach, the push-to-deploy magic's gone. I can't re-connect my GitHub account without also giving Heroku the keys to my employer's kingdom (is this intentional, Heroku?), and with no free Redis tier, I'm looking at a $31/month bill for what I could retool to run on a couple Lambdas and DynamoDB for less than a buck a month. As thorny as CodePipeline is, it'll get me back to the push-to-deploy workflow I was previously enjoying on Heroku. Or I can get over to Fly.io and pay...nothing?
I'm no big fish for Heroku, and despite their numerous 'hobby' plans I realize I'm not their core demo, but it'd sure be nice to have a real explanation as to this move.