[mrweasel]

How do you deal with abuse? We recently had to block all of Browserbase, because someone used their platform for AI training. Generally we're fine with scrapers, but we're not equipped to handle the amount of traffic that some of the browser automation sites can generate.

It really sucks to block an entire service, just because a few of its users can't control themselves. At the same time a lot of SaaS providers makes it impossible to report a single user/tenant and getting a paying user banned just isn't happening.

[marcon680]

Generally our use cases are completely different -- if a user is doing scraping, it's been structured scraping on a small (<50) set of sites where they need to be able to pull data from a website as if it was an API call, not as a way to web-crawl and get masses of training data.

We gate full access to the platform partially for this reason. We debated giving fewer than 50 free browser sessions, for example, and have already banned a few accounts from our self-serve today that were unidentifiable/"company accounts" without a legitimate web presence.

[mrweasel]

That is nice, so many companies don't stop to think how their product might be abused. Love to see that you've given it some thought.

One think I might add: limit how many requests per second your clients can make. Even if they can just scrape a small set of sites, they can still hammer a site into the ground. One of the things I think Google has been doing really well since their start is knowing when to back of a site. So either rate-limit your clients, or back of a site if you see responses slowing down.

We just had a company hit one of our sites pretty heavily, and when asking them of back off a bit, they just asked if we could perhaps rate-limit them. Apparently they don't know how to reduce their traffic themselves.

[pkiv]

Hey there! Founder of Browserbase here. If you're seeing any abuse from one of our customers we'd love to hear more. Mind sending more info to [e-mail]?