Back to Blog

How to protect a free static hosting tier from throwaway accounts

Free hosting tier abuse bills you every month, long after the signup. The bandwidth arithmetic, why basic fixes break and what to change before the next invoice.

Free hosting tier abuse is one person opening account after account on your static hosting platform, so the traffic of one busy site lands on you for free.

Say it's the 3rd of the month and your CDN invoice has just arrived. You budgeted $3,300. It says $7,350. This is a scenario, and the prices in it are assumptions for you to swap for your own:

  • Free plan: 100 GB of bandwidth a month per account
  • What bandwidth costs you: $0.03 per GB
  • Paid plan: $20 a seat, 1 TB included, $0.15 for each GB after that
  • Paying customers: 400 seats, so $8,000 a month

Real traffic, paid and free, came to 110 TB, the amount you expected. The other 135 TB came from 1,500 free accounts, each serving about 90 GB, and every one of them is under the limit you published.

1,500 accounts x 90 GB = 135,000 GB
135,000 GB x $0.03     = $4,050 a month
$4,050 x 12            = $48,600 a year

Say those accounts belong to 60 people with 25 accounts each. Each person is serving 2,250 GB a month for nothing (25 × 90 GB). On your paid plan that would cost them $20 + (1,250 GB × $0.15) = $207.50 a month, which is why opening 25 accounts felt worth an afternoon. Your invoice shows one number.

That number is about 51 cents of every dollar your 400 seats pay you. Bandwidth now takes $7,350 of your $8,000, leaving $650 for builders, support and your own salary. With $90,000 in the bank and without those accounts, you'd burn $1,500 a month, which gives you 60 months. With them you burn $5,550, which gives you about 16.

It won't go away by itself either, because nobody has to log in for a site to keep serving. If the accounts arrived at 125 a month for a year (125 × 90 GB × $0.03 = $337.50 of new monthly cost each month) and new ones then stopped completely, your monthly cost looks like this:

Bandwidth cost, illustrative0100020003000400024681012141618US dollarsMonth
Bandwidth cost, illustrative02000400026101418US dollarsMonth

New accounts stop at month 12 in that chart, and the bill stays where it is. A trial ends and an AI credit gets spent once. A published site bills you each time a stranger opens it, for as long as it stays up.

Then the same accounts reach your build queue. On the 17th, 8 of those 60 people push an update in the same hour. That's 8 × 25 = 200 builds. At 3 minutes each, that's 600 build minutes on your 12 shared builders, so anyone joining the back of the line waits 600 ÷ 12 = 50 minutes.

At 10:50 a.m. an agency on your paid plan pushes a fix to a client's landing page and watches it say Queued. At 11:36 they write to you: "Our client's campaign went live at 11 with the wrong price on the page. This fix has been queued for 46 minutes. What are we paying you for?"

You refund the month. That agency holds 6 of your seats, so if they leave you lose 6 × $20 × 12 = $1,440 a year, and those builders were busy with accounts that have never paid you a cent.

So you've got a decision you never wanted. You can cut the free plan for everyone, including the students and hobbyists who later brought you into their jobs. Or you can keep handing over 51 cents on the dollar and hope it doesn't grow.

Why free hosting tier abuse stays under every limit

