Connection Methods
Choose how the agent connects to a browser
Ev3ry needs a browser to visit websites and extract data. Three providers are supported, each with different trade-offs.
Overview
| Method | Engine | Privacy | Setup | Best for |
|---|---|---|---|---|
| Built-in browser | Firefox (Camoufox) | Data stays on your machine | Install locally | Sensitive data, anti-detection |
| BrowserBase | Chromium | Third-party hosted | API key | Cloud convenience, fast setup |
| Browserless | Chromium | Third-party or self-hosted | API key or Docker | Budget option, self-hosting |
Choosing a method
Use the built-in browser if:
- You extract data from authenticated pages with sensitive accounts
- The target site uses aggressive bot detection (Cloudflare, DataDome, etc.)
- You want full control over where your browsing activity goes
Use a cloud browser if:
- You want zero local installation
- You don't handle sensitive authentication sessions
- You're running extractions from a server or CI environment
Use Browserless self-hosted if:
- You want cloud convenience but on your own infrastructure
Configuring your default
Go to Settings > Browser to set your default connection method. You can override this per-website in the website settings, or per-run when you click Run.
app.ev3ry.io/settings/browser
Browser
Configure browser engine for learning sessions
Fast — DOM is ready
Local
Firefox-based anti-detection browser — included with Ev3ry
Local Camoufox (Optional)
Run Camoufox on your own machine and expose it via a tunnel. Leave empty to use the included server.
Live view differences
Both local and cloud browsers show a live view during runs, but the implementation differs:
- Built-in browser — polling-based screenshots (updates every ~500ms). The extraction itself runs at full speed; only the visual feed is polling-based.
- Cloud browsers — real-time iframe embed from the provider. Typically updates faster, but depends on the provider's infrastructure.