Back to Blog

How to protect a free object storage tier

Free storage tier abuse grows every month, because stored bytes keep billing. See the arithmetic, which basic fixes break and what to do about old data.

Your free tier has the best retention number in the company. Nearly every byte uploaded to it since spring is still there, and free storage has grown by about 12 TB a month for seven months in a row. For a storage product, that looks like trust.

It's a made-up example, so change the figures to fit your product. Your free plan gives every account 20 GB, and today you want to find the free accounts most likely to upgrade, so you sort them by bytes stored. The first page is all accounts sitting at 19.9 GB. So is the next page, and the one after that. You add a column for the last read, and most of it is empty. The files went in once and nobody has touched them since.

There are 4,200 accounts like this, holding 84 TB. All of your paying customers together hold 96 TB.

Say those accounts come from about 50 people, each opening 12 new accounts a month, filling each one and moving on. That's 240 GB of free space a month for each of them. For you it's free storage tier abuse, and the arithmetic is worse than it is for free credits, because a credit gets spent once and a stored gigabyte bills you again next month. Assume disks, replication and power come to $0.02 per GB per month, and replace that with your own figure.

50 people x 12 accounts x 20 GB = 12 TB added every month

Month 1:    12 TB x $0.02 per GB =   $240
Month 7:    84 TB x $0.02 per GB = $1,680
Month 12:  144 TB x $0.02 per GB = $2,880
Month 24:  288 TB x $0.02 per GB = $5,760

Add the months up and the first year costs $18,720 ($240 x 78). Two years cost $72,000 ($240 x 300). Your $15 plan includes 250 GB, which costs you $5 when it's full and leaves $10 of margin, so by month 12 these accounts cost as much as the margin on 288 paying customers ($2,880 ÷ $10).

Now say all 50 people stopped after month 7. The flat line below is what you'd keep paying anyway, because the files don't leave when the signups stop.

Monthly storage cost, illustrative050010001500200025003000123456789101112US dollarsMonth
Monthly storage cost, illustrative01000200030001357911US dollarsMonth

That same week, your capacity alert goes off. You keep your 240 TB pool under 85%, because a cluster needs room to rebuild when a drive dies, and you've just reached the line. Paying customers hold 96 TB, real free users hold 24 TB and these accounts hold 84 TB. That's 204 TB of 240 TB, or 85%.

Say writes start to slow while a rebuild runs. At 7:40 a.m. a customer on that $15 plan writes in: "Our nightly database backup has failed twice this week. Is it us or you?" That backup is the only reason they pay you, and they're already asking how to move it.

You buy capacity in 120 TB blocks on 12-month terms. At your rate that's $2,400 a month (120,000 GB x $0.02), so $28,800 you'd commit to this week. If your company spends $40,000 a month, that's about three weeks of runway. Without those accounts you'd be at 120 TB, exactly half full, with nothing to buy. With them, the new block buys 8.5 months before this same alert (102 TB of room ÷ 12 TB).

Deleting the accounts would be quicker, except you're a storage company. You can't prove who's behind any of them, and erasing a real developer's backups because they looked like the others is the worst mistake you could make. A 60-day notice period alone costs another $3,360 (2 x $1,680). And that retention number you liked an hour ago? Of the 108 TB on your free tier, 84 TB is these accounts. That's 78% of it.

Why free storage tier abuse compounds

Most free allowances get used up. A credit is spent, a free minute ends and a monthly quota resets. Storage goes the other way: every upload keeps costing you until someone deletes it, and nobody deletes free storage, because nothing prompts them to and there's nothing to gain.

A free bucket is useful the moment it accepts a file, and if your API works with standard storage tools, the next 20 GB is one new key away. Your quota counts bytes inside one account, so each new account looks like a model free user: verified, under the limit and quiet. Quiet accounts make almost no requests, so your usage alerts never fire.

The obvious fix is a smaller allowance. Cut 20 GB to 5 GB and everything already stored stays stored, unless you're willing to delete data from people who stayed inside the rules you gave them. The developer testing you on a side project gets a quarter of the room. Someone after 240 GB a month opens 48 accounts instead of 12 (240 ÷ 5).

Basic ways to limit free storage, and where they break

Start with signup checks, because they're cheap and each one does catch something. A unique-email rule compares strings, and one inbox can have several: Gmail ignores dots, and plus-tagged mail reaches the same inbox. That's how email works.

