How to protect free credits in an AI music generator
Free songs cost GPU time up front, and the files leave with the user. Price the damage, see which basic fixes break and protect credits before you render.
Why did we pay for 141,200 songs last month? Because 5,000 free accounts made 100,000 of them, and those accounts were never going to pay you. At 6 cents a track, that's $6,000 of compute in a month when your subscribers paid you $5,040.
That's a scenario, so rewrite it with your own numbers, but it shows what AI music generator free credits abuse does to a small company. Say every new account on your app gets 100 credits. A generation costs 10 credits and returns two takes of a three-minute track, so a free pack is 20 tracks. These costs are assumptions to replace:
- GPU render: 60 seconds at $2.40 an hour = 4 cents a track
- Lyrics, mastering, storage and delivery = 2 cents a track
- One track = 6 cents
- One fully used free pack = 20 × 6 cents = $1.20
You prepay $3,000 of compute on the 1st, which feels safe. A normal month is $2,472: 420 subscribers making 60 tracks each (25,200 × 6 cents = $1,512) and 2,000 honest free accounts making 8 tracks each (16,000 × 6 cents = $960).
Just before 3 p.m. on the 11th, the balance hits zero and your render queue stops. A wedding videographer on your $12 plan has a first-dance edit due tomorrow. They've watched a spinner for 40 minutes and then got "Something went wrong." Their email is short: "I pay for this. Is it broken?"
You top up from your own card and open the usage export. Spend has been running at $282.40 a day ($8,472 ÷ 30), so $3,000 lasted 10.6 days. Renewals land evenly through the month, which means only about $1,848 had come in by then ($5,040 × 11 ÷ 30). Getting to the 30th takes another $5,472.
Then you find where it went. Say it's 125 people running 40 accounts each:
- 125 × 40 = 5,000 accounts
- 5,000 × $1.20 = $6,000
- 40 × 20 = 800 tracks per person, about 25 GB of CD-quality WAVs
- 100,000 tracks × 60 seconds = about 1,667 GPU hours, against 420 for all your subscribers
So you ban all 5,000 accounts. It takes an evening, and you take back the unused credits, which comes to nothing, because there weren't any. The GPU time is paid for. The tracks are in folders and under videos you'll never find. You can delete your copies and save a few dollars of storage, and theirs stay exactly where they are.
Compute used to leave you $2,568 a month ($5,040 minus $2,472). Now you're $3,432 short. With $30,000 in the bank and $4,000 a month of other costs, your runway went from about 21 months ($30,000 ÷ $1,432) to about 4 ($30,000 ÷ $7,432). You refund the videographer's $12, and if they leave, $144 a year goes with them. The free pack that brought in most of your 420 subscribers is now the thing you're deciding whether to cut.
Why AI music generators get farmed so hard
A free song is a finished product. Answers from a free chatbot are gone once they're read, but a three-minute WAV keeps working for years, whether or not the account that made it still exists. So the demand comes in bulk. A video channel needs new background tracks every week, and a podcast or a small game needs a whole folder. Your $12 plan includes 100 tracks, so getting 800 a month from it would take eight subscriptions, or $96. Getting them from free packs costs someone an afternoon of signups.
Use is lopsided as well. Someone making a birthday song stops when it sounds right, so in this scenario an honest account makes 8 tracks and costs you 48 cents. Someone filling a folder has no reason to leave a credit unspent, so every farmed account costs the full $1.20. That's credit farming, and it's worth pricing your own free user before you change anything.
The money also moves in the wrong order. The GPU charges you the moment a render starts, while any revenue from that account is weeks away, if it was ever coming. Here's an illustrative life of one farmed account:
The obvious fix is to find those accounts and remove them. Do it, because they're distorting your numbers. But look where it sits on that line: by day 30, the last render finished a month ago. A non-commercial term on free tracks has the same problem. It tells someone what they may do with a file they already have, and your GPU bill stays where it was.
Free credit limits that fit a music app
These are yours to ship today, and the first two are worth having whatever else you decide.
- Give paying customers their own queue. One GPU that only reads paid jobs means a free-plan surge can't put a first-dance edit behind thousands of other renders.
- Set a daily compute budget for free renders. Honest free use here is about $32 a day ($960 ÷ 30), so a $40 cap holds free spend to $1,200 a month instead of $6,960. Now look at who gets the $40. It buys about 667 tracks, and farmed accounts want 86% of all free tracks (100,000 of 116,000). First come, first served, your honest users get about 92 of the 533 tracks a day they wanted. The bill's safe, and the free plan is mostly gone for the people it was built for.
- Hold renders until the email is confirmed. An account that never confirms now costs you one email instead of $1.20. Anyone with a real inbox still gets through.
- Make free tracks shorter. If render time scales with length, a 45-second clip takes a quarter of the GPU time: 1 cent, plus the 2 cents of other costs, or 60 cents a pack. That halves the farm to $3,000, and the honest user who wanted a whole song gets a chorus.
- Keep downloads for paid plans. That takes away much of the reason to farm. It also takes away the song someone wanted to send a friend, and shared songs are often how new people find you.
Each of these makes an account cheaper or slower, and a new account still gets all of it again. Cutting the pack itself has the same limit, whatever number of free credits you land on: 20 tracks becomes 10, and 40 accounts become 80.
The basic signup checks, and how each one breaks
So you try to stop the new accounts. A unique-email rule compares text, and one mailbox can have lots of spellings: Gmail ignores dots, and plus-tagged mail reaches the same inbox. That's how email works, and a second real mailbox only takes a few minutes anyway.
| Basic fix | What it catches | What it misses | Who it wrongly blocks | What it costs to keep working |
|---|---|---|---|---|
| Email verification | Typos and dead addresses | Any real second inbox | Songwriters whose code lands in spam | Sending and deliverability work |
| Disposable-domain blocks | Known throwaway services | New domains and ordinary mailboxes | People using privacy forwarding | A list someone updates forever |
| Gmail dots and plus addressing | One inbox written several ways | A second real mailbox | Bandmates sharing one inbox | Upkeep as mail services change |
| CAPTCHA | Simple scripts | People signing up by hand | People using screen readers or privacy tools | Fees and lost signups |
| Phone requirement | Casual second accounts | Anyone with another number | Young musicians without their own number | A charge for every text |
| Card requirement | Casual second accounts | Anyone with another card | Hobbyists after one song | Fewer signups |
| One per IP address | Repeat signups on one connection | Any other network | Studios, music schools and shared houses | Exceptions and tickets |
| VPN blocks | Known VPN ranges | Everything off your list | Privacy-minded artists on the road | Another list to maintain |
| Rate limits | Bursts from one account | 40 accounts under the limit | A songwriter retrying one chorus | Tuning per endpoint |
| Manual review | What a person can spot | Whatever renders before you look | Whoever looks odd to a tired reviewer | Hours every month |
No row in that table holds up for long. A disposable-domain list only knows the domains on it, CAPTCHA only slows scripts, and requiring a card loses the hobbyist too. Stack everything and that hobbyist confirms an email, solves a puzzle, types a phone number and enters a card before hearing a note. Review by hand, at a minute an account, is about 83 hours for 5,000 accounts (5,000 ÷ 60), and by the last account the songs left weeks ago.
All of that asks about the signup. The question that decides your GPU bill comes later, in the second before a render starts: should this claim go through?
Before the GPU starts
AbuseZero exists for that second, and we're proud of what it brings to it. It flags abuse that single checks miss and detects linked claims, with multi-layer AI risk analysis examining 140,000+ signals. AbuseZero uses a proprietary algorithm, with AI that checks the claim again. Your IP rule had one address to go on, and AbuseZero sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. Your email rules go stale, and AbuseZero checks mailbox aliases, disposable domains and mail routing. It recognizes repeat devices across new accounts, even when email addresses keep changing. Creating a fresh account isn't enough to erase previous activity, in a product where a fresh account is all a free pack has ever asked for.
Your server makes one API call before it grants the credits and gets a clear allow or deny, under rules you control. Hold the credits on a deny, and no GPU seconds start and there's no WAV to chase. Eligibility lets a one-time free pack and a monthly refresh carry different limits, Observe mode shows you what would be denied before anyone is blocked, and the quickstart walks you through your first benefit. You don't have to build your own abuse prevention system beside your render queue. Your app still runs the queue, the budget and the downloads.
Frequently asked questions
Can I take back a free track after banning the account?
Not in any practical way. You can remove access and delete your copy, and the file someone downloaded stays with them. That's why the decision has to come before the render.
Should a free plan on an AI music app allow downloads?
Only if downloads are how free users become paying ones. Test it on your own numbers, because a track someone can share may be your best advertising and your biggest reason to be farmed.
Is every second account on a music app abuse?
No. A producer may keep one account for clients and another for their own songs. Write down what you mean to give each person before you enforce it, and if you use AbuseZero, its rules should match that policy.
Protect your next free pack
Start with Builder
Pay as you go. Evaluate your first claim today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High volumes and custom terms.