Scanner Platform: 149 checks, one engine, two shipped products
One 149-check scan orchestrator, live on Azure Container Apps, powering an AEO/SEO product and a security domain-scan product.
A 149-check scan engine spanning email authentication, SSL/TLS, HTTP headers, DNS, vulnerability detection, performance, technology fingerprinting, compliance, SEO, AEO, content, accessibility, social, schema.org, local SEO, and WordPress categories, run from a single YAML-configured orchestrator, deployed live on Azure Container Apps. Running the same external-facing web scan engine to power two different products -- an AEO/SEO competitive-analysis product and a security domain-scan product -- from one orchestrator and checks library, instead of maintaining duplicate scanning code per product. Evidence: the repository's README check inventory, config/scanner-checks.yaml, lib/orchestrator.js, and 229 commits of history from March 2026 through August 2026.
Technologies
- 149-check orchestrator
- YAML-configured check library
- Azure Container Apps
Applicability
Useful for a technical or executive evaluator assessing Scanner Platform specifically; drawn from internal source evidence, not an independently public-published artifact.
Evidence
Evidence class: delivered-artifact
Frequently asked
What is the evidence behind "Scanner Platform: 149 checks, one engine, two shipped products"?
the repository's README check inventory, config/scanner-checks.yaml, lib/orchestrator.js, and 229 commits of history from March 2026 through August 2026.