ChatGPT Sites is live for every paid subscriber.

What launched, verified

From the launch announcement and thread: Sites is available now to all paid subscribers as part of the ChatGPT Work release; the announcement's own example site (a map visualization built "last night") lives at an openai.chatgpt.site subdomain. We fetched it within hours of launch: it serves publicly, HTTP 200, no ChatGPT account required to view. Rollout is staged — some Plus users reported not seeing the feature on day one, and the docs hedge that availability "can depend on your plan, region, and workspace settings" — and the team calls this "still only just the start". The docs also settle update semantics: you save versions and deploy them, updates keep the same URL, and "every Sites deployment URL is a production deployment" — genuine replace-in-place.

What changed from Codex Sites

Two things, both big. Availability: Codex Sites was a beta for team plans; the June signal that individual plans were coming "ASAP" took five weeks to land. Visibility: Codex Sites could not be viewed outside your authenticated workspace, which was its defining limitation. ChatGPT Sites flips that: sites are on the open web. If you found our "can you make a Codex site public?" status post before today, the answer there was no; for ChatGPT Sites it is yes, and that post now says so.

The Cloudflare underneath

The launch thread confirmed Sites is "a collaboration between OpenAI and Cloudflare", and community digging identified Cloudflare Workers with SQLite and Durable Objects. Notably, Sites can reportedly export a Wrangler project of your site for hosting on your own Cloudflare account — a real portability story, and a second consecutive datapoint (after Cloudflare Drop, launched the day before) that the biggest players are converging on the same shape: AI makes HTML, it needs a URL instantly, and Cloudflare is becoming the substrate either way.

What is still unknown

• Gates without accounts. The private modes (invitation-only, workspace-limited) require signed-in viewers; no password or email-domain gate exists for account-free recipients, and no expiry is documented.
• Custom domains. Sites live on openai.chatgpt.site subdomains; nothing documented about bringing your own.
• API or agent access. Created and managed in ChatGPT; the docs note there is no standalone CLI management view, and no public API or MCP surface exists for programmatic publishing.
• Limits, indexing, analytics, export. Site counts, sizes, search-engine indexing behavior, viewer analytics, and the community-reported Wrangler export: none documented yet.

Sites or a publish primitive

For a paid ChatGPT subscriber who wants a live app from a conversation, Sites is now the shortest path there has ever been, and public viewing removes its old dealbreaker. The trade arrives exactly where it did for every other entrant: the artifact is public on someone else's domain, made in a chat, updated in a chat. If the thing you are publishing is a client deliverable that should be private, needs your domain, an expiry, a password, or gets published and revised by an agent over an API rather than a conversation, that is the other half of the category — pages as deliverables, private by default, with a read on how they landed. Both halves just got very real.