We Read the Terms of Service So You Don't Have To: The Real Cost of 'Free' Hosting

Nobody reads the terms of service. We get it — you're spinning up a side project at 11 PM, you want to click the checkbox and move on with your life. But when a hosting company uses the word "free," the details of how they make that free work are hiding in exactly the place you skipped.

So we did the unglamorous work. We read the terms of service, acceptable use policies, and pricing FAQs for the most popular free hosting tiers out there. Here's what we found — including a few clauses that genuinely surprised us.

The Sleep Policy Problem

The single most common catch isn't hidden at all — it's just easy to forget. Several popular platforms will spin down or outright delete projects that sit idle.

Some services put apps to sleep after 15–30 minutes of inactivity, which means the first visitor after a quiet stretch stares at a cold start that can take 30 seconds or more. Others are more aggressive: a handful of platforms reserve the right to delete apps that haven't been deployed to in a set window — sometimes 30 days, sometimes longer. One platform's FAQ bluntly states that inactive free projects get removed without notice.

What this means in practice: if you host a portfolio site and don't touch it for a month, you might come back to a 404. Set a calendar reminder to redeploy, or pick a host without an idle-deletion policy if the project matters.

Bandwidth Caps and the 'Soft' Limits

Most free tiers advertise generous bandwidth — some claim "unlimited." Read closer, though, and you'll find phrases like "fair use," "subject to reasonable limits," or traffic caps measured in gigabytes per month (typically 100 GB across the more generous ones, sometimes far less).

The catch isn't the cap itself — 100 GB is plenty for a hobby blog. The catch is that when you cross it, the consequences vary wildly. Some hosts just hard-stop your site. Others email you a warning first. A few will push you into an upgrade mid-traffic-spike, which is a rough way to find out your side project went viral.

Data Ownership: Mostly Fine, Read Anyway

Here's the good news: we found no mainstream free host claiming ownership of your code or content. That horror story is mostly a myth at this point. What you will find are licenses — the legal language letting the host store, cache, and reproduce your content to serve it. That's normal and necessary.

The clause worth watching instead? A few platforms reserve the right to display branding or aggregate usage data. Not a dealbreaker, but worth knowing before you launch a client demo on a free tier.

Resource Limits Disguised as Generosity

Free tiers love to advertise "X hours of compute" or "Y MB of RAM." The fine print usually adds:

• Shared, throttled CPU — you're competing with other free users on the same box
• Ephemeral storage — files you write may vanish on redeploy or restart
• Build time limits — one platform caps free-tier build minutes, which stings if you have a slow CI pipeline
• Team size restrictions — some "free" plans are only free for solo developers

None of these are scams. They're how a company subsidizes free hosting. But they're the difference between "free forever" and "free until you actually get users."

The Ones That Genuinely Deliver

To be fair to the industry: several free tiers are remarkably honest. Static site hosts in particular tend to offer generous bandwidth, real SSL, and no sleep policies — because serving static files is cheap. Platforms with explicit free tiers backed by big cloud providers often publish their exact limits in plain numbers rather than vague "fair use" language, which is exactly what you want to see.

The pattern we noticed: the more precisely a company states its limits, the more likely it is to actually honor them. Vague language is where the trouble lives.

Our Verdict

"Free forever" is real, but "free forever with no strings" usually isn't. Before you commit a project to any free tier, spend ten minutes in the docs looking for three things: an idle-deletion policy, a bandwidth cap with stated consequences, and storage persistence rules. If all three are clearly documented, you've found a host you can actually trust with your weekend project.