Why Is It Free? — Who Pays for Cloudflare and GitHub
The result first
My blog costs $0 a month to host, and last night I had Moka measure what it uses: about 87 MB in total. That left a simple question — if the storage and the delivery are free, who is paying?
The answer: “free” comes in two kinds.
- The advertising kind. Meta and Google work this way. Users pay nothing; advertisers pay. What is gathered is your attention, and attention is the product.
- The paying-customer kind. Cloudflare and GitHub work this way. Most users pay nothing; a smaller number of large companies and paying users cover the cost. No advertising. What is gathered is users themselves.
My blog rides on the second kind. Here is what Moka found about the two companies behind it.
Cloudflare: a few thousand large customers carry millions of sites
Cloudflare is a US company, started in 2010, that delivers and protects websites around the world. Published figures say it serves more than 41 million websites — roughly a fifth of the web, and a number close to the number of households in Japan.
Its money, from public filings and reporting:
- Revenue in 2025 was about $2.17 billion
- Of that, advertising revenue was zero
- It had about 332,000 paying customers — and about 4,300 of them, large companies paying over $100,000 a year, accounted for around 73% of revenue
So the shape is simple: a few thousand large customers pay, and the foundation under 41 million sites is carried by that money. My 87 MB sits in a corner of it.
Why keep the free users? The company’s own materials give three reasons:
- Attack data. Attacks on free sites are seen too, so the defenses keep learning. Those defenses are what large customers pay for.
- Scale lowers cost. The more traffic runs through one network, the cheaper each piece becomes. The company itself has written that its free service helps keep its costs lower.
- People carry tools into work. Someone who learns a tool for free at home tends to suggest it at their company — and companies are where the paid plans live.
In 2024, Cloudflare’s official blog published a post reaffirming its commitment to free. Free is not charity there. It is part of the machine.
The site-hosting service, Cloudflare Pages, appeared in beta in December 2020 and opened to everyone in April 2021 — free from the start. Back when I used Cloudflare on my funeral company’s site, it was not yet a place to put a website at all.
GitHub: the place developers gather is the value
GitHub is where code — the parts and blueprints of software — is stored. It started in 2008, and my blog’s parts are stored there too. Its site-hosting feature, GitHub Pages, dates from the same era — and it is free as well.
In 2018, Microsoft bought GitHub for $7.5 billion. Today, more than 150 million developers use it (a 2025 figure) — more people than the population of Japan.
The money comes from plans for companies:
- Team: $4 per person per month
- Enterprise: $21 per person per month
- Copilot, the AI coding helper, also has paid plans
The reason for free storage mirrors Cloudflare’s. Because the free shelf exists, developers gather. The tool they learned for free keeps being used after they join a company. For Microsoft, owning the place where developers gather was itself the value.
I was one of the people who didn’t know
I had actually used Cloudflare before. Back when I ran a funeral company, I placed it in front of our website because I had heard its caching would make the pages load faster. Caching means keeping copies of a site close to its readers. To me, it was a tool for speed.
The setup back then was to keep the server we already had and place Cloudflare in front of it. It was known as an add-on for speed, and that is exactly how I used it.
So I knew the name, and I knew it worked. What I did not know was that you could put a whole website there.
People in IT may well know that. In other trades, even people who have heard the name often have not heard that part. I hadn’t. The tool had reached me — the idea that it could be a free home for a site had not.
Price and capacity, in plain numbers
Asked what my “server” costs per month and how much capacity it has, this is what Moka found.
The monthly price is $0. The only money spent is the domain: $12.29 a year. The shelf itself costs nothing.
Capacity has no gigabyte number. Cloudflare’s shelf is measured differently:
- Up to 20,000 files
- Up to 25 MB per file
- Up to 500 publishing runs a month
- Reading traffic (bandwidth) is unlimited, even on the free plan
If it were paid: the next plan (Pro) is $20 a month billed annually, or $25 monthly. What grows is the limits — 5,000 publishing runs, 100,000 files — plus image and security features. Capacity in gigabytes does not appear, because that is not how this shelf is sold. The plan above that (Business, $200 a month) has no role at my scale.
Rental servers, the familiar route, are usually sold as “about ¥1,000 a month for 200–300 GB.” Gigabyte capacity is a number from that shape of service. Different shape, different ruler — that was the answer to last night’s question.
My blog, in their numbers
Last night’s measurements, placed against the free plan’s limits:
- Stored: about 87 MB in 646 files. The free limit is 20,000 files — I am using about 3% of the allowance.
- Publishing runs: a handful a month. The free limit is 500 a month.
- The paid plan ($20 a month) raises those limits, but nothing in my numbers asks for that yet.
I am one free user at the entrance. And in this design, standing at the entrance is not freeloading — the users at the entrance are part of how the machine works. Knowing that removed most of the guilt of using something this good for free.
What this changed for me
Free has a reason. Once the reason is clear, the free thing becomes easier to trust.
With the advertising kind, what is gathered is your attention. With the paying-customer kind, what is gathered is the number of users, and the money arrives from large customers. Knowing which kind your tools are tells you what you are part of.
Free plans can change when a company’s circumstances change — that is exactly why it is worth knowing how the free is paid for. Knowing who pays for the tools I use is, for a non-expert like me, the right distance to keep.
Sources
- Cloudflare revenue, paying customer counts, and the large-customer share: public articles based on the company’s financial filings, checked in 2026 and organized by Moka
- “Reaffirming our commitment to free”: Cloudflare’s official blog, September 2024
- GitHub’s acquisition price ($7.5 billion, 2018): public articles based on Microsoft’s announcement
- GitHub pricing (Team $4 / Enterprise $21 per user per month): GitHub’s official pricing page, checked November 2026
- Developer count (150 million+): public reporting of the 2025 milestone
- Prices and limits (Pro $20/month, 20,000 files, 500 builds a month, and so on): Cloudflare’s official pricing pages and developer documentation, checked November 2026
- November 18, 2026 ― Draft created (ledger No.160. Title is a draft proposal; final decision by the author). Price-and-capacity section added at the author's direction(4,793 characters)
- November 18, 2026 ― Published (author approved; Japanese and English published together)(4,793 characters)
- November 18, 2026 ― Author's own experience added (used Cloudflare for speed on a funeral company site, without knowing it could host a site; author approved)(5,423 characters)
- November 18, 2026 ― Start of the free hosting added (Cloudflare Pages: beta December 2020, general availability April 2021, free from the start; GitHub Pages since 2008)(5,693 characters)
