OpenAI Codex Sites Explained — The AI Dev Environment That Deploys a URL for You

Codex Sites, in short, is a system that 'lets OpenAI host the code Codex writes and issue a shareable URL within your workspace.' With a ChatGPT Business or Enterprise subscription, you simply enable Sites from the Codex app sidebar, and the entire pipeline — coding, build, deploy, URL sharing — runs end to end. Previously you had to write deploy configs for Vercel or Netlify after getting your code; Sites skips that step entirely. That said, it is constrained to Cloudflare Worker-compatible JS/TS, and there are several things to consider before using it as a foundation for production services.

On June 2, 2026, OpenAI published 'Codex for every role, tool, and workflow' on its official blog and simultaneously updated the Codex Changelog, announcing three major updates at once.

- Sites: A new capability to generate, save, deploy, and inspect web apps, dashboards, and games - Annotations: Inline commenting for code reviews and documentation - Six role-specific plugins: Tailored for sales, data analysis, creative, product design, public equity investment, and investment banking

The overarching theme of this update is 'bringing Codex to every role, not just developers,' making it possible for non-technical workers to share their outputs in a directly accessible format.

According to the official specification, Sites is 'a plugin feature that lets you create, save, deploy, and inspect websites, web apps, and games directly from Codex, hosted by OpenAI.' Delivery is explicitly through the Codex app sidebar; there is currently no official documentation on using Sites via CLI, Desktop, or Mobile.

The intended output formats include:

- Dashboards (sales, analytics, KPI monitoring) - Planners (task management, roadmap visualization) - Review workspaces (code review, design approval flows) - Project boards (Kanban-style progress tracking) - Galleries (portfolio or document sharing) - Lightweight tools (calculators, forms, internal request systems)

Generated URLs can be shared with workspace members. There is no official documentation on public (anonymous internet) access, suggesting that 'sharing within the workspace' is the primary use case as currently designed.

Sites handles generated artifacts in two stages.

- Save: Keeps the artifact within the Codex session. No external URL is issued. - Deploy (production): Issues an OpenAI-hosted URL that workspace users can access and share.

Storage options explicitly documented include Cloudflare D1 (relational DB) and R2 (object storage), enabling lightweight data persistence without additional infrastructure. The binding between a local project and the hosted destination is managed via `.openai/hosting.json`, and runtime secrets (API keys, etc.) are configured from the app panel. Custom domains, SSL, bandwidth limits, and SLA are not mentioned in official documentation.

The official specification defines a compatible project as 'any project that can build a Cloudflare Worker-compatible ES Modules output.' The underlying runtime is a Cloudflare Workers-compatible environment served under an OpenAI hostname. Full Node.js APIs and Python servers are not directly supported.

There are no official announcements of support for individual frameworks such as Next.js, React, Vue, or Python servers. JS/TS-based configurations that fit within the Workers-compatible model (e.g., Hono, Remix on Workers) are expected to be the main use cases. Anyone wanting to run full-stack Rails or Django will need to find alternative hosting.

OpenAI has explicitly named Vercel, Wix, Base44, Replit, Lovable, Figma, Webflow, and Emergent as partners in the Sites ecosystem, while many of these services also compete directly with Codex Sites.

- v0.dev (Vercel): Component generation-focused; DB / Auth / Deploy handled separately - bolt.new / Lovable: JS-only full-stack generation for non-developers - Replit: Multi-language support with Agent 4 for serious app development - Codex Sites: 'One-click hosting by OpenAI itself with a shareable URL' is the differentiator

This 'competitor and partner' dynamic is unusual, and has attracted attention in TechCrunch and VentureBeat. OpenAI internalizing hosting while maintaining integration channels with the existing ecosystem is a reflection of how complex territorial competition in the AI coding market has become.

The official specification explicitly defines three levels of access control.

- admins_only: Accessible only to workspace admins - workspace_all: Accessible to all workspace members - custom: Accessible only to specific users or groups

Enterprise admins can enable or disable the Codex Sites feature itself through RBAC. For organizations that need per-department usage control or compliance with information security policies, this level of access granularity is an important capability.

There are two particularly important operational limitations to be aware of.

1. No staging environment: As officially stated, all deployed URLs are treated as 'production.' Test deployments also go directly to production URLs, which means teams accustomed to dev/staging/prod separation will need to rethink their workflows.

2. No official statement on external/public access: Sites is currently designed for 'sharing within the workspace' as its primary use case, and it is not possible to confirm from official documentation whether anonymous internet access is supported. If you are considering using Sites for externally facing services, reaching out to OpenAI support for clarification is strongly recommended.

Codex Sites is currently available as a preview for ChatGPT Business and Enterprise workspaces. Expansion to Plus, Pro, and Team plans is mentioned only as 'more plans rolling out later,' with no specific timeline.

- Additional charges: No official statement - Custom domain fees: No official statement - Bandwidth / execution time pricing: No official statement - Plus / Pro pricing: No official statement

Given the higher per-seat cost of Business / Enterprise, it is more practical to evaluate Sites as added value within an existing ChatGPT contract rather than as a standalone cost-benefit analysis.

Sites shines most when non-developers want to share their output in a directly accessible format. Combined with the six role-specific plugins (sales, data analysis, creative, product design, public equity, investment banking) released alongside Sites, workflows like the following become possible.

