I understand why they're doing this - companies have to make money - I get that.
I'm still annoyed with Heroku though. Cachet (https://cachethq.io) supports the "Deploy to Heroku" button. My experience is that their support is terrible. I've contacted them several times via; Twitter, email, GitHub and had no support from them in regards to this bloody button.
The reason I support Heroku in the first place is because of the free tier. It makes deploying your own instance of Cachet much easier. However, we've been having issues supporting it with Laravel 5's environment configuration anyway, so this is the last drop in the bucket before I pull native Heroku support.
I'm still annoyed with Heroku though. Cachet (https://cachethq.io) supports the "Deploy to Heroku" button. My experience is that their support is terrible. I've contacted them several times via; Twitter, email, GitHub and had no support from them in regards to this bloody button.
The reason I support Heroku in the first place is because of the free tier. It makes deploying your own instance of Cachet much easier. However, we've been having issues supporting it with Laravel 5's environment configuration anyway, so this is the last drop in the bucket before I pull native Heroku support.
Our demo (https://demo.cachethq.io) and our own status page (https://status.cachethq.io) are both hosted on Heroku with the "Auto Deploy" function, but only because it's "easy" to do.