Hosting Options for Sites Built with Codex, Claude, or ChatGPT

Where Can an AI-Built Site Live?

Codex, Claude and ChatGPT can now make a working website, not only small pieces of code. Then you must decide where the site runs and how people get to it.

One type of answer is built-in publishing in the AI product: Sites in ChatGPT and Codex, or a published artifact in Claude. This is the shortest path when you do all the work in one tool.

The other type of answer is a regular web host, such as Netlify, Cloudflare Pages, Vercel or GitHub Pages. A regular host accepts files from any agent. Because of this, the site does not depend on the assistant that you used last.

The tool that writes the code does not have to host it. This guide compares the two types. It also shows a workflow that keeps a site portable (easy to move from one agent to another).

Built-In Option 1: Sites in ChatGPT and Codex

With OpenAI’s Sites, you can build, host and share a website. You describe the website in ChatGPT or Codex. Sites can also host a compatible project that you built before, with no separate deployment setup. Sites serves HTTP, HTTPS and WebSockets, but not raw TCP connections.

By default, access is limited. Only the owner and the workspace admins can see a new site until you change the access. Then you can open the site to selected users or groups, invited external viewers or everyone in the workspace. If public publishing is on, you can also open the site to anyone on the internet. The options depend on your account and workspace settings. In Enterprise workspaces, public publishing is off by default, and an admin must turn it on (Sites publishing and sharing).

To update a site, open it in ChatGPT and describe the change. Then review the result, save a version and deploy it. Availability depends on your ChatGPT plan, your region and your workspace settings. Before you make plans that depend on Sites, read the OpenAI help center.

If you build in ChatGPT or Codex and your audience is mostly your own workspace, use Sites. Your plan and your admin settings must also allow it.

Built-In Option 2: Published Claude Artifacts

In Claude, an artifact is a single interactive page, such as a calculator, a small dashboard or a prototype. You can share an artifact from the chat. On Free, Pro and Max plans, open the artifact, select Publish and copy the public link. Anyone with the link can see and use the artifact without a Claude account (Anthropic help center).

On Team and Enterprise plans, you see Share & copy link instead, and the artifact stays in the organization. You can share it outside the organization only if an owner turned on external sharing. These outside viewers need a Claude account.

Artifacts have two limits. After you unpublish an artifact, you cannot publish it again. Also, the unpublish action permanently deletes the stored data of the artifact.

If you must share a single-page tool quickly and a claude.ai link is acceptable, use a published artifact.

Regular Web Hosts That Accept Any Agent’s Output

A regular host accepts the files from any assistant. You upload a folder, connect a Git repository or run a deploy command.

Host	How you publish	Access control	Good fit
Netlify	Drag a folder to Netlify Drop, run netlify deploy --prod, or connect Git	Password protection on Pro and Enterprise plans	Quick handoffs, forms, branch previews
Cloudflare Pages	Drag and drop, npx wrangler pages deploy, or connect Git	Cloudflare Access with email one-time codes or SSO	Private client reviews, large static sites
Vercel	Connect Git or use the Vercel CLI	Vercel Authentication on all plans, and a password on paid plans	Framework apps with preview deployments
GitHub Pages	Push to a repository and publish from a branch or a workflow	Public, except private sites on GitHub Enterprise Cloud	Public docs and project pages

These hosts also work well with coding agents. An agent that can run terminal commands, such as Claude Code or Codex, can deploy with the CLI (command-line tool) of the host. You must log in to the CLI first. Netlify publishes an MCP server (a connector that gives an AI tool new actions). It has setup guides for Claude Code, Codex, Claude, ChatGPT and other clients.

The Agent-Neutral Workflow

This workflow keeps a site portable:

1. Ask the agent to build the site into a folder. Keep the HTML, CSS, JavaScript, images and data files together, with index.html at the top.
2. Put the folder in Git. Then a different agent or a person can open the same files later and see what changed.
3. Deploy the folder to one project on Netlify, Cloudflare Pages, Vercel or GitHub Pages.
4. Share the URL.
5. Make all updates in the same folder, and deploy them to the same project. Claude, ChatGPT or Codex can make the next change. The URL stays the same.

This workflow also helps when different tools are good at different jobs. One assistant can write the first draft of the text. A different assistant can fix a build error, and a local script can export the data. The host sees only the finished files.

Publish the Finished Folder

1. Run the project on your computer. Look at every page that you plan to share. For a plain HTML folder, it is enough to run python3 -m http.server 8000 in the folder.
2. If the project uses a framework (a code library that builds the site), run its production build. Keep the entry HTML file and the assets that it uses together in the output folder.
3. Remove credentials (passwords and keys), .env files, private notes and all other files that do not belong on the site.
4. Upload the output folder with Netlify Drop or Cloudflare Pages Direct Upload. You can also upload it from the terminal:

npx wrangler pages deploy ./dist

5. Open the hosted address in a new private window. Make sure that the navigation, the images and the downloads work. Also make sure that a direct link to a nested page (a page in a subfolder) works.
6. Deploy later changes to the same project. Keep the previous working release. Netlify can publish an earlier deploy again. Cloudflare Pages can roll back to an earlier production deployment.

Decide at the start if you will upload the site or build it from a repository. If you create a Cloudflare Pages project with Direct Upload, you cannot change it to Git later.

Moving a Site Out of a Built-In Host

A static upload copies only static files (files that the server sends without changes). It does not copy a database, a server process, stored data or the sign-in of the original platform. Before you move a site from a built-in host to a regular host, do these steps:

• Ask the agent to list everything that the site depends on. The list must include data storage, environment values and secrets, sign-in, scheduled jobs and external APIs.
• Export the project files and run them on your computer. If a feature worked only on the original platform, it will fail here first.
• Replace the platform features with real equivalents. For data, use a JSON file or a hosted database. For sign-in, use the access control of the new host.
• Keep the old version online until the new version passes the same tests.

If an application needs server functions, read the deployment requirements of the new host first. Do not expect a folder upload to copy the original service.

Decision Guide

• If you work in ChatGPT or Codex and your audience is your workspace, choose Sites. Your plan and admins must allow it.
• To share a single-page tool quickly with anyone who has the link, choose a published Claude artifact.
• For the fastest drag-and-drop handoff of a finished folder, choose Netlify. It also has forms and previews when you need them.
• If the site is only for named people, choose Cloudflare Pages with Cloudflare Access and email codes.
• For framework apps that get value from a preview deployment on every change, choose Vercel.
• For a simple public site that stays next to its repository, choose GitHub Pages.

Before You Share the Address

If the output contains private material, set up access control before you send the link, not after. Choose the method that fits the audience:

• How to Password Protect a Netlify Site
• How to Password Protect a Vercel Site
• How to Password Protect a Cloudflare Pages Site

Then test the production address, each custom domain and each preview URL in a private window. Password Protect a Static Website Safely tells why a JavaScript password prompt in the generated page is not enough.

A docs portal with Ask AI
and support tickets

Connect a repository, or describe your product to start. Each docs site has search, Ask AI, an API console, an MCP server and support tickets.

• Publishes from GitHub on every push
• Works with Mintlify repositories
• API console from your OpenAPI file
• MCP server and llms.txt for AI agents
• Ask AI and support tickets
• Analytics for people and AI agents

Start Free→ Questions? Ask AI in our docs

No card required.