Product news · Published August 28 · Updated August 29, 2026
Revenue OS private beta is live in production
The scanner prototype is now a deployed operational workspace with bounded scans, page inventory, grouped issues, differential history and private reports.
Production verification completed
Revenue OS 0.2.0 is live with a healthy application and worker, a ready database, an immutable release identity and a verified pre-deploy backup. The application rollback path was rehearsed from the new release to the retained 0.1.0 release and back without a destructive database rollback.
What works now
Website Guard can monitor an authorized public website without a catalog. Catalog Guard adds product identity and source-to-site coverage. The private workspace supports authorization, bounded scan execution, page inventory, grouped issue evidence, status history, reports, export and manual or recurring schedules.
What was measured
A bounded engineering validation covered 95 public pages across five first-party production environments. It recorded zero request errors and zero writes or form submissions. Additional authenticated browser QA verified the production workspace on desktop and at 390 pixels. These are engineering facts—not customer count, revenue, ranking or conversion evidence.
Commercial starting point
The Website Revenue Risk Audit starts at $750. The Catalog Revenue Leak Audit starts at $1,500. A 30-day assisted private beta is scoped at $299–500 for a website or $699–1,000 for a catalog. Final scope records authorization, limits, review effort and exclusions.
What it does not do yet
Deep rendered-DOM analysis for client-only applications remains a bounded adapter. Migration Guard is a limited pilot. Authenticated sites require a separate agreement. Revenue OS does not make automatic production changes or promise ranking or revenue improvement. Self-service billing and verified email alerts are not available.
Who the pilot is for
Agencies, commercial websites, B2B catalogs, e-commerce and SaaS teams that need a repeatable way to detect website regressions, prioritize evidence and verify fixes. The next validation milestone is the first paid customer.