head to head · open source
proxy_pool vs google-maps-scraper
proxy_pool has 23,778 GitHub stars, 5,418 forks, 298 open issues and last shipped 5 months ago. google-maps-scraper has 7,194 stars, 1,118 forks, 56 open issues and last shipped 13 days ago. proxy_pool leads on adoption by 231% (23,778 vs 7,194 stars). proxy_pool is written in Python under MIT; google-maps-scraper is written in Go under MIT. proxy_pool has attracted 23% as many forks as stars, google-maps-scraper 16%. google-maps-scraper was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| proxy_pool | google-maps-scraper | |
|---|---|---|
| GitHub stars | ★ 24K | ★ 7.2K |
| License | MIT | MIT |
| Written in | Python | Go |
| Last push | 2026-06-15 | 2026-10-21 |
| Forks | ⑂ 5.4K | ⑂ 1.1K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick proxy_pool if
- You weight community size — 24K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick google-maps-scraper if
- You want the google-maps-scraper feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Go
- You evaluated both and google-maps-scraper fits your workflow better
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 →
About google-maps-scraper
Google Maps Scraper Extract Google Maps business leads, emails, reviews, phone numbers, websites, ratings, coordinates, and more with a free open source CLI, Web UI, REST API, and optional self hosted platform. Use it for lead generation, local business research, sales prospecting, data enrichment, or developer automation. Ask an AI Agent to Get Leads The easiest way to use Google Maps Scraper is with an AI coding agent such as Claude Code, Codex, Cursor, GitHub Copilot, or any Agent Skills compatible tool. You describe the leads you want; the agent plans the searches, runs a small validation, starts the full…
read the full google-maps-scraper 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 proxy_pool or google-maps-scraper more popular?
proxy_pool has 23,778 GitHub stars and google-maps-scraper has 7,194. proxy_pool has the larger community by that measure.
Are proxy_pool and google-maps-scraper free?
Both are open source. proxy_pool is licensed under MIT and google-maps-scraper under MIT. Neither carries a licence fee.
What is the difference between proxy_pool and google-maps-scraper?
proxy_pool is written in Python and google-maps-scraper in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, proxy_pool or google-maps-scraper?
Choose proxy_pool if you want the larger community (23,778 stars) or its MIT licence terms. Choose google-maps-scraper if its feature set, stack or MIT licence fits better. Both are self-hostable.