Correct. If you're running more than one dyno in an app, however, there are no 'timeouts'.
If you're trying to maximize your free dyno usage, however, you might want to use the 'heroku scheduler' addon, and have it ping your app once every 10 minutes to keep it 'awake'.
Re:Heroku WebSocket performance
by derekchiang on Monday October 28, 2013 @03:36PM
(#6629253)
Yeah, it's killed after a timeout and restarted when a new request comes in. Which is why when you revisit an old Heroku app it takes a long time to load.
You can keep a single free Dyno "awake" by hitting it with a request at least once per hour. If you use New Relic the built in availability monitoring will do the trick and otherwise Scheduler should work. For more info:
Re:Heroku WebSocket performance
by felipesabino on Monday October 28, 2013 @05:42PM
(#6630035)
Now you can also check if your app is sleeping on the dashboard :)
https://blog.heroku.com/archives/2013/6/20/app_sleeping_on_h...
Also, I used pingdom.com once to make sure that my "very low in traffic" app never sleeps, but any solution that performs a request in this interval would be valid
I couldn't find this info in the pricing page.