Back to Blog

How to stop users creating new workspaces to reset free limits

When a new workspace means a fresh free allowance, paying customers end up waiting. How to make limits hold, and which basic fixes break first.

Last quarter you told your investors active workspaces was the one number to watch. Say it's Tuesday morning, and you've got that chart open because it's the nicest thing on your screen. Active workspaces went from 2,000 to 2,760 this quarter, up 38%, and you're about to paste it into the investor update.

Then you click into the 760 new ones and sort by owner. One login owns 51 workspaces. The next owns 47. Keep scrolling and 15 logins own 660 of the 760, about 44 each, and every one of those workspaces used all 300 of its free runs last month. Take them out and your quarter is 100 new workspaces, which is 5%. If you typed reset free limits new workspace into a search box this week, you've probably seen a chart like this one.

This is a scenario, so check the numbers against your own. Each free run costs you $0.02 in compute:

  • 15 people × 44 workspaces = 660 workspaces
  • 660 × 300 runs = 198,000 runs a month
  • 198,000 × $0.02 = $3,960 a month
  • $3,960 × 12 = $47,520 a year

That $3,960 is about what 81 customers on your $49 plan pay you each month (81 × $49 = $3,969). If your company spends $20,000 a month, the year's total is 2.4 months of runway, handed to 15 people who've never paid you.

You'll notice the money last, though. Your workers clear 75 runs a minute, and at peak your real users need 60, so normally nobody waits. Those 198,000 runs mostly land between 9 a.m. and 2 p.m. on 22 working days: 198,000 ÷ 22 ÷ 300 minutes = 30 runs a minute. Now 90 arrive, 75 leave, and the line grows by 15 a minute with your paying customers in it.

TimeRuns waitingWait for a new run
9:00 a.m.0None
10:00 a.m.90012 minutes
11:00 a.m.1,80024 minutes
12:55 p.m.3,52547 minutes
2:00 p.m.4,50060 minutes

At 1:44 p.m. your biggest account writes in. They're on the $499 plan, and people on that plan run the most work at the busiest hours, so they feel every minute of this. "Our report normally takes under a minute. I started it at 12:55 and it finished at 1:42, with a client on the call. Is this how it works now?"

You credit their month, another $499. If they leave anyway, that's $5,988 a year ($499 × 12). The next customer this happens to won't write in at all. They just won't renew, and the cancel form won't say why.

By 4 p.m. you've got a draft open that you never wanted to write. You launched with 300 free runs and no card, and you were proud of that, because most of your paying customers started there. Cutting it to 60 would bring the bill down. It would also take 80% of the plan from everyone using it honestly, while those 15 people would only need five times as many workspaces (300 ÷ 60 = 5), or 220 each. The free plan that found you your customers is now the thing you have to cut, and your best customers spent the day waiting behind it.

Why a new workspace resets free limits

Most apps keep the usage counter on the workspace, because that's where the plan and the members live. A new workspace gets a new row, and a new row starts at 0. In some apps the counter is deleted along with the workspace, so even deleting and recreating one starts the count again.

loop[Every time the limit is hit]Create a workspaceNew counter at 0Use 300 free runsLimit reachedUpgrade promptOne personYour appUsage counterOne personYour appUsage counter
loop[Every time the limitis hit]Create aworkspaceNewcounter at0Use 300free runsLimitreachedUpgradepromptOnepersonYour appUsagecounterOnepersonYour appUsagecounter

Nothing about the 44th workspace looks wrong, because creating workspaces is supposed to be easy. Agencies, consultants and freelancers really do need several, which is why where your free limits sit matters more than how high they are.

The obvious fix is a cap on workspaces per login, and you should add one. It holds for as long as a second login takes to create. Your 15 logins can become 660 logins with one workspace each, and your sort by owner comes back empty. So you need a limit that a new workspace can't reset, and then you need to know how far that limit reaches.

How to stop a new workspace resetting free limits

Measure it first. This query shows who holds the most free workspaces:

free_workspaces_by_owner.sql
select owner_id,
       count(*)       as free_workspaces,
       sum(runs_used) as runs_used
from workspaces
where plan = 'free'
group by owner_id
having count(*) > 3
order by runs_used desc;

Read the top of the list by hand before you act on it. Your agencies will be in there.

Move the counter to the owner's account. Give each account one free allowance a month, shared across every free workspace it owns, in a table keyed on account and month. Nothing that happens to a workspace touches that table, so creating or deleting one changes nothing. In the scenario, 44 workspaces now share 300 runs, and the 15 logins drop from 198,000 runs a month to 4,500 (15 × 300).

