No: first not "many", but very few. And second they are proprietary projects.
Other people express strong opposition to the idea that "open" might just mean the same thing as "available" in the context of open source. None of those people have proposed a more coherent definition that I've seen of what that word means in that specific phrase though.
Alternatively they can put such large share-back requirements that corporations don't want to use it and would rather pay for an alternate license. SSPL and to a lesser extent AGPL achieve this.
What you're asking is, should widely used libraries be proprietary software sold for money? And that is indeed an honest question. There's a huge ecosystem of developers out there who say yes, there's nothing special about that idea at all.
For example, on Apple, Google and Microsoft platforms you don't use OpenSSL when writing native apps. You use the vendor's cryptography APIs. The licenses of Windows and macOS force all users large or small to pay for them. On Android, the native crypto provider is Conscrypt:
https://github.com/google/conscrypt/
... which is open source, but you will notice that it doesn't accept outside contributions and is funded by revenue from Android's proprietary components licensing. So that's very close to the model you're suggesting: it's "open source" but in practice large corporations pay Google lots of money for the privilege of shipping it.
Moreover Google fund BoringSSL and other forks of OpenSSL. The issue here isn't funding levels (anymore). The issue is that OpenSSL is written in C, and not very good C at that.
The thing you're allowed to charge for but only a reasonable amount is to provide the sources to software you have previously distributed, for free or otherwise. If I get some binaries from you and then request the sources too, under the GPL, you are forced to provide them, but you can ask for a fee to cover the transfer costs.
Yes, that Automattic. Yes, that Google, AWS and Cisco. Yes, that Microsoft. There are one or two entities in this list I don't mind but... damn.
It's time to retire the phrase "open source" and go back to "free software". Not many people know "open source" was originally coined by corporations who didn't want anything to do with freedom.
The problem with "free software" lies exclusively with the English language; other languages don't have the same issue due to having separate words for "freedom" and "zero price".
Also see LibreOffice.
And when Redis changed their license for such reasons, companies and people united to create ValKey or even the Centos/Rocky linux situation.
Then I read articles about billionaires donating millions or even billions to various (sometimes frivolous) charities and I wonder WTF.
The numbers just don't add up. It's like there is an invisible force field preventing people from donating money to open source?
Crazy to think that the people who once posted a dumb viral 30-second meme video on YouTube probably got more money than the author of a complex, world-famous open source project which has been at the top for decades and which quite literally intermediates every aspect of almost every human's life.
Does not compute.
From your HN bio, I guess this is your project: https://socketcluster.io/
From the home page, I see that you are sponsored by two different companies. To me, "in terms of funding, it's crickets for me" isn't an honest statement.
If funding is such a problem for you, why don't you use a non-open source license, e.g., Business Source License? This would allow non-commercial projects to use your software for free, but commercial users need to pay. There are a bunch of big, important open source projects that already changed: HashiCorp, CockroachDB, MariaDB, etc.
[1] https://openssl-corporation.org/blog/2025-02-14-annual-repor...
[2] https://www.openssl-corporation.org/assets/Annual-Report-202...
All yours! Use it to your heart's content.