Hacker News Reader

Comment by tlrobinson | Hacker News Reader

"Flexible dyno hours" is some nice marketing spin. 550 hours a month works out to one application running 18 hours a day, whereas previously you could have an unlimited number of apps running up to 18 hours per day.

View on HN

But you get 1000 free hours? (if you give them credit card data)

If you just want one 24h-app + a bit that's better, if you can live with <=18h for all your apps it is worse.

Nice, now I can just put all my apps in one dyno, and I get free hosting. This is actually better for me. With SSL!

I think it's time to move away from Heroku or create multiple accounts to pool together "low usage" apps.

Before // After

18h for every app // 24h for one app

Yup, basically killing most free apps, sad times.

Hey, I am the PM for this project. It's not our intent to kill free apps. I love weekend hacks and small pet projects myself and Free dynos are still perfect for that. What we've found is that 1000 hours covered about 95% of the Free dyno usage on the platform. In most cases, if you have a bunch of Free apps, they're usually sleeping since they're not receiving traffic. I'd love to hear any additional feedback. You can reach me at brett@heroku.com.

I have many free apps as well as paid apps running. But I always used Heroku because I didn't have to worry about limitations unless a particular app has high volume. Now that it's become a monstrous burden, I'll definitely be moving most of my apps to a vps/DigitalOcean.

You just lost a huge number of free apps that could potentially become paid apps.

TLDR: Hassle of keeping track of account wide dyno use > hassle of running on vps

I am honestly curious how many of the "huge number of free apps" would actually become big paying apps. I suspect its quite a low number.

You'd be surprised. And at their rates for paid apps, even a single mid-low traffic paid app can run $xxx per month (incl. db).

Reply on news.ycombinator.com