https://crossfyre.io/blog Distributed recon, offensive-security methodology, and Crossfyre product notes. en-us https://crossfyre.io/blog/open-beta https://crossfyre.io/blog/open-beta Wed, 17 Jun 2026 00:00:00 GMT Product Crossfyre is a hosted control plane for distributed offensive security: enrol your own machines as nodes, orchestrate recon engines across them, and get raw output turned into ranked findings. Here is what is live today, what is coming, and how to start free. https://crossfyre.io/blog/distributed-port-scanning-pulse https://crossfyre.io/blog/distributed-port-scanning-pulse Tue, 16 Jun 2026 00:00:00 GMT Methodology Scanning a large IP range from one host is slow and conspicuous. See how Crossfyre fans a pulse scan across a node fleet: splitting CIDR ranges, choosing SYN vs connect, detecting services, pacing the scan for you, and resuming a big sweep crash-safe. https://crossfyre.io/blog/roadmap https://crossfyre.io/blog/roadmap Mon, 15 Jun 2026 00:00:00 GMT Product A candid look at where Crossfyre is going: a dedicated vulnerability-scanning engine, Mission Planner, an expanded Valkyrie, an extension marketplace, and a self-hosted control plane. These are directions, not ship dates. https://crossfyre.io/blog/cfx-playbooks https://crossfyre.io/blog/cfx-playbooks Sun, 14 Jun 2026 00:00:00 GMT Capabilities A .cfx playbook is a Python file that chains engines and extensions into one repeatable, parametrized workflow. Here is what a playbook looks like, how it pipes voyage into pulse into mach, and how the same file runs locally or across your whole fleet. https://crossfyre.io/blog/crash-safe-recon https://crossfyre.io/blog/crash-safe-recon Fri, 12 Jun 2026 00:00:00 GMT Capabilities A node reboot, a dropped SSH session, a rate-limit timeout: most recon tooling loses the run. Crossfyre does not. Here is how crash-safe execution works, and why you are never billed for work that did not finish. https://crossfyre.io/blog/valkyrie-triage https://crossfyre.io/blog/valkyrie-triage Thu, 11 Jun 2026 00:00:00 GMT Capabilities Raw recon output is a firehose of mostly noise. Valkyrie is the triage layer that reads it, ranks what matters by severity, and tells you why each finding is worth your time. Here is what it does, what it costs, and what it does not do yet. https://crossfyre.io/blog/nine-layer-stack https://crossfyre.io/blog/nine-layer-stack Wed, 10 Jun 2026 00:00:00 GMT Capabilities Most "distributed recon" is a shell script gluing other people's tools across SSH. Crossfyre is a nine-layer platform built from the runtime up: node fleet, provisioning, package management, networking, engines, workflows, orchestration, control plane, and results. Here is each layer and why it matters. https://crossfyre.io/blog/content-discovery-at-scale https://crossfyre.io/blog/content-discovery-at-scale Tue, 09 Jun 2026 00:00:00 GMT Methodology Large content-discovery runs trip rate limits and WAFs when they all leave from one address. Crossfyre spreads a mach job across your own nodes and proxy routes and paces it for you, so a big scan gets broad coverage with far fewer blocks, and resumes cleanly if it breaks. https://crossfyre.io/blog/opsec-routing https://crossfyre.io/blog/opsec-routing Sun, 07 Jun 2026 00:00:00 GMT Capabilities Where your scan traffic comes from is a scope question before it is anything else. Crossfyre gives you layered proxy chains and VPN-isolated tunnels per node and manages them for you, so authorized tests leave from exactly the IP you intend and stay in-scope. https://crossfyre.io/blog/subdomain-enumeration-voyage https://crossfyre.io/blog/subdomain-enumeration-voyage Fri, 05 Jun 2026 00:00:00 GMT Methodology Thorough subdomain discovery means running passive OSINT and active DNS brute-forcing together, then handling wildcards and validating what you found before you act on it. Here is the methodology, with voyage commands, for scopes you are authorized to test. https://crossfyre.io/blog/getting-started https://crossfyre.io/blog/getting-started Wed, 03 Jun 2026 00:00:00 GMT Guides A real quickstart: install the CLI, log in, enrol a node, launch a subdomain enumeration against an authorized target, and watch findings stream in. With the exact commands. https://crossfyre.io/blog/recon-methodology-bug-bounty https://crossfyre.io/blog/recon-methodology-bug-bounty Sat, 30 May 2026 00:00:00 GMT Methodology Recon that pays off is not a one-off blast of tools, it is a staged pipeline you can run again and again. Here is a repeatable methodology mapped onto Crossfyre workflows: scope, enumerate, validate, scan, discover, triage, and schedule it to stay fresh. https://crossfyre.io/blog/how-credits-work https://crossfyre.io/blog/how-credits-work Wed, 27 May 2026 00:00:00 GMT Guides Your plan sets your limits and unlocks capabilities, and scanning within them is unlimited. Credits are a separate wallet that fuels upcoming AI features. No per-scan fees, no metered minutes. https://crossfyre.io/blog/meet-the-engines https://crossfyre.io/blog/meet-the-engines Fri, 22 May 2026 00:00:00 GMT Capabilities Crossfyre ships three in-house recon engines written in Rust: mach for content discovery, voyage for subdomain enumeration, and pulse for port and host scanning. Here is what each one does, why we built them in Rust, and how they run standalone or orchestrated across a fleet. https://crossfyre.io/blog/crossfyre-concepts https://crossfyre.io/blog/crossfyre-concepts Wed, 20 May 2026 00:00:00 GMT Guides A five-minute explainer of the four nouns that make Crossfyre make sense: the hosted control plane, the nodes that do the work, the workflows you launch, and the findings that stream back.