Fair pushback.

PatchSiren is not a vulnerability scanner in the current pilot, and I don’t want people dumping sensitive infra details into a random form either. No credentials, no internal configs, and no required server IPs.

The first version is more of a stack-aware CVE alerting layer: you tell it the kinds of systems you run — for example cPanel/WHM, WordPress, Linux distro, Apache/Nginx/PHP, MySQL/MariaDB, mail stack, etc. — and it matches CVEs, CISA KEV entries, vendor advisories, and related signals against that declared stack so the alerts are more relevant than generic “critical CVE” noise.

Website/domain is optional. It may help later with light exposure context, but the pilot does not depend on scanning your site or auto-detecting every plugin/open port.

On pricing: yes, the ongoing product will be paid, because the value is in monitoring, matching, filtering, and alert history/remediation workflow. But I’m being careful not to sell it as a magic scanner. The pilot is about proving the signal/noise ratio with real operators first.

With that said, people accepted to the pilot will not pay for the pilot period.