Per user or per workspace: where should free limits sit?
Free plan limits per workspace or per user? Compare what one person can collect under each, what real teams get, and which basic checks hold up.
All morning the export queue on your admin screen has been climbing, when it's meant to sit near zero. Then your co-founder sends you this: "Our biggest customer says exports are taking an hour and a half. I told them we're on it. While I've got them, how many actual people are on our free plan? I don't mean accounts or workspaces. People."
You start typing "about 3,000" and then you delete it. 3,000 is how many active free workspaces you have, and it's the only number you've got.
You set free plan limits per workspace when you launched, because it felt fair to teams: every free workspace gets 300 runs a month. Stay with this scenario and check the arithmetic against your own product. Your workers clear 2,000 runs an hour. Say every free workspace uses its allowance at a steady pace around the clock, and paying customers are busiest from 9 a.m. to 1 p.m.
Free load: 3,000 workspaces x 300 runs = 900,000 runs a month
900,000 / 720 hours = 1,250 runs an hour
Paying load: 1,500 runs an hour at peak
Total: 2,750 runs an hour, against 2,000 of capacity
Backlog: 750 x 4 hours = 3,000 runs waiting by 1 p.m.
The wait: 3,000 / 2,000 = 1.5 hoursSo the customer who pays you $1,400 a month clicks export at 1 p.m. and gets the file around 2:30. Their renewal is six weeks away, $16,800 a year, and their exports sit in the same queue as every free workspace you've ever given out.
You sort free workspaces by owner to see who's ahead of them. The top account has 40. So does the next one. You keep scrolling and count 60 accounts like that, every workspace under its limit.
- 60 accounts × 40 workspaces = 2,400 of your 3,000 free workspaces
- 40 × 300 runs = 12,000 runs per account every month, four times the 3,000 runs in your $49 plan
Your co-founder's question just got harder, because 60 accounts might not be 60 people.
Now price it. One worker clears 250 runs an hour and costs $620 a month, so the free load takes 5 workers, or $3,100 a month. Those 60 accounts hold 80% of the free workspaces, which makes them $2,480 a month and $29,760 a year. That's more every month than your biggest customer pays you. At a $25,000 monthly burn, a year of that is about 1.2 months of runway.
By 2 p.m. you've got two options and you hate both. You can buy capacity: 2,750 ÷ 250 is 11 workers, 3 more than you have, for another $1,860 a month to keep serving those accounts. Or you can cut the limit to 100 runs. Your other 600 free workspaces lose two-thirds of what they signed up for, while those 60 accounts just need 120 workspaces each instead of 40. You wrote your launch post about that free plan, and almost every paying customer started on it. Your co-founder's next message is short: "Do we cut free?"
Why every free limit leaks through the thing it counts
A limit needs a unit, such as an account or a workspace. The allowance attaches to that unit, so anyone who wants more of it makes more of the unit. You meant to give something to a person or a team, and your database can only give it to a row.
Making those rows cheap was the right call. You want someone working within two minutes, so a signup takes one email and a new workspace takes one click. Each of those choices also sets the price of the next allowance. The obvious fix is to move the limit to the other unit. That changes what another allowance costs and who pays for the change, so compare the two before you migrate anything.
Free plan limits per user vs per workspace
| Question | Per user | Per workspace |
|---|---|---|
| What earns another 300 runs? | A new account | A new workspace |
| What does that take? | An inbox and a signup | One click on the same account, unless you cap it |
| What does a team of 5 members get? | 5 × 300 = 1,500 runs | 300 runs, shared |
| How hard does the limit push a team to upgrade? | Weakly, because the plan grows with the team | Firmly, because the team shares one ceiling |
Your exposure under either model comes down to one sum:
Run those 60 accounts through it, counting each as one person. With no cap on workspaces, 60 × 40 × 300 is 720,000 runs a month, 80% of your free load, from 60 inboxes. With one free workspace per account, the same runs take 2,400 accounts, which is what per-user limits would ask for too. A capped workspace limit and a user limit therefore charge the same price for another allowance: one more signup.
Where they part ways is honest teams. A team of 5 members gets 1,500 runs under per-user limits and 300 under per-workspace limits. The per-user plan costs you five times as much for that team and gives them less reason to buy.
Our pick depends on the product:
- Most team products: per workspace, with one free workspace per account. Usage stays bounded, and a team at its ceiling has a reason to upgrade.
- Products people use alone, such as an AI assistant or a personal API key: per user, because there's no shared workspace to meter. If you have workspaces anyway, add a total per workspace so a new member doesn't add runs.
- Per workspace with no cap: the most exposed setup here, because the next allowance doesn't involve a signup at all.
The placement is our judgment. Whichever model you pick, do these next.
Allow one free workspace per account. Count every free workspace an account has ever created, so deleting one doesn't hand back a slot. There's more on limits that survive a new workspace.
Reserve capacity for paying customers. In this scenario, seven of your eight workers (1,750 runs an hour) take paid work first, and free runs use whatever's left. The 1,500 paying runs at peak now clear without a backlog. Free runs wait instead.
Decide what people see at the limit. Show the limit, the date it resets and the plan that raises it.
The basic checks teams add, and how each one breaks
A one-workspace cap makes a new account the price of another allowance, so the question moves to signup. Most of these checks run only there, which means a new workspace on an existing account never touches them.
Unique emails usually come next. They catch the same address twice and wrongly block almost nobody, but they compare text, and one inbox can have many spellings: Gmail ignores dots in personal addresses, and mail with a plus sign and any word before the @ reaches the same inbox. Aliases like these are simply how email works.
| Basic check | What it catches | What it misses | Who it wrongly blocks | What it costs to keep |
|---|---|---|---|---|
| Email verification | Typos and dead addresses | Any second real inbox | People whose code lands in spam | Deliverability work |
| Disposable-domain blocks | Known throwaway services | New domains and normal mailboxes | People using privacy forwarding | A list that never ends |
| CAPTCHA | Simple scripts | Someone signing up by hand | People on screen readers | Fees and lost signups |
| Phone or card requirement | Casual extra accounts | Anyone with another number or card | Students, people trying before buying | Text charges, fewer signups |
| One account per IP | Repeats on one connection | Any other network | Real teams in one office | Tickets and allowlists |
| VPN blocks | Known VPN ranges | Everything off your list | Staff on company VPNs | Another list |
| Rate limits | Bursts from one account | 60 accounts under the limit | Real teams in a busy hour | Tuning per endpoint |
| Manual review | What a person can spot | Anything spread over weeks | Whoever looks odd that day | Hours, every month |
The cheap ones are worth keeping. Look at who gets hurt, though. A one-per-IP limit lands on 5 members of a real team in one office, the people you most want on a workspace. Rate limits count requests, so 60 accounts that stay under them look like 60 customers. Reviewing 2,400 workspaces at a minute each is 40 hours, and next month's new workspaces need the same.
Add them up and you've got a cap, a domain list, a puzzle on your form and a spreadsheet of allowed IP addresses, and your co-founder's question still has no answer. None of them can tell you whether this person already took this allowance under another name.
Deciding who gets the next free workspace
Whether this claim should go through is the question AbuseZero answers, and it goes well past anything in that table. Before a free workspace or a monthly allowance goes out, your server makes one API call and gets a clear allow or deny, under rules you control. AbuseZero puts 140,000+ signals through multi-layer AI risk analysis, which detects linked claims and flags abuse that single checks miss. Those signals are read together, never one at a time. There's also a proprietary algorithm, with AI that checks the claim again.
Your one-workspace cap ends at a new inbox. AbuseZero recognizes repeat devices across new accounts, even when email addresses keep changing, and creating a fresh account isn't enough to erase previous activity. Your IP limit sees an address and stops there, while AbuseZero sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. It checks mailbox aliases, disposable domains and mail routing as well, so nobody at your company has to keep that list. You don't have to build your own abuse prevention system.
Set eligibility for each benefit, such as once per user or once per calendar month, and start in Observe mode to see what would be denied before anyone is blocked. The quickstart covers your first benefit.
Frequently asked questions
Are free plan limits better per user or per workspace?
For most team products, per workspace, with one free workspace per account. Per user suits products people use alone. See setting free plan limits that don't invite extra accounts.
Does one free workspace per account stop extra accounts?
No. It raises the price of another allowance from a click to a signup. AbuseZero evaluates the claim itself, so you get allow or deny whichever account is asking.
What about freelancers and agencies who need several workspaces?
Let them ask for a second free workspace, or offer a plan that includes several, and put that in your one account per person policy.
Keep the free plan and the fast queue
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.