Crossfyre vs BBOT
A modular recursive OSINT framework vs a managed distributed recon platform.
BBOT is a powerful open-source recon framework with a large module ecosystem and recursive "spider" behavior. It is yours to run, tune, and scale. Crossfyre trades that build-it-yourself surface for a managed control plane: distributed execution across your nodes, crash-safe state, a dashboard, teams, and AI triage, with open-source engines underneath.
BBOT
- Free and open source; large module ecosystem and recursive enumeration
- You run and scale it yourself (one host, or your own orchestration)
- Highly tunable for those who want to live in the config and modules
- Output is yours to wrangle; no hosted dashboard, teams, or history
- Resilience, scheduling, and triage are whatever you build around it
Crossfyre
- Distributed execution across your own nodes with no orchestration to build
- Crash-safe operations resume across node failures (NATS JetStream)
- mach, voyage, and pulse engines plus an extension model for more
- Hosted dashboard, teams, RBAC, findings history, and exports
- Valkyrie AI turns raw output into ranked, prioritized findings
The honest take
Choose BBOT if you want a free framework you fully own and enjoy tuning. Choose Crossfyre if you would rather not build orchestration, resilience, scheduling, and triage yourself, and want a fleet that just runs.
Frequently asked
Is Crossfyre open source like BBOT?
The scan engines (mach, voyage, pulse) and the node agent are open source. The control plane, orchestration, and Valkyrie AI are proprietary. BBOT is fully open source and self-hosted.
Can I extend Crossfyre with custom modules?
Yes, through Node Extensions and (an early, expanding capability) .cfx playbooks that chain engines into custom workflows. A larger community extension marketplace is on the roadmap.