Run offensive operations across globally distributed nodes with live intelligence, anonymized execution, and a command center designed for modern reconnaissance.
Recon pipelines are still stitched together with shell scripts, temp files, and fragile glue logic. Enumeration, scanning, probing, and analysis remain disconnected systems with no shared operational context.
One scanner discovers an exposed API. Another tool never sees it. Findings stay trapped inside isolated outputs instead of flowing through a unified operational pipeline.
As targets, nodes, proxies, and workflows scale, operational awareness disappears. Teams lose track of what is running, where traffic originates, and how scans are behaving in real time.
Cron jobs crash. VPS nodes disappear. Tunnels leak. Long-running scans silently stall without orchestration, health monitoring, or recovery mechanisms built into the execution layer.
Everything required to orchestrate offensive security operations at scale, from distributed execution to live operational intelligence.
A scalable operational architecture built for distributed reconnaissance, anonymized execution, and live attack surface intelligence.
Create and manage jobs, configure workflows, and monitor execution through a web interface or direct API calls.
Central control plane that schedules jobs, coordinates workers, and tracks execution state across the platform.
Backend services responsible for authentication, persistence, messaging, and coordinating communication between components.
Distributed execution unit that pulls jobs, runs assigned extensions, and reports results back to the controller.
Modular execution unit that performs a specific operation as part of a workflow.
The systems, networks, or applications designated for testing or analysis during an operation.
Built for every layer of offensive operations, from independent research workflows to enterprise-scale infrastructure programs.
Run distributed reconnaissance and large-scale scanning workflows without building or maintaining offensive infrastructure from scratch.
Coordinate complex offensive operations through a centralized command layer with shared visibility, distributed execution, and operational control.
Continuously monitor internal and external attack surfaces using customizable reconnaissance workflows, streaming intelligence, and automated analysis.
Standardize offensive tooling, infrastructure, and operational policies across distributed teams with centralized visibility and scalable execution.
Crossfyre was designed around the operational realities of modern offensive security, from distributed reconnaissance to stealth infrastructure and large-scale execution.
Crossfyre was built from real-world frustrations with fragmented tooling, unreliable workflows, and infrastructure that failed during active operations.
Designed around evolving offensive methodologies, distributed execution models, and scalable attack surface intelligence techniques.
Built to maintain operational continuity across unstable networks, rate limits, infrastructure failures, and degraded routing conditions.
Limited Seats Available
Limited operator seats · Free during pilot
Answers about deployment models, infrastructure, operational workflows, and platform capabilities.
Crossfyre is built for offensive security teams, independent researchers, enterprise security labs, and organizations operating large-scale reconnaissance or attack surface intelligence workflows.
No. Crossfyre is a commercial offensive security platform developed by Clickswave Labs Private Limited. Certain ecosystem tooling and components may be released separately in the future.
Nodes can be self-hosted by any user. Deploy the cfx_node daemon on your own VPS, lab, or internal infrastructure. Self-hosting the full control plane (Nexus, API switch, and supporting services) is available exclusively to enterprise customers.
Extensions allow Crossfyre nodes to execute external tooling, custom workflows, daemon integrations, and reconnaissance utilities as part of distributed operational pipelines.
Workflows are decomposed into operations and dispatched across distributed nodes using a streaming execution model backed by NATS JetStream. Findings are returned in real time as operations execute.
Yes. Nodes can operate behind layered proxy chains and VPN-isolated network namespaces to reduce attribution risk and enforce traffic isolation during offensive operations.
Crossfyre includes team-based operational management with shared workflows, centralized visibility, permissions, activity tracking, and distributed infrastructure coordination.
Yes. Crossfyre includes a Python-based .cfx playbook system for building custom offensive workflows, automation pipelines, and extension-driven execution logic.