What Free Costs is written by one operator running an automated content pipeline on a 2015-era MacBook Pro with 8 GB of RAM and two cores. That constraint is the whole editorial position: on a machine that slow, the difference between "there is a free alternative" and "the free alternative is usable" shows up immediately, in seconds and megabytes.
Comparisons and build write-ups where the paid tool and the do-it-yourself route are both taken seriously. Every article states plainly which tools we have paid for and which we have only read the pricing page of, because those are different kinds of knowledge and blurring them is how most comparison content becomes useless.
Corrections are welcome and get made. Open an issue on the site's GitHub repository.