jeffersoncgo/flaresolverr-bridge repository overview

FlareSolverr Bridge is a lightweight, high-availability proxy that sits in front of multiple FlareSolverr instances — turning them into a resilient, distributed solving cluster. Instead of relying on a single point of failure, your scraping or automation requests are intelligently routed through all configured targets. The bridge returns the first successful response from any healthy instance, ensuring maximum uptime and performance.

Perfect for production-grade web scraping, automation pipelines, or any application requiring robust CAPTCHA and Cloudflare bypass capabilities, FlareSolverr Bridge adds redundancy, load distribution, and real-time monitoring — without changing your existing code.

🔗 Available on Docker Hub: jeffersoncgo/flaresolverr-bridge⁠

⁠✅ Key Features

• Automatic Failover: Requests are sent to all configured FlareSolverr endpoints simultaneously — the first successful response wins.
• Real-Time Monitoring: View live status, latency, and uptime of each target directly in the built-in web UI.
• Dynamic Target Management: Add, remove, or update FlareSolverr instances on-the-fly via the intuitive dashboard.
• Zero Code Changes Required: Simply point your app to the Bridge endpoint — it speaks the exact same API as FlareSolverr.
• Lightweight & Fast: Minimal overhead with near-zero latency penalty.
• Docker-Native: Easy deployment via docker run or Docker Compose — scales seamlessly with your infrastructure.

⁠🖥️ Dashboard

The clean web interface lets you manage your distributed FlareSolverr fleet in real time. Add new targets with one click, view their current status (green = online), response latency (e.g., “18 ms”), and uptime since last connection. A trash icon allows quick removal of failed or outdated instances — keeping your cluster lean and responsive.

⁠🚀 Use Cases

• High-availability scraping clusters across multiple servers or regions
• Load balancing heavy automation workloads across multiple FlareSolverr containers
• Avoid downtime during maintenance or unexpected crashes
• Monitor and optimize solver performance by comparing latencies across nodes

⁠🛠️ Quick Start

docker run -d -p 8191:8191 --name flaresolverr-bridge jeffersoncgo/flaresolverr-bridge:latest

1. Visit http://localhost:8191 to access the dashboard.
2. Add your FlareSolverr instances (e.g., http://10.0.0.6:8191, http://192.168.1.212:8191).
3. Point your scraper tools (Puppeteer, Playwright, Scrapy, etc.) to http://localhost:8191/v1 — just like a regular FlareSolverr!

⁠💡 Why Use This?

Stop worrying about single points of failure. Scale your scraping infrastructure with confidence.

✅ Get it now on Docker Hub:
👉 https://hub.docker.com/r/jeffersoncgo/flaresolverr-bridge⁠