Codex Sites: Internal Tools and Service Limitations

What is Codex Sites?#

In short: you tell the chat, “build me a sales dashboard with filters by manager and month,” and a few minutes later you get a live URL. You get a production-ready page immediately—not a file you have to deploy to Vercel or Cloudflare yourself, and not a preview that lasts an hour. Only people with accounts in your ChatGPT workspace can view it.

OpenAI describes Sites this way:

The key word is “internal.” Codex Sites does not build a public brochure website or an advertising landing page. That becomes clear as soon as you start working with it: no public URLs, no custom domains, and no way to accept payments.

June 2 Timeline: How OpenAI Introduced Codex Sites#

At the same event, OpenAI shared the numbers: Codex has more than 5 million weekly active users, and about 20% of them are non-developers. This group is growing three times faster than developers. Analysts, marketers, operators, designers, researchers—more and more people are using Codex as a tool for their daily work, not as an AI for code.

Sites is a response to this shift. When you have ten non-programmers on your team describing tasks to Codex every day, sooner or later the question comes up: can the result live somewhere other than the chat, as a working tool the whole team can use? Sites says yes, without a separate deployment.

Partners at the announcement included Wix, Base44, Replit, Lovable, and Figma. Technically, the partnerships do not mean mutual integration—they are a PR framing.

What’s Inside Codex Sites: Cloudflare Worker, D1, and R2#

Technically, Codex Sites is a templated build for Cloudflare Workers. The application gets built-in storage primitives:

• D1 — a relational, SQLite-compatible database. For user records, game progress, voting entries, and any structured state.
• R2 — object storage. For images, documents, audio, and video.
• Environment variables and secrets — managed through the Sites panel, not an MDX file in the repository.

OpenAI describes the deployment workflow this way:

In business terms: there is no test domain, no staging server, and no “draft we’ll push later.” Every version save followed by deployment goes straight into the workspace’s live environment. This works for prototypes, but long-lived internal tools call for caution: every employee will see a logic error as soon as it is deployed.

Another important technical limit is what Sites does not do:

This is a direct policy prohibition. Any use case involving such data—medical records, customers’ card details—is immediately out. That is understandable: OpenAI does not want to take on HIPAA and PCI compliance for a preview feature.

5 Codex Sites Limitations That Reviews Don’t Mention#

OpenAI’s technical documentation provides a map of the limitations. As of June 14, 2026, they are as follows.

1. No public URL. Authentication is tied to the ChatGPT workspace. To access the site, you must be a member of that workspace and sign in through “Sign in with ChatGPT.” An outside client who is not on the team will see nothing. It is an internal application in the strict sense, not a public one.

2. No custom domain. All applications live on the name.sites.openai.com subdomain. You cannot host one under your own brand or point a CNAME to it. This rules out scenarios where the site needs to look like part of your brand.

3. No code export. What Codex Sites builds stays inside OpenAI’s infrastructure. You cannot download a project archive and move it to Vercel or your own server. This is not yet relevant for a solo founder on Plus or Pro—the service simply is not available to them.

4. You can’t accept payments. Sites’ policy explicitly prohibits processing bank card data. That means e-commerce, SaaS subscriptions, and direct sales through a website are all out.

5. Business and Enterprise only. ChatGPT Plus, Pro, Team, and Free are not supported. OpenAI promises that “other plans will be connected gradually,” but has not announced dates. A solo founder on the Pro plan cannot use Sites now, even if willing to pay separately.

In the June 14 preview snapshot described here, Sites access is included with Business and Enterprise. Codex usage allowances and Sites hosting charges are separate questions: this article does not establish a token-based hosting tariff or a hosting spending cap. Check the current plan and service terms before budgeting for continued use.

What Is an Internal Tool and Why Does a Team Need One?#

This distinction is key to understanding Codex Sites. Lovable, Bolt, v0, and Replit Agent are all optimized for external products: a landing page, a service prototype, a SaaS prototype you can show clients or investors tomorrow. Such a product needs a public URL, preferably a custom domain, a way to accept payments, and user registration.

An internal tool is a different category. Ten to twenty people on a team use it, and three things matter more: that it can be built quickly, that it works right away, and that its data lives in the same place as the rest of the work. It does not need a branded domain. It does not need a public URL. It does not need customers at all.

If you have a team of five or more on ChatGPT Business, you could build the following in Sites in a week:

1. An analytics dashboard for senior management (weekly sales KPIs, registration funnel, retention).
2. An idea submission form with employee voting.
3. An onboarding hub for new employees with a first-week progress tracker.
4. An internal product knowledge base with search.
5. A request board for departments with status filters.

Each of these tools used to be built either as a Notion page (slow, poor logic), a Google Sheet with Apps Script (scary), or by hiring a frontend developer for two weeks. Sites handles this class of task faster, more cheaply, and without external deployment.

Codex Sites vs. Lovable, Bolt, v0, and Replit: What’s the Right Comparison?#

Reviews have fallen into a lazy habit: if a service builds a website, let’s compare it with others that also build websites. That mixes different niches. The right dividing line comes down to two questions: who needs it, and where does the code go?

A comparison across the key dimensions:

OpenAI positions it this way: your workspace now works as a platform for lightweight applications. Sites is bundled with the Business subscription, with no separate charge or purchase button.

If you are already using Lovable and thinking of switching, don’t. In the preview snapshot described here, Lovable has three things Codex Sites does not offer: a public URL, a custom domain, and code export. I covered the differences between Lovable and Claude Code in a separate Lovable guide—there you can see that Lovable is built specifically for public products.

Codex Sites handles the internal office board. It does not build a storefront for the market.

Who Codex Sites Is Really For in 2026: 3 Profiles#

Profile 1: a ChatGPT Business team of 5 to 50 people. They already use Codex and ChatGPT at work. An analyst puts together reports every day, a marketer prepares briefs and materials, and a salesperson tracks the funnel. Requests for internal dashboards are growing: “Can we make the data available at a live URL for the team, without resending it from chat every time?” Codex Sites fills this gap without a developer budget. One example: a 15-person startup whose CEO asks for a dashboard showing weekly team activity. Codex Sites handles this class of task without a separate rollout.

Profile 2: a startup on ChatGPT Enterprise with RBAC. They have a complex access model: some people see finance, others product, and others marketing. Codex Sites supports workspace_admins_only and configurable groups. This fits their security needs: data stays within the account perimeter, authentication is through Sign in with ChatGPT, and the audit log is standard. The lack of external URLs and code export matters to them as a plus, not a minus. Example: a 40-person fintech startup that needs a dashboard for compliance reports with access controls.

Profile 3: a 200-person corporate marketing department. They use ChatGPT Enterprise, but the IT department is busy migrating the ERP. Requests for internal sites are piling up—an onboarding hub for new hires, a brand library, a performance dashboard for senior management. Through IT, this would take six months. With Codex Sites, a couple of days. A corporate AI tools pilot without the infrastructure team. Example: corporate marketing at a large bank building a quarterly prototype dashboard for customer NPS.

In all three profiles, the key condition is that the team already has ChatGPT Business or Enterprise. Without that, Codex Sites is not an option.

Who Codex Sites Is NOT For: 3 Anti-Profiles#

Anti-profile 1: a solo founder or freelancer. They are on ChatGPT Plus or Pro, where Sites is currently unavailable. When OpenAI will make it available on those plans is unknown. Their alternatives are Lovable, Bolt, v0, Replit, Cursor, and the Claude Code combination. I wrote about comparing all eight tools in a separate pillar guide—it shows which tools suit which solo projects.

Anti-profile 2: an e-commerce or SaaS owner. They need a public URL, a payment form, customer registration, and recurring billing. Codex Sites does none of this: its policy explicitly prohibits PCI DSS, authentication is workspace-only, and code export is impossible. Shopify + Lovable / Bolt for a landing page, or Claude Code for full-stack, would suit them.

Anti-profile 3: a marketer who needs a public landing page. The task is standard: a landing page for an advertising campaign, SEO optimization, metrics, A/B tests, and a lead form connected to a CRM. Codex Sites is not indexed by Google (there is no public URL), does not connect to a CRM without scripts, and is not visible without signing into ChatGPT. It is immediately clear this is not the right tool. Lovable, Webflow, Tilda, or a landing page built in Claude Code and deployed to your own hosting would suit them.

How to Try Codex Sites Today and What to Do Without Business#

Step-by-step plan for Business / Enterprise:

1. Open ChatGPT in a browser or the app.
2. Go to Codex (in the left sidebar or by opening the Codex tab directly).
3. Find the Sites plugin in the sidebar. It is enabled by default on Business. On Enterprise, an administrator must enable it through the access settings.
4. Start a conversation: “Build me a weekly sales dashboard.” Don’t go into detail in the first prompt.
5. When Codex offers the first prototype, ask for changes iteratively: “add a manager filter,” “save the data in D1 so it persists between sessions,” “add CSV export.”
6. Before deployment, reread OpenAI’s warnings about production. Every deployment goes straight to production; there is no separate staging phase.
7. After deployment, you will get a URL like app-name.sites.openai.com. Share it with your team via a link or pin it in the workspace.

If you don’t have Business, there are three practical alternatives:

• Lovable + Vercel — for a public prototype or landing page. The free plan is enough to build a prototype in an evening.
• Bolt or v0 — if you need a focused React frontend for an existing backend.
• Claude Code + Coolify combination — full control over the code, your own infrastructure, and no dependence on another provider. This is the path for people who want long-term autonomy. This combination works for various projects, from landing pages to internal tools.

If you don’t yet have a team and ChatGPT Business, don’t rush to sign up for one Sites. Wait until it opens up on Plus and Pro (OpenAI promises “in the coming months,” with no exact date), or use Claude Code + Lovable for prototypes aimed at the public market.

What’s Next for Codex Sites: A Forecast Without Guarantees#

The preview described here has no separate Sites access charge for Business / Enterprise. That snapshot does not establish future hosting prices or prove that separate billing will be introduced; check an official pricing announcement when terms change.

Custom domains remain an open question. OpenAI’s official documentation does not mention them. Logic suggests custom domains will appear in Sites sooner or later—it is too obvious a feature to leave out. But not now.

OpenAI’s cited direction is gradual availability on other plans. It does not establish when Plus or Pro will gain access. Wait for an actual eligibility announcement before planning work around either plan.

Expanding deployment modes (staging vs. production) seems like a likely next step. Production-only deployment works for prototypes, but it is risky for serious internal tools. A separate preview mode is an author’s forecast; no release date is established here.

In short, Codex Sites is a service in its first version. In six months, it will look different. The decision to use it comes down to whether you need it now or can wait.