feat: add fastCRW crawl provider#4033
Open
us wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds fastCRW as a crawl provider, alongside Firecrawl.
Extends the
CrawlTypeenum + crawl dispatch incrawl_operator.rs.Why
fastCRW is a faster, more open alternative to Firecrawl for web crawling — and the reason this diff is small is that it implements the same API surface.
Fully open self-hostable — reaches sites Firecrawl OSS can't. fastCRW ships anti-bot/stealth handling, BYO-proxy + rotation, and JS rendering (Cloudflare challenge bypass, SPA support, HTTP→headless→proxy fallback ladder) in the open core under AGPL. Firecrawl's OSS release gates its stealth engine (
fire-engine) behind a cloud-only flag, so a self-hosted Firecrawl falls back to plain fetch/Playwright and can't reach protected or JS-heavy pages. fastCRW's self-host can — one ~8MB Rust binary, ~6MB RAM, no multi-service stack.Faster and higher recall on Firecrawl's own benchmark dataset. On Firecrawl's published benchmark corpus: fastCRW achieves 63.74% truth-recall vs. Firecrawl's 56.04%, with a faster median latency (p50 ~1.9s vs. ~2.3s).
Search backed by an optimized SearXNG. The
/searchendpoint is SearXNG-backed with added reranking and multi-round retrieval, rather than a thin proxy over a single search provider.Why this is a tiny additive diff: fastCRW is wire-compatible with the Firecrawl API, so adding it mirrors the existing Firecrawl integration without touching any existing code paths (Firecrawl untouched).
Key via
CRW_API_KEY(free tier at https://fastcrw.com/dashboard); self-host base URL supported. Happy to adjust to your conventions — I maintain it and can provide free credits.