Build and deploy from one task

Sites is a managed hosting service in ChatGPT. Ask ChatGPT to create an app, and it can build the project, run it for testing, deploy it, and return a URL you can share.

Sites is in public beta for eligible paid plans. It isn’t available on Free or Go, or in the EEA, Switzerland, or the United Kingdom at launch, and rollout or workspace settings can affect access.

The scope ranges from static sites to full-stack JavaScript or TypeScript web apps. That makes Sites a good fit for focused internal tools: onboarding dashboards, training hubs, searchable resource libraries, lightweight workflow apps, and reporting views.

See the Sites documentation for setup, storage, deployment, and access guidance.

Start with one useful workflow. A clear first version is easier to review, deploy, and improve than a broad request to recreate an entire internal system.

What to expect

Here is a fictional example using an attached launch brief and five sample requests. The first pass creates and checks a focused request tracker; the follow-up adds an owner filter and makes overdue requests easier to see.

ChatGPT Work

Give ChatGPT the workflow context

Tell ChatGPT who the app is for, what people should do, which source material it should inspect, and what should persist between sessions. Be explicit about the intended sharing scope and ask ChatGPT to test the main flow before it deploys.

Use plugins to fetch or refresh data from connected internal sources. Start a Sites task that uses connected apps or cloud files in Work on the web, or in Work or Codex on desktop. Use the desktop app for a local file, the built-in browser for a signed-in site, or the Codex Chrome extension for an existing Chrome session.

Choose storage for the app

Many internal apps need persistence. Sites supports two storage primitives:

• Use D1, a SQLite-compatible database, for structured data such as checklist state, bookmarks, filters, annotations, configuration, and file metadata.
• Use R2 object storage for file bytes such as uploaded documents, images, or other assets that should persist.

Keep structured metadata in D1 and larger file objects in R2. A read-only resource page or small static site may not need either one.

Sites doesn’t support data or inference residency. Don’t use it to process protected health information or payment-card data, or to enable financial transactions. Review the Sites data and usage restrictions before storing sensitive information.

Manage and share your projects

You can manage who can visit your deployed projects.

Keep a new project private while you review its content, data handling, and intended audience.

Depending on your account and workspace settings, you can share it with:

• People you invite.
• Everyone in your workspace.
• Anyone on the Internet.

Sharing lets people visit the project; it doesn’t let them edit it. To change access, open Sites in ChatGPT or ask ChatGPT directly:

Public sharing also works for a lightweight event guide, club resource page, or other site meant for people outside a workspace. In Enterprise workspaces, public publishing is off by default and an admin must enable it. Keep internal data private even when a public link is available.

Examples

The Sites showcase includes Site examples with full prompts.

• Onboarding Hub combines a first-week checklist, resources, notes, and uploaded documents. It uses D1 for user state and file metadata, and R2 for uploaded file bytes.
• Enablement Hub provides a searchable training library with filters and saved bookmarks backed by D1.
• Pulse Dashboard presents metrics, trends, and lineage details while using D1 for configuration and cached snapshots.
• Sparkboard turns employee idea intake into a workflow with authenticated submissions, voting, comments, status boards, and contributor rankings.
• Launch Cal organizes upcoming product launches into a monthly calendar with filters, risk signals, checklists, and connected-source references.
• Event Planning Hub combines event requests, approvals, templates, milestones, policy readiness, and connected planning resources.

Use those examples as starting points, then narrow the prompt around your team’s workflow and source material.