Your free limit is per account, so the account is what someone multiplies. Static hosting suits this better than most products because the person doing it never has to come back. They publish once and you serve it every day after that. (What people choose to host is a separate problem, and this post doesn't cover it.)

The obvious fix is to cut the limit. Say you drop it from 100 GB to 20 GB. Someone who needs 2,250 GB now runs 125 accounts at 18 GB each instead of 25 at 90 GB, which costs them a second afternoon. Meanwhile a student whose project reaches the front page of a forum uses up 20 GB in an evening and gets a paused site on the best day that project will ever have.

Read where free limits should sit and limits that don't invite extra accounts before you touch that number.

Basic fixes for free hosting tier abuse, and how they break

Most teams try these, and each one does catch something. A unique-email rule compares strings, and one mailbox can have many of them: Gmail ignores dots, and plus-tagged mail reaches the same inbox.

Basic fixWhat it catchesWhat it missesWho it wrongly blocksWhat it costs to keep working
Email verificationTypos and dead addressesAny real second inboxDevelopers whose code lands in spamSending and deliverability work
Unique emails, Gmail dots and plus addressingOne inbox written several waysA second real mailboxPeople who sort their mail with plus addressesUpkeep as mail services change
Disposable-domain blocksKnown throwaway servicesNew domains and ordinary mailboxesDevelopers using privacy forwardingA list someone updates forever
CAPTCHASimple signup scriptsPeople opening accounts by handPeople using screen readers or strict privacy settingsFees and lost signups
Phone or card requirementCasual extra accountsAnyone with another number or cardStudents and hobbyistsText charges and fewer signups
One per IP addressRepeat signups on one connectionAny other networkCoworking spaces, campuses and bootcampsExceptions and tickets
VPN blocksKnown VPN rangesEverything off your listRemote developers on company VPNsAnother list to maintain
Rate limits and usage capsOne account overrunning25 accounts under the limitAn honest site on its best dayTuning, and deciding what a capped site shows
Manual reviewWhat a person can spotAccounts under every limitWhoever looks odd to a tired reviewerHours every month

Two of those hurt more on a hosting platform. A one-per-IP rule lets one person in a 30-student bootcamp publish a portfolio and turns away the other 29, in the week they're picking a platform. Manual review sounds fair until you do the sum: 1,500 accounts × 2 minutes is 50 hours, spent looking at accounts that are under every limit you published.

Now line up when most of these run against when you get billed, for one illustrative account at $2.70 a month:

Day 1Email, CAPTCHA, IPDay 1Site publishedDay 3Last loginMonth 6$16.20 billedMonth 12$32.40 billed
Day 1Email, CAPTCHA, IPDay 1Site publishedDay 3Last loginMonth 6$16.20 billedMonth 12$32.40 billed

Your signup rules have finished by the end of the first minute, and the billing runs for the next year. They also do nothing about the 1,500 accounts you already have.

What holds up on a static hosting platform

You can still limit what each account costs and keep paying customers out of that queue.

Make the free limit a real stop. A limit that only sends a warning has no ceiling. Pause the site at 100 GB and each account can cost you at most 100 × $0.03 = $3 a month. Alert on total free-plan bandwidth, so the invoice isn't how you find out.

Give paying customers their own builders. Reserve 4 of your 12. Those 200 free builds now take 600 ÷ 8 = 75 minutes, and the agency's fix starts as soon as one of the 4 is open.

Retire what nobody looks after. After 90 days with no login or deploy, email the owner. If there's no reply in 14 days, pause the site and keep the files. If a third of those 1,500 accounts never answer, that's 500 × $2.70 = $1,350 a month back, from the bill you already have.

Treat the first published site as the claim. Opening an account costs you almost nothing. Free capacity starts when a site goes live, so that's the moment to decide whether this account gets it.

Write the rule down, and decide what a no looks like. Start with one free account per person, with room for work and personal accounts. When you turn someone down, offer the paid plan and a way to reach you.

None of this stops the next free account from opening, and each one is another claim on your free capacity. Account 26 shows up with a new address and an empty history, and 30 students on one connection can look worse than it does. Guess wrong and you've turned away a real developer.

Every row in that table also needs someone to keep it working, and that someone is usually you, after a full day of running a hosting company.

Deciding the free tier claim at the first deploy

You don't have to build your own abuse prevention system, or spend another year topping up a domain list. AbuseZero evaluates whether each claim on your free tier should go through, and it picks up where that table gave out. An IP rule counts signups per address. AbuseZero sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. A unique-email rule compares strings. AbuseZero checks mailbox aliases, disposable domains and mail routing, and recognizes repeat devices across new accounts, even when email addresses keep changing. Creating a fresh account isn't enough to erase previous activity, which is worth a lot on a product where a new account takes a minute to open.

AbuseZero's multi-layer AI risk analysis examines 140,000+ signals, detects linked claims and flags abuse that single checks miss. We also built a proprietary algorithm, with AI that checks the claim again.

Your server makes one API call when someone publishes their first free site and gets a clear allow or deny, under rules you control. Eligibility can be once per user or once per rolling number of days, and Observe mode shows you what would be denied before anyone is blocked. Your platform still meters bandwidth and runs the queue. The quickstart walks you through your first benefit.

Frequently asked questions

What is free hosting tier abuse?

It's one person claiming your free hosting allowance more times than you meant to give it, usually by opening several accounts.

Will a bandwidth cap stop it?

A cap limits what each account can cost you. It doesn't limit how many accounts there are, so the bill still grows with each new one. Keep the cap, and read what rate limits and abuse prevention each stop.

Is every second free account abuse?

No. Developers keep work and personal accounts, and freelancers may keep one for each client. Decide what you'll allow, then set your rules in AbuseZero to match.

Keep free hosting for the developers it's meant for

Keep reading

Copying your prompt…

Copied the to your clipboard. Give it to your coding agent & it will handle the rest.