Crossfyre is in open beta

Crossfyre is open beta, and you can start using it for free today.

Crossfyre is a hosted control plane for distributed offensive security. You enrol your own machines as nodes, the platform orchestrates recon engines across them, and it turns the raw firehose of output into prioritized findings. You bring the compute and the targets; we handle orchestration, crash-safe execution, results, and the parts that are tedious to build yourself. The scan engines and node agent are open source; the orchestration, scheduling, and dashboard are the hosted platform.

Who it is for

Solo bug-bounty hunters and small red teams. If you already run recon from a few boxes and you are tired of babysitting long scans, stitching tools together, and rerunning runs that died on a reclaimed instance, Crossfyre is built for exactly that. It is not an enterprise-only platform with a sales gate. You sign up and you are running.

What is live today

Everything in this list works right now in the beta:

• Distributed nodes with crash-safe execution. Enrol your own hosts; work is decomposed into durable operations on a NATS JetStream stream, so a dropped or reclaimed node is redelivered to a healthy one and the run keeps going. (More in how scans survive a crashed node.)
• Three recon engines. mach (HTTP fuzzing and content discovery), voyage (subdomain enumeration, passive plus active), and pulse (host and port scanning). Run them standalone or orchestrated across your fleet.
• Workflows. .cfx scripts that drive a scan: subdomain enumeration, port scanning, content discovery. Run locally with crossfyre run or launch across your nodes from the dashboard.
• Live findings and export. Results stream into the Findings explorer as they land; filter by severity and host, search, and export to CSV, JSON, or Markdown.
• Valkyrie triage. The AI triage layer reads scanner output and surfaces ranked findings with severity and context, metered in credits. (See Valkyrie: turning the firehose into ranked findings.)
• Teams and RBAC. Shared nodes, wordlists, and findings in a Team Space, with role-based access for leaders and members.
• Notifications. Get pinged on Discord, Slack, or email when a scan finishes or a finding lands.
• Scheduling. Run workflows on a recurring basis and have results pushed to you.
• The CLI. One crossfyre binary drives install, node enrolment, engines, local runs, and updates.
• Billing and credits. Reserve-then-reconcile metering: you pay for work that actually completed, and credits never expire.
• The newsletter. A public newsletter for release notes and recon writeups.

What is coming

These are on the roadmap and in active development. They are not shipped yet, and we will say clearly when each lands. We do not put dates on things we have not finished.

• A dedicated vulnerability-scanning engine that turns discovered surface into checked, evidence-backed findings.
• Mission Planner, a visual composer for chaining workflows into multi-stage engagements with conditional branching.
• Expanded Valkyrie: payload mutation and deeper agentic probing to dig into candidate vulnerabilities and cut false positives.
• A community extension marketplace for engines and integrations built by the team and by you.
• An enterprise self-hosted control plane for teams that need to run the orchestration layer themselves.

For the current roadmap in more detail, read what we are building next.

How to start

The Free plan gets you one node, one workflow at a time, and starter credits: enough to run a real scan and see the whole loop end to end. No card required to try it.

1. Create an account.
2. Install the CLI: curl -fsSL https://get.crossfyre.io/install.sh | sudo bash
3. Authenticate (crossfyre login), create a node in the dashboard, and enrol your host with sudo crossfyre node init.
4. Launch a workflow and watch findings stream in.

The full walkthrough is in the docs, and the plans are on the pricing page (Free, Pro at $19/mo, Team at $59/mo).

It is beta. Tell us what breaks.

We are calling this open beta because that is what it is. The core is solid and people are running real engagements on it, but you will find rough edges, and we want to hear about every one of them. If a scan does something surprising, if a finding looks wrong, if the CLI fights you, that feedback is the most valuable thing you can send us right now.

Thanks for being early. Go break something (in scope).