Introducing Sites in Codex

The more consequential detail buried in this announcement is that OpenAI is now competing with its own enterprise customers: companies that built internal tooling businesses on top of OpenAI APIs now face a first-party product targeting the same workflow automation use cases they serve.

This move is a direct extension of the distribution logic covered when OpenAI's frontier models and Codex landed on AWS Marketplace at the start of June. That partnership removed procurement friction for enterprises; Sites removes the remaining build friction by collapsing the gap between model access and deployed application. Together, the two moves sketch a clear vertical integration strategy: OpenAI wants to own the path from API call to production tool, not just the model underneath it. The Lovable coverage from the same period is also relevant here, since GPT-5.5's planning improvements were framed as enabling more ambitious no-code builds. Sites effectively internalizes that value proposition rather than leaving it to third-party builders.

Watch whether Retool, Glide, or similar internal-tool vendors report customer churn or pricing pressure in their next public updates. If enterprise adoption of Sites is material, those signals will surface within two quarters.