4 ms·

New Heroku Pricing

20 points by colinbartlett 12y ago

akerl_ 12y ago
It seems like the short version is that they're removing the ability to run a small app 24/7 on a single free dyno. Maybe the right decision for them in the long term, but it definitely means I'll be migrating away from Heroku for apps I would have otherwise kept there at the free tier and potentially scaled up there in the future. Any word yet on if existing apps will be grandfathered into their existing pricing model?
- grandalf 12y ago
  > removing the ability to run a small app 24/7 on a single free dyno This is correct. The first step was removing varnish (which happened a few years ago). Now, Heroku is hoping to get $7/month from many of the freeloaders. I highly doubt this would make sense if Heroku planned to grandfather anyone.
  - thinkbohemian 12y ago
    > The first step was removing varnish This was removed for architectural reasons. It brought a lot of downtime to the platform and didn't help speed all that much. It's better and faster to cache this type of content with a CDN anyway.
jonaldomo 12y ago
https://devcenter.heroku.com/articles/usage-and-billing#750-free-dyno-hours-per-app https://devcenter.heroku.com/articles/usage-and-billing#750-...
jscheel 12y ago
Is this a reliable source?
- colinbartlett 12y ago
  I am OP and it was sent to many people, including myself, in an email from Heroku. Here's a screenshot from their site (which requires login): http://i.imgur.com/PdZT3JQ.png http://i.imgur.com/PdZT3JQ.png
  - jscheel 12y ago
    Thanks OP, I appreciate the verification!
Brushfire 12y ago
I'm not surprised - I know of at least 3 companies that were abusing the free tier -- running thousands or 10s of thousands of simultaneous dynos on free and keeping them awake. Honestly, its kind of amazing they let it go on this long.
- ceejayoz 12y ago
  Won't they just run twice as many for half-days each?
yeasayer 12y ago
Really sad news. Now I have to change the pinging strategy to prevent idling and choose which 12 hours part of the day my app should be available. Probably will migrate my apps to AWS Beanstalk or OpenShift.
bbody 12y ago
Off to AWS for me.

20 points by colinbartlett 12y ago

It seems like the short version is that they're removing the ability to run a small app 24/7 on a single free dyno. Maybe the right decision for them in the long term, but it definitely means I'll be migrating away from Heroku for apps I would have otherwise kept there at the free tier and potentially scaled up there in the future. Any word yet on if existing apps will be grandfathered into their existing pricing model?

grandalf 12y ago
> removing the ability to run a small app 24/7 on a single free dyno This is correct. The first step was removing varnish (which happened a few years ago). Now, Heroku is hoping to get $7/month from many of the freeloaders. I highly doubt this would make sense if Heroku planned to grandfather anyone.
- thinkbohemian 12y ago
  > The first step was removing varnish This was removed for architectural reasons. It brought a lot of downtime to the platform and didn't help speed all that much. It's better and faster to cache this type of content with a CDN anyway.

jonaldomo 12y ago

https://devcenter.heroku.com/articles/usage-and-billing#750-free-dyno-hours-per-app https://devcenter.heroku.com/articles/usage-and-billing#750-...

jscheel 12y ago

Is this a reliable source?

colinbartlett 12y ago
I am OP and it was sent to many people, including myself, in an email from Heroku. Here's a screenshot from their site (which requires login): http://i.imgur.com/PdZT3JQ.png http://i.imgur.com/PdZT3JQ.png
- jscheel 12y ago
  Thanks OP, I appreciate the verification!

Brushfire 12y ago

I'm not surprised - I know of at least 3 companies that were abusing the free tier -- running thousands or 10s of thousands of simultaneous dynos on free and keeping them awake. Honestly, its kind of amazing they let it go on this long.

ceejayoz 12y ago
Won't they just run twice as many for half-days each?

yeasayer 12y ago

Really sad news. Now I have to change the pinging strategy to prevent idling and choose which 12 hours part of the day my app should be available. Probably will migrate my apps to AWS Beanstalk or OpenShift.

bbody 12y ago

Off to AWS for me.