ChatGPT Sites: Codex Now Builds and Deploys Internal Web Apps for Business Teams
ChatGPT Sites lets Business and Enterprise teams ask Codex to build, deploy, and host full-stack internal web apps — no deployment pipeline needed.
Most teams have a list of internal tools they’ve always needed but never built. A KPI dashboard for the weekly review. A request tracker for the ops team. An onboarding hub that isn’t just a Google Doc with too many headings. These things never clear the engineering backlog because they’re useful but not urgent, and they sit there for years.
ChatGPT Sites, which launched in preview on 2 June 2026, is a direct answer to that problem. Available now for ChatGPT Business workspaces with Codex access, it lets teams ask Codex to build, deploy, and host a lightweight full-stack web app — with a real URL, workspace authentication, and data storage — without touching a deployment pipeline.
What ChatGPT Sites actually does
Sites is a feature built on top of Codex, OpenAI’s coding agent. You describe what you want, Codex builds the application in JavaScript or TypeScript, deploys it to OpenAI-managed hosting, and hands you a URL you can share with your team.
The apps are full-stack. They can read and write data, store files, and authenticate users through Sign in with ChatGPT — meaning access is automatically limited to people already in your ChatGPT workspace. You do not need to set up OAuth, configure a hosting provider, or write a single line of deployment config.
What you can build is genuinely broad. Codex can produce dashboards, project trackers, review workspaces, galleries, lightweight approval tools, and knowledge bases. These are not static pages. The apps update as project information changes and remain shareable via URL throughout their lifecycle.
How access and permissions work
For Business workspaces, Sites is enabled by default. Admins and owners manage it from Workspace settings > Permissions & Roles, and can disable published sites from Workspace settings > Sites.
For Enterprise and Edu workspaces, it is off by default. Admins need to enable it through the Early Access section of admin settings, after which users can install the Sites plugin from the Codex Plugins marketplace.
New sites default to the most restrictive access posture — admins only — and access can be widened deliberately from there. The RBAC model mirrors the existing ChatGPT workspace structure, so there is nothing new to learn or configure from a permissions standpoint.
What this means for your team
The practical value here is mostly about the gap it closes between “we should build something” and “we have a working thing.”
Right now, that gap requires a developer, a backlog slot, a hosting decision, an auth integration, and probably a few weeks of elapsed time. With Sites, a team member describes the tool they need, Codex builds it, and within a session they have a hosted URL they can share with colleagues. A developer can still be involved — to refine the app, review the code, or add complexity — but they no longer need to be the person who gets it from zero to deployed.
Authentication is already included because it inherits from your ChatGPT subscription. A company with 500 employees on ChatGPT Business gets internal-tool authentication for all 500 people without any additional setup. Security and compliance carry over from the workspace too, including SOC 2 compliance and OpenAI’s default policy of not using Business or Enterprise data to train models.
Hosting is fully managed by OpenAI. The app itself lives on OpenAI infrastructure. Data the app processes can come from connected systems like Google Drive or Slack through existing integrations.
A few things worth knowing before you start
OpenAI’s developer documentation is explicit on a couple of points worth flagging.
Storage: Codex stores project and hosting configuration in .openai/hosting.json. Use the relational database (D1) and file storage (R2) options for data that genuinely needs to persist between sessions. Do not use them for temporary UI state like a dismissed banner or a theme preference.
Secrets: Manage environment variables and secrets through the Sites panel in the Codex app. Do not put secret values into .openai/hosting.json or commit them to source control.
Access: Set access controls before sharing a URL. The default is admins-only, which is the right starting point.
The broader picture
OpenAI noted during its “Intelligence at Work” livestream that Codex now has more than 5 million weekly users, and roughly 20% of them are not developers. That group — analysts, operators, marketers, researchers — is growing more than three times faster than the developer segment. Sites fits squarely into that trend. It gives non-developers a way to produce something genuinely interactive and shareable from Codex, not just a document or a code file they cannot run.
OpenAI is also building out a partner ecosystem around Sites, working with companies including Wix, Replit, Lovable, Figma, Webflow, and Emergent, though detail on what those integrations look like in practice is still limited at preview stage.
For teams already on ChatGPT Business, Sites is available now. For Enterprise admins, the toggle is in the Early Access section of your admin console. Given that it adds no incremental cost and requires no infrastructure changes, it is worth switching on and seeing what your team reaches for first.