Gaffa

Gaffa is a REST API designed for developers, entrepreneurs, and product managers who need scalable browser automation without complex setup. It offers a simplified interface to control real browsers programmatically, eliminating the need to manage proxies, headless browsers, or automation frameworks.

What Makes Gaffa Stand Out

• Real Browser Automation: Executes actions in fully rendered browsers with JavaScript support, avoiding typical headless browser quirks.
• Framework Abstraction: Removes the learning curve of tools like Playwright, Selenium, or Puppeteer by providing a single REST API for all automation needs.
• Proxy Integration: Includes residential proxy support for reliable global web access, handling proxy complexities internally.
• Data Processing Options: Converts web pages into simplified HTML, markdown formatted for large language models (LLMs), or self-contained offline pages.
• Full Observability: Records automation sessions, allowing users to review the exact browser interactions.

Who Should Use Gaffa

• Developers needing to scrape or ingest web data into AI or LLM applications without handling proxy or scaling challenges.
• Startups seeking automated web data gathering with a manageable, credit-based pricing model.
• Teams requiring automated browser tasks such as printing, screenshot capture, or web content extraction.

Frequently Asked Questions

What is Gaffa?

Gaffa is a REST API focused on browser automation that allows users to control real browsers at scale simply by making API calls. It is designed to streamline web data scraping, automated browser tasks, and data formatting for downstream AI applications.

What makes Gaffa suitable for AI and data scraping projects?

Because Gaffa operates real browsers with JavaScript rendering, it can more accurately retrieve dynamic web content. Combined with proxy management and formatting outputs into markdown or offline files, it's well-tailored for feeding web data into AI models or large language models.

What are the limitations of using Gaffa?

Requests consume credits based on duration and data usage, which can add up for long-running tasks or high bandwidth proxy usage. Additionally, credit balances do not roll over monthly, so unused credits expire. The service requires a paid plan to access live web automations beyond the demo environment.

What alternatives exist to Gaffa?

Alternative browser automation solutions include direct use of browser frameworks like Selenium, Playwright, or Puppeteer. Unlike Gaffa, these require manual proxy and scaling configuration. Some platforms offer headless browser automation but may lack integrated proxy management or real-browser rendering fidelity.

How is credit usage calculated?

Credits are spent based on the length of each browser request and proxy bandwidth usage. For example, one credit charges each 30 seconds of runtime per request, doubled if screen recording is enabled. Proxy bandwidth is charged at a set credit rate per GB used, affecting total consumption.