Yeah, I had been keeping my eye on render.com, but haven't been using it yet -- I just noticed the price changes, which can be pretty steep for a small project.

Yeah, I had been keeping my eye on render.com, but haven't been using it yet -- I just noticed the price changes, which can be pretty steep for a small project. I was curious if they had been discussed on HN yet. Now, I'm currently on heroku, and to be honest, the pricing of heroku is not a huge problem for me, although did seem a bit steep. (With a small/medium sized project for my small non-profit employer, I pay heroku somewhere between 8-10K a year -- kind of a lot for us, but less than sysadmin/devops, and peanuts for heroku). Render used to seem _incredibly_ lower-priced than heroku, which led some people to suggest that heroku was incredibly over-priced... but perhaps this pricing change shows that in fact render was kind of under-priced. It's hard to say exactly what my spend on render would be if I switched, as the metrics charged are different, and I haven't done the work to estimate. But I'd guess it's still a bit cheaper -- and honestly even if it were about the same, that would be fine... we're not looking to get off heroku because of price mostly, but because we don't trust heroku's future. I really don't love the per-developer pricing or the non-trivial bandwidth pricing though. I don't like being incentivized to have fewer developers with access to render. And for a small organization, having predictable pricing that doesn't go up if our bandwidth goes up (not entirely under our control) is huge, and something that heroku gives us... although I realize there are hardly any services that can give you unmetered bandwidth these days, it may just not be feasible. I would _rather_ have increased compute prices, that are more predictable and stable costs for us, instead of a per-developer or bandwidth increase.