CF user here. While I agree tag support would be cool, complaining about CF buildpack incompatibility is a bit disingenuous, no? I mean, you generally can use

CF user here. While I agree tag support would be cool, complaining about CF buildpack incompatibility is a bit disingenuous, no? I mean, you generally can use a Heroku build pack on CF, but if you have unique requirements, that's why there are CF-only buildpacks. The general reason is that some CF deploys don't have internet access and therefore need a completely offline cache of the binaries. Secondly, > they're missing a few core features, most notably application rollbacks and zero-downtime app migrations at the router level I'm curious why you think this? For example: http://blog.pivotal.io/cloud-foundry-pivotal/case-studies-2/case-study-how-pivotal-network-does-zero-downtime-deployment-on-cloud-foundry http://blog.pivotal.io/cloud-foundry-pivotal/case-studies-2/...