# 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. It is open source and self-hosted, installable on Docker Hub and Unraid.

Canonical page: https://ourlocalhost.com/app/2496/fastcrw-aio

## Description

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.

## Health score

51/100 (Fair), based on 3 of 4 factors.
- Maintained: 84 (last commit 11 days ago)
- Popular: 12 (3 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)

## Links

- Docker Hub: https://hub.docker.com/r/dub19/fastcrw-aio
- GitHub: https://github.com/wgross19/fastcrw-aio
- Official website: https://fastcrw.com
- Documentation: https://fastcrw.com/skills
- Unraid: https://ca.unraid.net/apps/fastcrw-aio-0ocpc4219tpc9y?q=fastcrw-aio

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/2496/fastcrw-aio), the self-hosted and open-source app directory.
