Docs / Results and account
Teams and billing
Workspaces, teams and organizations, your plan's limits, and where to see how much of them you have used.
Workspaces & teams
A workspace is the isolation boundary for work: its own assets, findings, workflows and history. Keep one per client, per programme, or per environment, and switch between them from the workspace picker. Scans, findings and captures stay in their workspace. Nodes, proxies, credentials and wordlists belong to the account or team that owns the workspace, and every workspace it owns shares them.
A Team Space adds people: shared nodes, proxies, wordlists and credentials. Roles gate managing the team, a node's shell, and archiving, deleting or resetting a workspace; any member of a workspace can run scans in it and manage its arsenal and scope list. Leaders manage members and billing; members run work. Seats and workspace counts are set by your plan.
Invite teammates from Team Space; they join with the invite code emailed to them. Organizations add multiple teams, an org console and shared billing.
Organizations
A personal plan covers your own workspaces and your own arsenal. An organization is a separate billing entity with member seats, teams and shared team workspaces, and it is what you want the moment a second person needs to see the same findings.
You can hold a personal plan and be a member of an organization at once. Your own work stays on your plan; work inside the org is covered by the org. Seats, teams and workspace counts are set by the org plan rather than by the members' individual ones.
Syndicate is prepaid and self-serve: you choose seats and limits up to the plan maximum, and usage pauses instead of overspending. Enterprise is postpaid, provisioned during onboarding and invoiced. Both are managed from the org billing page rather than your personal one.
Usage & status
The Usage page shows what you have consumed against your plan's ceilings: workflows this month, concurrent runs, nodes, proxies, wordlist storage and credits. It is the page to check before a large engagement rather than after one stops early.
The Status page reports the health of Crossfyre's own servers, and the dashboard reads it to explain itself: if a scan will not start because the platform is degraded rather than because of your configuration, that page is where it says so. It is also public at status.clickswave.org.
Billing & credits
Your plan sets your limits (nodes, concurrent workflows, storage, seats). Scanning is unlimited within your plan limits: there are no per-scan fees.
- Free: 2 nodes, 2 concurrent.
- Pro: 10 nodes, 10 concurrent.
- Reaper: 20 nodes, 50 concurrent.
Organizations run on Syndicate (a base price carrying three seats, then per seat) or Enterprise instead. Prices, seat counts and the full limit matrix live on the pricing page, which is the source of truth.