FastCRW AIO

FastCRW AIO is a self-hosted, Firecrawl-compatible web scraping, crawling, and search service packaged as a single Unraid container for AI agents.

  • AI
  • Development
  • Tools & Utilities
FastCRW AIO is a self-hosted, Firecrawl-compatible web scraping, crawling, and search service packaged as a single Unraid container for AI agents. One s6-supervised image bundles the CRW Rust server, a LightPanda JavaScript renderer, and SearXNG search, exposing scrape, crawl, map, extract, batch scrape, parse, and search endpoints plus a native MCP (Model Context Protocol) endpoint on port 3000. Point Firecrawl-compatible clients or MCP clients such as Claude Code, Cursor, or Gemini CLI at the container to fetch web data at no per-call cost, giving homelab builders a self-hosted alternative to Firecrawl and Tavily.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

51/100 Fair

Maintained
84last commit 11 days ago
Popular
123 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 25 days ago

GitHub stars
3
Open issues
2
Last commit
2026-11-09
Latest release
v0.39.1-aio.1
Activity
declining

Checked 8 days ago - source: GitHub (wgross19/fastcrw-aio)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • MCP setup and agent skill MCP-compatible clients (Claude Code, Cursor, Gemini CLI, Codex, OpenCode, Windsurf) can be pointed at the container's /mcp endpoint on port 3000 (for example, http://[container IP]:3000/mcp) to use the native CRW tools. Install the official fastCRW agent skill, a short SKILL.md file that auto-triggers on web-data tasks, by running npx crw-mcp@latest install. The container also serves full API docu source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need to run SearXNG for fastcrw-aio?

Search and Research require an external SearXNG instance with its JSON API enabled. Set CRW_SEARCH__SEARXNG_URL to that instance, while scrape, crawl, map, extract, and parse work without it.

Can I change the port that clients use?

The internal API port is pinned to 3000 in the image. The published host port is the only port knob and can be changed in the Unraid template's API Port field.

Where does fastcrw-aio store its runtime files?

The container writes runtime configuration under /config and runtime data under /data.

Where should I point an MCP-compatible agent?

Point it at the API port under /mcp.

Will fastcrw-aio replace an existing fastcrw Compose stack?

No, the image does not replace /docker-compose/fastcrw automatically. Keep the existing Compose stack until a separate migration decision is approved.

How are fastcrw-aio upgrades handled?

Upgrades are review-gated and automated, not silent. The aio-fleet control plane watches us/crw for new stable tags and opens a PR on a new tag.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads