Crawld for enterprise
Read this before you start a procurement process: several answers are no.
Status: Not built yet : read the cautions below before planning around this. The rubric applies; the segment-specific work does not exist yet.
The situation
You are evaluating tooling against a security review, a compliance checklist and an SLA. It is cheaper for both of us to establish now which of those this product currently fails.
Which findings dominate here
The product is the same product for every segment: one rubric, 129 checks, the same three outcomes. What changes is which findings do the damage.
The gates are mandatory
The loop stops twice for human approval and that cannot be turned off. WEBSITE.md is explicit: this is not for teams wanting a fully autonomous agent. If the value you are buying is "nobody has to look at it", this is the wrong tool.
No certifications
No SOC 2, no ISO 27001, no published penetration test, no contractual uptime guarantee. These are stated plainly on the security page rather than discovered during review.
Content leaves our infrastructure
Model-judged checks send page content to a large-language-model provider. That is disclosed on the privacy page and is a real consideration for a data-classification review.
What the loop looks like
The free scorecard needs no access and no contract, so a technical evaluation costs nothing and commits nothing.
Where this is a poor fit
If your procurement requires certification, an SLA or a signed DPA today, this is not yet a product you can buy. That is a straight answer rather than a "contact sales".