I'm trying to understand what fake or repeat signups actually cost a small product, and what people can do to limit them. Are there simple checks to add at signup, or is it better to change the free tier itself?
How do you keep free-tier signups from getting abused?
Answers
Start with the cost, not the signup count. Extra accounts that use a little storage may be cheap enough to monitor, while accounts burning AI credits, SMS or compute can eat into your margins quickly.
Estimate the cost of a suspicious account and compare it with what you spend to acquire a genuine user. That gives you a better idea of how much friction and engineering the problem is worth. Abuse may also arrive in bursts, so a single average percentage can hide the expensive days.
Reply to this answer
Put a hard budget on the free tier across the whole product, not just a limit on each account. A per-account cap doesn't help much if someone can create hundreds of accounts.
You can also make the initial allowance small and unlock more after email verification or setup. A card requirement is another option, though it'll add friction for legitimate users too.
Reply to this answer
For a basic signup flow, email verification, disposable domain checks and rate limits are reasonable places to start. You can flag clusters of signups from the same network for review rather than automatically treating every shared IP as abuse.
Some of that can be added through existing services rather than built from scratch. The useful thing to look for is whether a service can return a signal to your backend before you grant costly credits. No single check will reliably separate every genuine user from every repeat account.
Reply to this answer
The kind of product matters a lot. A limited feature set is different from handing out credits for something with an obvious resale value. If the free allowance is worth more than the effort of opening another account, expect people to try.
Changing when and how much value you give away may do more than stacking signup checks. Delay expensive features until a user has completed setup, for example, and keep the initial allowance modest.
Reply to this answer
For a business product, you might have a stronger identifier than an email address. If the product serves registered companies, one free account per verified company tax ID could make repeat signups harder. That won't fit consumer products or every business, though.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_q45+drandelo.7:
That makes sense. The product-wide cap seems useful even if signup checks miss something.