Free Hosting Fails in Three Different Ways. The Terms Tell You Which.

“Free” is the only word every hosting pitch uses identically. What they do not share is the ending, and the ending is not a matter of how generous the company feels. It is decided earlier, by a question that has nothing to do with hosting: who is paying for this machine, and what do they expect to get back?

There are three answers, and each produces a distinct failure mode. Once you can name which one you are standing on, the risk stops being vague.

The three modes, and the sentence that authorises each

What the free tier is for	Who absorbs the cost	How it ends	The document says
A machine attached to another product	The product’s budget	Removal, with no availability promise	Muse terms: “at any time, for any reason, without prior notice or liability”
A funnel into a cloud account	The acquisition budget	Reclamation when you stop looking valuable	Oracle: “Idle Always Free compute instances may be reclaimed by Oracle”
A growth channel for a developer platform	The marketing budget	Use restrictions and soft metering	GitHub: “not intended for or allowed to be used as a free web-hosting service to run your online business”

The rest of this article is the detail behind each row.

Mode one: the machine is a cost centre

Meta’s Muse agent ships with a dedicated Ubuntu VM per user. It has a shell, a package manager, a browser, and a filesystem that persists between sessions. It is a real computer, and the “free VPS” framing spread quickly.

Its terms never mention hosting, servers, uptime, or bandwidth — not once. What they do contain is the opposite of a hosting commitment:

“MUSE IS PROVIDED ON AN ‘AS IS’ AND ‘AS AVAILABLE’ BASIS.”

Meta may “remove, disable, or restrict access to any artifact created with Muse, at any time, for any reason, without prior notice or liability.”

That second clause is followed by three examples — security risk, legal requirement, terms violation — attached to the word “including.” They are illustrations, not a closed list. The grant before them is the operative part: at any time, for any reason.

None of this is malicious. The machine exists so an agent can execute instructions inside a container. Serving a website is not the job it was built for, so no promise was made about it. The document is honest; the marketing around it is what leaks.

Oracle’s version of the same mode is different in mechanism but identical in logic. Oracle is not selling you a free VM — it is selling you the habit of using Oracle Cloud. A machine that consumes resources without generating usage is a cost with no return, so the documentation says plainly:

“Idle Always Free compute instances may be reclaimed by Oracle. Oracle will deem virtual machine and bare metal compute instances as idle if, during a 7-day period, the following are true: CPU utilization for the 95th percentile is less than 20%. Network utilization is less than 20%. Memory utilization is less than 20% (applies to A1 shapes only).”

Read the shape of that rule. It is not measuring whether your site is good. It is measuring whether you look like a customer. A site that gets modest but steady traffic can sit comfortably under 20% CPU — and be reclaimed anyway, because idle is defined by resource use, not by whether anything is being served.

Mode two: the free tier is a funnel

GitHub Pages is the cleanest example, because GitHub wrote the limitation down instead of leaving it to enforcement discretion:

“GitHub Pages is not intended for or allowed to be used as a free web-hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS).”

Then the soft limits: sites no larger than 1 GB, a soft bandwidth limit of 100 GB per month, and a soft limit of 10 builds per hour — the last of which does not apply if you build with a custom Actions workflow.

Note the word soft. It does not mean “we will not notice.” It means there is no hard counter that stops you at the byte; there is a policy, and enforcement happens when someone looks. That is a different kind of ceiling, and for a site that intends to earn money — which is the entire reason most people read these articles — the restriction is not about volume at all. It is about purpose.

This matters because the restriction is easy to satisfy on a personal blog and impossible to satisfy on a site with ads and affiliate links. Same platform, same free plan, two very different answers, decided by what the site is for rather than how big it is.

Mode three: the free tier is a growth channel

The third mode is the one most static hosts use, and it is the least hostile: the free tier is deliberately kept usable because it is how people discover the paid one. The failure mode here is not removal or prohibition. It is metering.

That is a different problem, and it has its own arithmetic — which meters are counted (bytes, requests, build minutes), and why a site that is cheap on one model is expensive on another — so it lives in its own article rather than being repeated here. The short version: on this mode you are usually safe, and you should still know which meter you are near.

How to place any free tier in five minutes

Search the terms for as is. If the phrase appears with a warranty disclaimer, availability is not part of your deal. That is mode one or mode three with the brakes off.
Search for may reclaim, may remove, suspend, terminate. Who can end it, on what notice, and does the clause contain “for any reason”?
Search for not intended, not allowed, acceptable use, commercial. This is where mode two hides, and it is the cheapest thing to check before you invest a month of writing.
Find the SLA or the uptime figure. If there isn’t one, there is no commitment, and “99.9%” in a blog post is marketing rather than a term.

Four searches, about five minutes, and you know which of the three modes you are standing on before you have written a line of content.

What follows from the classification

Mode one is for disposable work. Scripts, experiments, a build you will throw away. Never the thing a domain points at, because the removal clause does not need your consent or your mistake.
Mode two is for non-commercial publishing. A personal notebook, documentation, a project page. The moment the site is meant to earn, the restriction — not the bandwidth — is what you are violating.
Mode three is where a commercial site belongs. Not because the company is nicer, but because its incentive is to keep you running until you outgrow the plan. That is a business model you can plan around.

The mistake people make is treating all three as the same offer with different sizes, then choosing on the size. Size is the least interesting number in the table. The ending is the one that costs you a weekend.

If you have already picked a platform and want to know whether the meter will bite before the business model does, the three meters are worth understanding. And if the platform is a static host you have not used yet, the deployment path is a half-hour read, not a project.