- Sales teams: Generate a dashboard from deal data in Codex and share the URL with managers - Data analysts: Convert analysis results into a visualization app and share with non-engineer decision makers - Product designers: Generate UI prototypes in Codex and review them within the workspace - Internal IT teams: Quickly deploy request forms or lightweight internal tools for department rollout - Corporate planning: Build a PoC dashboard in minutes and issue a demo URL for an executive presentation

While Sites is highly convenient, the following points need to be addressed before full enterprise deployment.

- No SLA or availability guarantees: As a preview, OpenAI makes no uptime commitments - No production/staging separation: Test deployments go directly to production URLs - Data stored on OpenAI hosting: The underlying runtime is a Cloudflare Workers-compatible environment - Business / Enterprise plans only: Unavailable to personal or Team plan subscribers at this time - Cloudflare Worker compatibility constraint: Full Node.js APIs and Python require alternative solutions

Many Japanese enterprises already have ChatGPT Business or Enterprise subscriptions, and in that context the addition of Sites represents an extremely low barrier to entry — 'generate, host, and share a URL, all within the existing contract, with no additional infrastructure.'

The highest-impact scenarios are:

- Departmental internal dashboards (automated weekly report visualization, etc.) - Rapid PoC prototyping with quick sharing to stakeholders - Fast setup of internal review screens

On the other hand, given (a) no official documentation on custom domains or public access, (b) Business/Enterprise-only restriction, (c) Cloudflare Worker compatibility constraint, and (d) no SLA in preview, it is prudent to conclude that adopting Sites as a foundation for customer-facing production services is premature. The recommended approach is to position it as an internal all-in-one complement to Vercel or Netlify, while continuing to use dedicated hosting platforms for externally facing production services. From an AI consulting perspective, proper situational awareness and phased adoption planning are essential when evaluating new tools like this.

As of the time of writing (June 3, 2026), the following items could not be confirmed from official documentation and are expected to be clarified in future updates.

- Custom domain support - Explicit SSL certificate documentation - Pricing and timeline for Plus / Pro / Team plans - Free tier, bandwidth limits, and execution time billing - SLA (uptime guarantees) - Anonymous public internet access - Usage via CLI, Desktop, or Mobile apps - Official framework support statements for Next.js, Remix, Python, etc.

Is Codex Sites free to use? Currently, it is limited to a preview for ChatGPT Business and Enterprise workspaces. There is no official documentation on additional charges or free tiers. Expansion to Plus, Pro, and Team plans is described only as 'rolling out later.' Can I deploy a React or Next.js app directly? The official specification defines compatibility as 'any project that can build a Cloudflare Worker-compatible ES Modules output.' There are no official announcements of support for Next.js, Python servers, or other specific frameworks. JS/TS-based configurations compatible with the Workers runtime are the expected primary use case. Can I share the deployed URL with people outside my company? There is no clear official documentation on external (anonymous internet) access. Based on the access control specification, Sites appears to be designed with 'sharing within the workspace' as the primary use case. Confirm with OpenAI support before relying on public access for your use case. Can I create a staging or test environment? Not at this time. As officially stated, all deployed URLs are treated as production. Test deployments also go directly to production URLs, so workflows requiring environment separation need to account for this. Where is my data stored? Data from generated and deployed apps is stored on OpenAI hosting (Cloudflare Workers-compatible runtime). D1 (relational DB) and R2 (object storage) are available as storage options. Can Enterprise admins restrict access to Sites? Yes. Enterprise admins can enable or disable the Codex Sites feature via RBAC. Additionally, the three-level access control (admins_only / workspace_all / custom) allows per-department usage restrictions. How does it compare to Vercel or Replit? The key differentiator is 'one-click hosting by OpenAI itself with a URL issued directly from Codex output.' Vercel's v0.dev is component generation-focused with separate deploy setup; Replit is a full multi-language development environment; Lovable is a full-stack generator for non-developers. Notably, OpenAI has also named these companies as official partners, creating an unusual competitive-yet-collaborative dynamic.

Codex Sites offers a groundbreaking experience — 'everything from coding to URL issuance within a single ChatGPT contract' — while also carrying limitations that make it not yet ready for enterprise production: Cloudflare Worker-only, no staging, no confirmed public access, and no SLA.

Where it delivers immediate value: Internal PoC, departmental dashboards, and rapid build-and-share for review workspaces. With a Business or Enterprise subscription, you can start the same day with no additional infrastructure.

Where it is better to wait: Customer-facing production services, portals requiring public access, and systems built on Workers-incompatible technology like Python or Rails. Reassessment is recommended once SLA commitments and custom domain support are officially published.

The evolution of AI coding tools continues across OpenAI Codex Computer Use Windows, OpenAI Symphony, Claude Code, Cursor Automations, Windsurf x Devin, and Google Antigravity 2.0, and competition is intensifying. The GA launch, pricing announcements, and framework support expansions for Sites are worth watching closely.

- Sites – Codex (official specification) - Changelog – Codex - OpenAI — Codex for every role, tool, and workflow - TechCrunch — OpenAI launches new Codex tools (2026-06-02) - VentureBeat — Codex Sites for enterprise workspaces - Neowin — Codex shareable Sites - 9to5Mac — Codex 6 business plugins (2026-06-02) - The New Stack — OpenAI Codex Sites, Annotations