I try to keep such coupling to a minimum, though. Only when the alternative to a `heroku add ..` is really hard, I prefer to have a much more flexible SOME_SAA

I try to keep such coupling to a minimum, though. Only when the alternative to a `heroku add ..` is really hard, I prefer to have a much more flexible SOME_SAAS_KEY env var and use that in my app/adapters rather than having heroku shoehorn it in. Because the latter only ever ties me further into Heroku. Which, following YAGNI, may not be an issue today, but does make your agility and ability to react to market changes (such as alternatives being a better option) much less. I try to keep my software platform agnostic because any tight coupling will haunt me in future.