Charge a member's runs to the workspace owner. Then being invited to a free workspace doesn't bring anyone a second allowance.

Cap free workspaces per account, at one to three. Put the reason in the error and give people who need more a paid plan or a way to ask. Write the rule down first.

Split the queue. Say paid plans need 45 of your 75 runs a minute at peak. Reserve those 45 for paid work and let free runs share the other 30, with a daily budget on top. The bad morning from the table above now backs up the free queue only. Honest free users still wait, but the $499 report takes under a minute.

YesNoNoYesNoYesRun requestedOn a paid plan?Paid queueOwner has free runs left?Offer a paid planFree budget left today?Try again tomorrowFree queue
YesNoNoYesNoYesRun requestedOn a paid plan?Paid queueOwner has free runs left?Offer a paid planFree budget left today?Try again tomorrowFree queue

Email existing owners before you switch, and read up on setting free limits that don't invite extra accounts before you pick a number.

The basics that try to stop a second account

All of that makes the limit follow the account. A new account still starts at 0, with nothing on paper tying it to the last one. Here's what most teams try next, and how each one holds up.

Email verification and unique emails. Verification catches typos and dead addresses, and a unique rule catches the same address used twice. Neither does anything about a second real inbox, and verification only proves someone can open one. Real people get caught when their code lands in spam.

Disposable-domain blocks. These stop known throwaway services and miss every domain that isn't on the list yet. They also turn away people who use privacy forwarding, and somebody has to update the list forever.

Gmail dots and plus addressing. Gmail ignores dots, so jane.doe@gmail.com and janedoe@gmail.com reach one inbox, and mail to jane+anything@gmail.com lands there too. That's how email works. Treating those as one person catches a lazy repeat and misses a different mailbox.

CAPTCHA. It stops simple scripts. A person opening accounts by hand clears it in seconds, while people using screen readers or privacy tools can get stuck. You pay in fees and lost signups.

Phone or card requirements. Both catch casual second accounts and miss anyone with another number or card. Students and people without a reliable mobile number get shut out, every text is a charge, and "no card" was the promise your free plan launched on.

One per IP and VPN blocks. A one-per-IP rule catches repeats on one connection and misses every other network. It also lands on the wrong people, since companies and agencies sharing one address are who create workspaces. VPN blocks stop known ranges, turn away staff on company VPNs and add another list to maintain.

Rate limits and usage caps. A limit on workspace creation catches 44 in a minute and misses 44 in a month, and it trips when an agency sets up ten clients in an afternoon. A usage cap stops one account overrunning, and each new account gets a fresh one.

Smaller allowances and shorter trials. You lower the cost per account, every honest user pays for it, and more accounts make up the difference.

Manual review. A person can spot what a rule can't, for as long as they're awake. At one minute per workspace, 660 is 11 hours, due again next month, and whoever looks odd to a tired reviewer gets turned away.

Stack all of these and your signup asks for a verified email, a puzzle, a phone number and a card, from the people your free plan was meant to welcome. You'd still have two lists to maintain and a review queue.

Stopping the reset when the account is new

This is the job AbuseZero was built for, and it picks up where that list ran out. Your counter now follows the account, so what's left to answer is whether this claim looks like a repeat, and creating a fresh account isn't enough to erase previous activity in AbuseZero. With multi-layer AI risk analysis, AbuseZero examines 140,000+ signals, detects linked claims and flags abuse that single checks miss. Signals are read together, never one at a time. There's also a proprietary algorithm, with AI that checks the claim again. Your unique-email rule stopped at the inbox. AbuseZero checks mailbox aliases, disposable domains and mail routing, and recognizes repeat devices across new accounts, even when email addresses keep changing. Your IP rule locked out an office. AbuseZero sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence.

You treat the free plan as a benefit and make one API call before a new account gets its allowance, and you get a clear allow or deny under rules you control. Eligibility can be once per user or once per calendar month. Observe mode shows you what would be denied before anyone is blocked. You don't have to build your own abuse prevention system, and the quickstart protects your first benefit.

Frequently asked questions

Should free limits be per workspace or per account?

Count free usage against the account that owns the workspace. Limits per workspace reset whenever someone makes a new one.

Is having several free workspaces abuse?

No. Agencies and consultants have good reasons. Abuse is using extra workspaces to collect more than you meant to give one person. Account sharing is a different problem.

What about a new account with a new email?

Your own counter starts at 0 for that account, so you need something that looks further. AbuseZero's evaluation returns allow or deny before the allowance goes out.

Keep the free plan you were proud of

Keep reading

Copying your prompt…

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