Announcing BrowserQL, our next-gen automation tooling #4413
zach-browserless
announced in
Announcements
Replies: 1 comment
-
|
Did you consider adding an SDK for BrowserQL? I checked the website and it seems like the anticipated usage is to send strings. Which makes it harder to manage in case of any logic. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We’re very excited to announce that BrowserQL is now live! It’s our fully revamped approach to browser automation.
It comes from our frustrations with Playwright and Puppeteer, which aren’t designed to be stealthy. We found ourselves constantly having to modify their behavior to hide signs of automation.We ended up creating our own internal tools to directly interact with the browser via Chrome DevTools Protocol. As is often the way, those tools have morphed into a full standalone product.The result is BrowserQL, a dedicated query language and scraping IDE. As a quick summary:
It comes from our frustrations with Playwright and Puppeteer, which aren’t designed to be stealthy. We found ourselves constantly having to modify their behavior to hide signs of automation.
We ended up creating our own internal tools to directly interact with the browser via Chrome DevTools Protocol. As is often the way, those tools have morphed into a full standalone product.
The result is BrowserQL, a dedicated query language and scraping IDE. As a quick summary
For the full details, check out the announcement article here:
Announcing BrowserQL, our next-gen scraping tool
As much as we'd love to make it open source, we don't want to make our stealth strategies easily available for the devs at Cloudflare/Datadome to analyse, so it is going to stay closed-source until further notice. To test it out, you'll need to grab a trial.
Beta Was this translation helpful? Give feedback.
All reactions