In the context of the article, the costs I'm referring to are related to a third-party component (integrated easily by default in a framework) that is moving to a pay-sometimes license.

(you also make a very observant hint: total cost of ownership includes hardware-level resource provisioning)