Next.js; custom server-rendered catalog sites; non-catalog commercial site
Bounded production evidence exists.
Platform support · No partnership claims
Web-contract first. Framework adapters second.
Revenue OS primarily observes HTTP, HTML, headers, robots, sitemaps, DOM-visible metadata, schema, links and timing. A CMS or framework integration can add context, but it is not required for the baseline.
Private Beta · Selected engagements
PHP, Java server apps, static HTML, WordPress, WooCommerce, Shopify, Webflow, Framer, Tilda
Basic HTTP/HTML checks do not require a framework connector; platform-specific validation is still required.
React/Vue/SPA application shells
HTTP facts work now. Full rendered-DOM, mobile and visual checks require the optional browser adapter, currently under validation.
Intranets, customer portals, staging behind login
Not scanned by the public worker. Requires explicit authorization and a separately configured execution boundary.
A Java, PHP, Node, Ruby or .NET server that returns public HTML is analyzed through the same web contracts. Static sites work the same way.
A client-rendered app may return an empty shell. Revenue OS records the HTTP fact, labels CLIENT_RENDER_REQUIRED, and avoids false conclusions until the browser adapter runs.
“Compatible with” does not mean partner, certified integration or complete validation on every theme and plugin combination.