Docs / Results and account

Not built yet

What Crossfyre does not do today, and what works only in part.

This list says what is missing today. It comes from the same status table the landing page counts from.

Managed nodes and proxy pools

Not built

Today every node is one you enrol yourself, on a Linux host with Docker. Managed nodes would remove that step. The deploy page shows the option disabled rather than pretending otherwise.

Requests and responses in a report

Not built

A finding in a report prints what the engine observed and a request you can run to see it yourself. The raw request and response behind it are not kept, so they are not printed. Reports are also set in Latin script only, and a share link is always on crossfyre.io.

Public partner API

Not built

The dashboard and the CLI both talk to the control plane, but there is no documented API for anyone else to build against.

Two-factor authentication

Not built

The settings page has the row and it is locked.

Self-hosted control plane

Not built

The engines and the OAST server are open and self-hostable. The control plane is not.

Half built

These exist and you will notice the gap:

  • Custom .cfx workflows run, but the create card in the dashboard is still locked.
  • Findings retention runs in report-only mode in production: it logs what it would remove and removes nothing, so the plan retention windows are not yet enforced.
  • Priority execution and the per-tier adaptive levels are not differentiated yet.