FlareSolverr is a proxy server designed to bypass anti-bot and DDoS protection from Cloudflare and DDoS-GUARD. It operates by starting a proxy server and waiting for user requests. When a request is received, it uses Selenium with undetected-chromedriver to launch a headless browser (Chrome). This browser navigates to the requested URL, automatically solving the security challenges. Once the challenge is cleared, the HTML code and the necessary cookies are sent back to the user. These returned cookies can then be used with other HTTP clients to access the protected content directly. It supports both temporary and permanent user sessions. Note: Use http://flaresolverr_server_1:8191/v1 as the URL for integration with other applications.
License: MIT. Built with: Python, HTML, Dockerfile. Website: https://github.com/FlareSolverr/FlareSolverr. Source: https://github.com/FlareSolverr/FlareSolverr.
docker run -d \ --name=flaresolverr \ -p 8191:8191 \ -e LOG_LEVEL=info \ --restart unless-stopped \ ghcr.io/flaresolverr/flaresolverr:latest
Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.
Most self-hosted apps run comfortably on modest hardware — a Raspberry Pi 4, a mini PC, a NAS with Docker support, or a small VPS is usually enough for personal or family use. CPU and RAM requirements scale with how many simultaneous users or how much data you push through flaresolverr. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.