The free tier was never generosity. It was a customer acquisition cost carried on the engineering side of the ledger rather than the marketing side, and for most of the last decade it was an excellent trade. Storage and bandwidth fell reliably, a non-paying user cost a fraction of a cent to serve, and the funnel they fed was worth vastly more than the infrastructure they consumed.
Both halves of that trade have moved. The features users now expect are not storage and bandwidth; they are computation, and computation has not fallen the way its predecessors did. A free user who generates, summarises or transcribes costs real money every time, and the cost recurs whether or not that user ever converts.
What replaced free is not paid, it is metered
The vendors moving fastest are not simply deleting the free plan. Doing that severs the funnel, and the funnel still works. What they are doing instead is separating the parts of a product that are cheap to serve from the parts that are not, and leaving the cheap parts free indefinitely while metering the expensive ones from the first use.
This produces pricing pages that look stranger than they used to. A plan may offer unlimited projects, unlimited collaborators and unlimited history, then stop you at a small monthly allowance of the one feature the product is now marketed on. That is not a mistake or a dark pattern; it is a fairly precise map of which operations cost the vendor money, which is the same map inference costs drew when they moved from footnote to line item.
Buyers are absorbing this unevenly. Procurement teams already contending with more tools than they can account for now find that consumption is variable in a way seat licences never were, which makes the annual number harder to forecast and the renewal conversation harder to prepare for. Several report that the shift from per-seat to per-use has done more to complicate budgeting than any price rise.
The knock-on lands hardest on the developer tier, where free was doing structural work rather than marketing. A generous free API allowance let people learn a product, prototype against it and bring it into an employer, and that path was how a great deal of enterprise software got adopted. Metering it protects margin and closes the path, which is a slow cost that will not appear in this year's numbers. Platforms that already went through the API economy's consolidation into a utility recognise the pattern: the pricing that makes a mature business can prevent the next one.
The same pressure is reshaping what vendors expect from what they build on. When a dependency's own costs are usage-linked, open source maintenance stops being a community question and becomes a procurement one, because the cost of the stack is no longer fixed at the moment you choose it.
What is disappearing, then, is not free software. It is the assumption that a company can afford to be indifferent to how much a non-paying user consumes — an assumption that held for long enough that a generation of products was designed around it.
