How to protect the hosted free tier of an open source project
Repeat accounts can eat a hosted open source free tier and slow your paying teams. What each basic fix catches, who it blocks and how to say no fairly.
It's 11:20 p.m. on the 8th, and you're in your admin table because a customer on your $50 team plan wrote in: "Our nightly sync used to take 6 minutes. Last night it took 40. Did something change?" You sort your free accounts by compute used this month. The top row has burned all 50 of its free hours, a week in. One row down is a second account just like it. It runs the same job, it has used the same 50 hours, and it was created four minutes after the first.
You keep scrolling. By 1:05 a.m. you've counted 220 of them, and you've stopped feeling tired. This is open source cloud free tier abuse, and from where you're sitting it looks nothing like an attack, because every one of those accounts is inside its limit.
These numbers are a scenario, so swap in your own as you go. Say your hosted version runs on a shared pool of 60 workers at $0.08 a worker hour:
- 220 accounts × 50 hours = 11,000 hours a month
- 11,000 hours × $0.08 = $880 a month
The bill is the smaller problem. Allowances reset on the 1st, these accounts spend theirs straight away, and 11,000 hours ÷ 60 workers is about 183 hours, or 7.6 days of your entire pool. For the first week of every month, a team paying you $50 waits in line behind jobs that pay you nothing. That's where the 40 minutes came from.
Then you look at the rest of the table. You have 4,100 free accounts, and the other 3,880 average 2 hours a month, or 7,760 hours in total. So 5.4% of your free accounts (220 ÷ 4,100) are using 59% of your free compute (11,000 ÷ 18,760 hours). The free tier you meant to offer costs about $621 a month (7,760 × $0.08). You'd pay that forever without a second thought. It's students, and people trying your project before they show it to their boss.
Your hosted plan brings in $6,200 a month from 124 teams. The full worker bill is $3,456 (60 × 720 hours × $0.08), which leaves $2,744, and that's what pays for your time on the project. Those 220 accounts are $880 of that bill, so you'd have 32% more left over without them.
At 9:40 a.m. the customer replies. Their engineer has read your self-hosting docs and thinks one server will do the job, so they're cancelling. Say two more teams follow this quarter. That's 3 × $50, or $150 a month, gone from the people who read your changelog and file good bugs. The self-hosted option you were proud of is what lets your best customers walk away, and the 220 accounts have no reason to go anywhere.
By lunch there's a draft open: cut the free tier from 50 hours to 10. Your README still says the hosted free tier is there for the community. You wrote that line yourself, and you can already picture the issue thread.
Why open source free tiers get hit so hard
A free tier is handed out per account, so every new account is a new allowance. Your users are developers, so they can schedule a job and they know what free compute is worth. And if your limits live in the repository, anyone can read the exact number. Move them to a private module and you're maintaining two versions of your own project.
You're also slower to act than a closed SaaS would be, for a decent reason. A contributor you block by mistake can open an issue in public, with your project's name on it.
The obvious fix is that draft on your screen. Cutting 50 hours to 10 lowers the cost per account by 80%. But 11,000 hours ÷ 10 is 1,100 accounts, and opening more accounts is the one thing these people have already shown they'll do. Your average honest user, at 2 hours, won't notice the cut. The contributor testing a branch and the teacher running a workshop will. A one account per person policy is worth writing, but a sentence in your terms doesn't stop anyone.
Your license covers the code. Compute is a separate gift, and you get to set its terms. What you're weighing is goodwill against cost, and the options don't all land where you'd guess.
Those positions are judgment calls, so move them around for your own project.
The basic fixes, and how each one breaks here
Each of these catches something real, and each one stops somewhere.
Email rules
Email verification catches typos and dead addresses, and a unique-email rule catches the same address twice. Neither touches a second real mailbox, because a verified address only proves someone can open an inbox. One inbox can also be written several ways. Gmail ignores dots, and mail sent to name+anything@gmail.com lands with name@gmail.com. That's just how email works, and a rule built on it needs upkeep.
Disposable-domain blocks catch known throwaway services until the next domain appears. They also turn away people using privacy forwarding, and some of your most loyal users will be among them. Someone has to keep that list current forever.
CAPTCHA, phone and card
A CAPTCHA filters simple scripts. It does little against a person signing up by hand, some automation gets through it from day one, and people using screen readers or privacy tools get the worst of it.
A phone requirement stops casual second accounts and misses anyone with another number. You pay for every text, and you shut out people without a reliable mobile number, which a worldwide community has plenty of. Requiring a card filters harder and costs more goodwill. Students and contributors in places where cards are uncommon can't get through, and "free, just add a card" is a sentence you'll be defending in your issue tracker.
IP and VPN rules
One signup per IP address catches repeats on one connection. It also fails a university lab, a company office and every workshop you've hoped someone would run on your project. Put 30 people on one campus network and 29 of them get rejected. VPN blocks catch the ranges on your list and nothing else, and they land on privacy-minded people and staff on company VPNs. Both leave you with a list to maintain and a queue of exception requests.
Rate limits and usage caps
Rate limits stop bursts from one account. Usage caps stop one account going past its allowance. You need both, and neither saw what happened on the 8th, because all 220 accounts stayed exactly inside the 50 hours. Rate limits answer a different question from who should get the allowance at all.
Manual review
A person can spot things a rule won't. At one minute an account, 4,100 free accounts is about 68 hours (4,100 ÷ 60), and that person is usually a maintainer, so it comes straight out of the project. It's also the fix most likely to go wrong in public, when someone reviewing at 1 a.m. bans a contributor whose account looked odd.
Stack all of this and your signup asks for a verified email, a puzzle, a phone number and a card, on a project anyone was meant to be able to try. The 220 accounts you already have never see that form again.
What to do about your hosted free tier
Write down who the tier is for. "Trying the project without installing it" is a good answer. Put it on your pricing page.
Give free jobs their own capped pool. In the scenario, 12 workers × 720 hours is 8,640 hours, enough for the 7,760 honest hours, with a ceiling of about $691 a month (8,640 × $0.08). Your paying teams stop waiting. Repeat accounts can still fill that pool, so this protects your revenue while your free users take the queue.
Make self-hosting the honest alternative. A closed SaaS can only say no. You can say no and hand over the whole product. Keep one page that really works, test it each release, and link it from every limit message.
Make exceptions on purpose. Give contributors and workshops a way to ask for more hours, answered by a person.
Keep hosted rules off the self-hosted path, so nobody running their own copy ever meets them.
A message you can use
You've used the free hosted hours for this project. You can keep going for free by running it yourself with our self-hosting guide. If we've got this wrong, reply here and a person will take a look.
Here's the order we'd take the options in.
Deciding who gets the free hours without a second codebase
Everything above looks at the account in front of it. Your free tier needs to know something else before the hours go out: does this claim look like a repeat?
AbuseZero was built for that question, and it goes well past where a domain list and a campus IP rule gave up. A single check looks at one thing. AbuseZero's multi-layer AI risk analysis examines 140,000+ signals, detects linked claims and flags abuse that single checks miss. There's also a proprietary algorithm, with AI that checks the claim again. AbuseZero recognizes repeat devices across new accounts, even when email addresses keep changing, and it checks mailbox aliases and disposable domains, so that's one less list for your maintainers. It sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence, which beats rejecting 29 people in a workshop. Creating a fresh account isn't enough to erase previous activity. And you don't have to build your own abuse prevention system, then explain it in a public repository.
Your hosted code makes one API call and gets a clear allow or deny. The rules are yours, they live in AbuseZero instead of your repo, and eligibility can be once per calendar month to match a monthly allowance. Observe mode shows what would be denied before anyone is blocked, which matters when the person might be a contributor. A deny is where your self-hosting message goes. The quickstart covers your first benefit.
Frequently asked questions
Is it fair to limit the free tier of an open source project?
Yes. Your license gives people the code, and self-hosting stays open to everyone. How much hosted compute each person gets is up to you.
Should I remove the hosted free tier?
Not first. In this scenario the tier you meant to offer costs about $621 a month. Work through the decision before you take it from everyone.
Won't a good self-hosting path cost me customers?
Some, yes. The teams that stay are paying so they don't have to run it themselves, so a fast paid queue is what keeps them.
Protect the free tier you promised
Start with Builder
Pay as you go. Protect your free hours today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High volumes and custom terms.