Bluefield
Self-hosting Bluefield as a Firecrawl alternative
If you want to keep web scraping in your own infrastructure, Bluefield self-hosts in Docker with the same API surface and the same signing pipeline, and its attestation verifier is open source. Firecrawl’s AGPL core has the larger open-source community today; Bluefield’s edge is verifiable provenance, including when self-hosted.
What "self-host" means here
Self-hosting runs the scraping API and its cryptographic signing inside your own cloud, so data and attestations never leave your environment — useful for data-residency and control requirements.
- Self-host
- Run the full API + attestation pipeline in your own Docker environment.
- Open verifier
- The attestation-verification tool is open source, even where the service is not.
- AGPL core
- Firecrawl’s open-source licence; its community is larger today.
Bluefield capabilities
| Capability | Detail |
|---|---|
| Docker self-host | Same API surface in your own cloud |
| Same signing | Cryptographic attestation in your own deployment |
| Open verifier | npx bluefields verify — open-source verification |
| Data control | Data + attestations stay in your environment |
| Agent-native | MCP + OpenAPI + llms.txt |
Frequently asked questions
- Is Bluefield fully open source like Firecrawl?
- The attestation verifier is open source and the service is self-hostable in Docker with the same API. Firecrawl’s AGPL core has a larger community today — if open-source ecosystem size is your priority, that is a real point for Firecrawl.
- Can I keep all data in my own cloud?
- Yes. Self-host Bluefield and both the scraped data and the signed attestations stay in your environment.
- Do I still get provenance when self-hosting?
- Yes — the same signing pipeline runs in your deployment, so every live result is signed and verifiable.