Basic fixWhat it catchesWhat it missesWho it wrongly blocksWhat it costs to keep working
Email verificationTypos and dead addressesAny second real inboxDevelopers whose code lands in spamDeliverability work
Disposable-domain blocksKnown throwaway servicesNew domains and ordinary mailboxesDevelopers using privacy forwardingA list someone updates forever
Gmail dots and plus addressingOne Gmail inbox written several waysA second real mailboxDevelopers who tag one inbox per projectUpkeep as mail services change
CAPTCHASimple scriptsPeople signing up by handPeople using screen readersFees and lost signups
Card requirementCasual second accountsAnyone with another cardStudents and hobby projectsFewer free signups
One per IP addressRepeat signups on one connectionAny other networkOffices, campuses and shared developer networksExceptions and tickets
VPN blocksKnown VPN rangesEverything off your listDevelopers on company VPNsAnother list to maintain

People opening 12 accounts a month aren't casual, so the rows that stop casual second accounts don't slow them much. The rows that do bite land on your own audience, because developers sign up from cloud machines and shared offices, and plenty keep separate accounts for clients or staging on purpose. A signup check also runs only at signup. All 84 TB got in before you added it, and it's still billing.

The controls inside the product have their own gaps. Rate limits catch bursts from one account, and a repeat account uploads its 20 GB once and then sits still. Your 20 GB quota, meanwhile, is working perfectly on all 4,200 accounts.

Manual review runs into a problem specific to storage: you can't look inside. Customers trust you not to read their files, and encrypted objects wouldn't tell you anything anyway. At 600 new full accounts a month and 2 minutes each, you're spending 20 hours a month, and an account holding 19.9 GB of never-read files looks exactly like someone's honest backup. What you really want to know is whether this new account is the person who took 20 GB last week, and nothing on this list can tell you that.

How to protect a free storage tier, step by step

Build around the thing that makes storage different: the pile.

Price an account over its life. Multiply the allowance by your monthly cost and the months it's likely to stay. 20 GB x $0.02 x 24 months is $9.60, where a one-month view says $0.40.

Measure the pile. Each month, total the free GB with no reads in 90 days and work out what share of your capacity that is. Your retention chart was hiding this number.

Give free storage its own pool and a hard ceiling. When the free pool is full, new free accounts wait. A bad month on the free tier then can't reach paying customers' writes or your rebuild room. If you do one thing this week, do this.

Put an expiry rule in your free terms before you need it. Untouched free data gets a notice, and then it's deleted. It's the only fix here that shrinks what you already pay for, and the chart below shows one careful way to run it. The catch is that a good backup exists so nobody ever has to read it.

YesNoYesNoFree account at its limitno reads in 90 daysEmail the ownerwith a 60-day noticeOwner repliesor logs in?Keep the datarestart the clockPaid plan oropen ticket?Hand to a personDelete after noticesend confirmation
YesNoYesNoFree account at its limitno reads in 90 daysEmail the ownerwith a 60-day noticeOwner repliesor logs in?Keep the datarestart the clockPaid plan oropen ticket?Hand to a personDelete after noticesend confirmation

Even if all of that works, the pile doesn't go away. A file that waits 90 days to count as untouched and 60 more for its notice stays about 5 months, so 12 TB a month settles at a permanent 60 TB, or $1,200 a month (60,000 GB x $0.02). Every fix so far runs once at signup, rations everyone or cleans up afterward. The inflow gets settled at a single moment, when a new account asks for its 20 GB and you have to decide whether this claim should go through.

Evaluate every claim before the space goes out

You don't have to build your own abuse prevention system. With AbuseZero, your server makes one API call before the 20 GB is granted and gets a clear allow or deny, under rules you control. Every row in that table is a single check. AbuseZero's multi-layer AI risk analysis examines 140,000+ signals, detects linked claims and flags the abuse single checks miss, and you also get a proprietary algorithm, with AI that checks the claim again.

Email addresses are the cheapest thing anyone can change, and AbuseZero recognizes repeat devices across new accounts, even when email addresses keep changing. It checks mailbox aliases and disposable domains, so that work stops being your team's job. Where a one-per-IP rule has an address and nothing else, AbuseZero sees beyond it with VPN, hosting, network reputation, Tor and proxy intelligence. Creating a fresh account isn't enough to erase previous activity.

Eligibility is yours to set, and Observe mode shows you what would be denied before anyone is blocked. In this scenario, each repeat claim you deny is 20 GB that never starts billing, worth $4.80 for every year it would have stayed. Your pool, your expiry rule and your quotas stay in your application. The quickstart protects your first benefit.

Frequently asked questions

What is free storage tier abuse?

It's opening several free accounts to stack up more storage than you meant one person to have. It costs more each month because the files stay.

Can I delete files from accounts I think are duplicates?

Not on suspicion alone. Say what happens to free data in your terms, send a notice and give people a way to respond.

How do I keep repeat accounts off my free tier?

Basic signup checks slow down casual attempts. To decide each grant, evaluate the claim first: AbuseZero's evaluation returns allow or deny before the space goes out.

Before you order the next block of capacity

Keep reading

Copying your prompt…

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