head to head · open source

Scrapegraph-ai vs proxy_pool

Scrapegraph-ai has 32,439 GitHub stars, 3,313 forks, 16 open issues and last shipped 28 days ago. proxy_pool has 23,778 stars, 5,418 forks, 298 open issues and last shipped 5 months ago. Scrapegraph-ai leads on adoption by 36% (32,439 vs 23,778 stars). Scrapegraph-ai is written in Python under MIT; proxy_pool is written in Python under MIT. Scrapegraph-ai has attracted 10% as many forks as stars, proxy_pool 23%. Scrapegraph-ai was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (crawler), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

Scrapegraph-ai ★ 32K proxy_pool ★ 24K category Data & Analytics

← all 20902 open source comparisons

Side by side

Scrapegraph-ai proxy_pool
GitHub stars ★ 32K ★ 24K
License MIT MIT
Written in Python Python
Last push 2026-10-06 2026-06-15
Forks ⑂ 3.3K ⑂ 5.4K
Self-hosting Yes Yes
Data ownership Your server Your server

pick Scrapegraph-ai if

  • You weight community size — 32K stars and counting
  • You want the MIT license terms
  • Your stack matches Python
  • You value the larger contributor base for long-term maintenance

full Scrapegraph-ai profile →

pick proxy_pool if

  • You want the proxy_pool feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches Python
  • You evaluated both and proxy_pool fits your workflow better

full proxy_pool profile →

About Scrapegraph-ai

🚀 Looking for an even faster and simpler way to scrape at scale (only 5 lines of code)? Check out our enhanced version at ScrapeGraphAI.com ! 🚀 🕷️ ScrapeGraphAI: You Only Scrape Once English 中文 日本語 한국어 Русский Türkçe Deutsch Español français Português Italiano ScrapeGraphAI is a web scraping python library that uses LLM and direct graph logic to create scraping pipelines for websites and local documents (XML, HTML, JSON, Markdown, etc.). Just say which information you want to extract and the library will do it for you! 🚀 Integrations ScrapeGraphAI offers seamless integration with popular frameworks and tools…

read the full Scrapegraph-ai overview →

About proxy_pool

ProxyPool 爬虫代理IP池 ======= ( ) 0: try: html = requests.get(' proxies={"http": " 使用代理访问 return html except Exception: retry count = 1 删除代理池中代理 delete proxy(proxy) return None python from fetcher.baseFetcher import BaseFetcher from util.webRequest import WebRequest class MyProxyFetcher(BaseFetcher): """我的代理源""" name = "myproxy" url = " enabled = True def fetch(self): r = WebRequest().get(" for item in r.json: yield item["ip"] + ":" + item["port"] 2、添加好后, schedule 进程下次抓取时会自动扫描 fetcher/sources/ 目录并启用新代理源,无需修改配置。 可用 python proxyPool.py fetcher 命令查看当前启用的代理源列表。 如需临时禁用某个代理源,在 setting.py 的 PROXY FETCHER EXCLUDE 黑名单中添加其…

read the full proxy_pool overview →

More in Data & Analytics

Related comparisons

More Data Extraction & Web Scraping projects

Compare either of these against the rest of the Data Extraction & Web Scraping field.

Frequently asked questions

Is Scrapegraph-ai or proxy_pool more popular?

Scrapegraph-ai has 32,439 GitHub stars and proxy_pool has 23,778. Scrapegraph-ai has the larger community by that measure.

Are Scrapegraph-ai and proxy_pool free?

Both are open source. Scrapegraph-ai is licensed under MIT and proxy_pool under MIT. Neither carries a licence fee.

What is the difference between Scrapegraph-ai and proxy_pool?

Scrapegraph-ai is written in Python and proxy_pool in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, Scrapegraph-ai or proxy_pool?

Choose Scrapegraph-ai if you want the larger community (32,439 stars) or its MIT licence terms. Choose proxy_pool if its feature set, stack or MIT licence fits better. Both are self-hostable.