A QA lead asks whether it cuts maintenance. A security owner asks whether a finding can be trusted. An engineering manager asks what it costs and where the data is. Each page answers its question first and says what we are not for.
Yes, where the maintenance is locator churn: a recorded step that stops finding its element gets a proposed repair from more than fifteen fallback strategies, and a person approves it in a queue, so the suite stays green for a reason you can read.
Read the answerA finding is reported as confirmed only when the scanner can attach the request that triggered it, the response that shows it and a proof of concept you can replay; everything else is an observation that never fails a gate.
Read the answerPrices are published: Free, Solo Pro, Team (up to 16 seats, flat) and Enterprise (a from-price, agreed per contract), in USD with an Indian rupee sheet invoiced locally, and nothing is billed as overage.
Read the answerEvery module, with its evidence and its limits, on one page per module.
We use one optional analytics tool, run on our own servers, to see which pages help people. It stays off unless you turn it on. Storage needed to sign you in, keep the site secure and remember this choice is always on. Cookie Policy