# Joel Griffith - Browserless Source: https://www.youtube.com/watch?v=xgSUJb4rulw Recap page: https://rapidrecap.app/video/xgSUJb4rulw Generated: 2026-02-16T08:03:45.715+00:00 --- ## Quick Overview Joel Griffith, founder and CEO of Browserless, discusses how the challenges of web scraping and the subsequent realization that many web automation tools rely on outdated or non-compliant practices led him to create Browserless, a browser-as-a-service solution that simplifies web automation by handling complexities like security and rendering consistency. **Key Points:** - Joel Griffith founded Browserless to address the difficulties developers face with web scraping and automation. - Early web automation often involved manually dealing with issues like inconsistent browser behavior, security verification, and outdated components. - Browserless functions as a browser-as-a-service, abstracting away complexity so users can focus on defining the desired outcome. - The motivation stemmed from personal frustration, such as dealing with Google's frequent changes to indexing/scraping rules (like Puppeteer/headless Chrome limitations). - A key feature is providing a stable, containerized environment (like Docker) for browser automation, ensuring consistent behavior across different environments. - Griffith notes that while AI is advancing, there is still a need for structured, reliable browser automation tools, especially for tasks involving complex, real-world web interactions. - The company prioritizes maintaining compatibility with various browser engines (Chrome, Firefox, WebKit) to ensure broad functionality. ![Screenshot at 00:14: The DevTools.FM podcast introduction screen, establishing the context of the interview about developer tools and the people who build them.](https://ss.rapidrecap.app/screens/xgSUJb4rulw/00-00-14.jpg) **Context:** Joel Griffith, founder and CEO of Browserless, joins the DevTools.FM podcast hosted by Andrew Lisowski to discuss the origin and purpose of his company, Browserless. Griffith explains that his journey into creating this service was driven by the frustrations he experienced while trying to automate web tasks, particularly dealing with the opacity and frequent changes in how major platforms (like Google) handle automated traffic. He contrasts the older, manual ways of solving these problems with the modern, containerized solution Browserless offers. ## Detailed Analysis Joel Griffith, founder and CEO of Browserless, explains that he started the company because traditional web scraping and automation methods were frustrating for developers. He recalls that when he first encountered web automation issues while working on websites for bands and music stores around 2012, the lack of reliable tools forced him to write his own solutions, which often resulted in constant maintenance due to underlying browser changes. The major turning point came when he realized that even popular tools like Puppeteer/headless Chrome required complex workarounds (like manually floating elements, clearing data, or dealing with inconsistent API behavior) to function reliably, especially when dealing with things like security checks or federal compliance sites. This led to the creation of Browserless, a browser-as-a-service that runs automation in a controlled, containerized environment. He emphasizes that Browserless provides a stable environment, often using managed Docker images that handle updates and complexities, allowing users to focus on the desired outcome (e.g., getting data, checking prices, taking screenshots) rather than debugging environment differences. Griffith notes that while AI is emerging, there's still a significant need for tools that provide reliable, consistent execution of web tasks, especially given the constant cat-and-mouse game with platforms trying to block automated traffic. He also mentions the importance of supporting multiple browser engines (Chrome, Firefox, WebKit) and having clear documentation for routes and schemas, contrasting this with the difficulty of relying on proprietary or poorly documented systems. ### Origin of Browserless - Frustration with web scraping complexity - Realizing the pain points in web automation, such as dealing with inconsistent rendering and security checks (like those from Google). ### The Browserless Solution - Offering a managed browser-as-a-service built on Docker to provide a stable, consistent environment for automation tasks. ### Key Technical Benefits - Abstracting away complexities like handling CSS/HTML5 parsing, security checks (SSL/HTTPS cookies), and multi-threading issues inherent in running browsers locally. ### Open Source Philosophy - Highlighting the importance of open source components, like providing open, documented GraphQL schemas, even while maintaining commercial viability. ### Future Outlook - Acknowledging that while AI is growing, there is still a need for reliable, structured browser automation tools, and hoping Browserless continues to simplify this space. ![Screenshot at 00:00: Joel Griffith, founder of Browserless, speaking into a microphone during the podcast introduction.](https://ss.rapidrecap.app/screens/xgSUJb4rulw/00-00-00.jpg) ![Screenshot at 00:14: The DevTools.FM podcast branding screen, setting the context for the interview.](https://ss.rapidrecap.app/screens/xgSUJb4rulw/00-00-14.jpg) ![Screenshot at 00:25: Co-host Andrew Lisowski introducing Joel Griffith.](https://ss.rapidrecap.app/screens/xgSUJb4rulw/00-00-25.jpg) ![Screenshot at 00:36: Joel Griffith explaining the initial frustrations with web scraping requiring manual workarounds.](https://ss.rapidrecap.app/screens/xgSUJb4rulw/00-00-36.jpg) ![Screenshot at 02:22: Andrew Lisowski describing the shift from jazz trombonist to developer, illustrating his background.](https://ss.rapidrecap.app/screens/xgSUJb4rulw/00-02-22.jpg)