head to head · open source

ArchiveBox vs proxy_pool

ArchiveBox has 28,624 GitHub stars, 1,610 forks, 167 open issues and last shipped today. proxy_pool has 23,730 stars, 5,421 forks, 298 open issues and last shipped 3 months ago. ArchiveBox leads on adoption by 21% (28,624 vs 23,730 stars). ArchiveBox is written in Python under MIT; proxy_pool is written in Python under MIT. ArchiveBox has attracted 6% as many forks as stars, proxy_pool 23%. ArchiveBox 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.

ArchiveBox ★ 29K proxy_pool ★ 24K category Data & Analytics

← all 20902 open source comparisons

Side by side

ArchiveBox proxy_pool
GitHub stars ★ 29K ★ 24K
License MIT MIT
Written in Python Python
Last push 2026-09-27 2026-06-15
Forks ⑂ 1.6K ⑂ 5.4K
Self-hosting Yes Yes
Data ownership Your server Your server

pick ArchiveBox if

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

full ArchiveBox 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 ArchiveBox

ArchiveBox is an open source, self hosted web archiving application that lets individuals and organizations preserve public and private web content in durable, readable formats while keeping control of their own data.

read the full ArchiveBox overview →

About proxy_pool

proxy pool is a self hosted Python proxy IP pool for web spiders that continuously collects, checks, and serves rotating HTTP proxies from public free proxy sources through a Redis backed pool.

read the full proxy_pool overview →

More in Data & Analytics

Browser Use ★ 116K Mermaid ★ 90K Crawl4AI ★ 84K Scrapling ★ 84K Apache Superset ★ 75K echarts ★ 67K

Related comparisons

firecrawl vs scrapy firecrawl vs crawlee browser-use vs crawl4ai browser-use vs scrapling playwright vs crawl4ai browser-use vs scrapy playwright vs scrapling crawl4ai vs scrapling godot vs pixijs mermaid vs apache-superset three-js vs pixijs supabase vs metabase mermaid vs echarts grafana vs apache-superset apache-superset vs echarts mermaid vs metabase mermaid vs clickhouse crawl4ai vs clickhouse scrapling vs clickhouse apache-superset vs clickhouse mermaid vs apache-pinot clickhouse vs duckdb crawl4ai vs apache-pinot scrapling vs apache-pinot

More Data Extraction & Web Scraping projects

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

ArchiveBox vs Browser Use ArchiveBox vs Crawl4AI ArchiveBox vs Scrapling ArchiveBox vs scrapy ArchiveBox vs EasySpider ArchiveBox vs Lightpanda ArchiveBox vs changedetection.io ArchiveBox vs CloakBrowser ArchiveBox vs lux ArchiveBox vs Scrapegraph-ai ArchiveBox vs page-agent ArchiveBox vs crawlee

Frequently asked questions

Is ArchiveBox or proxy_pool more popular?

ArchiveBox has 28,624 GitHub stars and proxy_pool has 23,730. ArchiveBox has the larger community by that measure.

Are ArchiveBox and proxy_pool free?

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

What is the difference between ArchiveBox and proxy_pool?

ArchiveBox 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, ArchiveBox or proxy_pool?

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