4 ms·
> the goal is to get rid of users that don't pay anything but send 12k emails per month I agree, but you even understate the problem. If your API-based SaaS of
by derefr 11y ago
> the goal is to get rid of users that don't pay anything but send 12k emails per month
I agree, but you even understate the problem. If your API-based SaaS offers a free plan, then you can't actually enforce any caps on that plan. Anyone who uses your service can just register N free accounts and multiplex their load across them, to get as much usage out of your SaaS as they like. (Yes, even if you make them register with a credit card and deduplicate by card number; registering a bunch of Visa gift cards that don't have to maintain a balance is essentially "free.") The only real way to get around this—besides eliminating your free plan—is full-on "submit your birth certificate" KYC.
Of course, this doesn't apply if your SaaS is delivered as a web service or a fancy thick client, where the raison d'être is mostly in the UX—it's hard to multiplex that. But when your service is just an API, it's dead simple.
- mangeletti 11y agoIt's not about sealing a security hole. It's about increasing the cost and decreasing the value for abusers, to reduce the amount of abuse to a sustainable level.