Primary navigation
Codex

Codex use case

Build and deploy internal apps

Turn a team workflow into a hosted internal app with Sites.

Difficulty Intermediate
Time horizon 30m

Use Sites in ChatGPT to build, test, and deploy internal apps, with built-in storage and auth context.

Best for

  • Teams that want to turn recurring workflows into interactive apps.
  • Apps that need lightweight structured persistence, file uploads, or workspace-oriented sharing.
  • Internal tools that benefit from building, testing, deploying, and iterating in one task.

Contents

    ← All use cases

    Build and deploy internal apps

    Turn a team workflow into a hosted internal app with Sites.

    Use Sites in ChatGPT to build, test, and deploy internal apps, with built-in storage and auth context.

    Intermediate
    30m

    Use Sites in ChatGPT to build, test, and deploy internal apps, with built-in storage and auth context.

    Intermediate
    30m

    Best for

    • Teams that want to turn recurring workflows into interactive apps.
    • Apps that need lightweight structured persistence, file uploads, or workspace-oriented sharing.
    • Internal tools that benefit from building, testing, deploying, and iterating in one task.

    Starter prompt

    Build and deploy an internal app for [team or workflow]. Goal: - [what the app should help people do] - [who should use it] - [source docs, data, or connected services ChatGPT should inspect] Requirements: - Keep the first version focused on one useful workflow. - Use D1 for structured data persistence. - Use R2 for user-uploaded files if needed. - Test the main flow, persistence, and responsive layout before deploying. Make it available to all workspace users.
    Build and deploy an internal app for [team or workflow]. Goal: - [what the app should help people do] - [who should use it] - [source docs, data, or connected services ChatGPT should inspect] Requirements: - Keep the first version focused on one useful workflow. - Use D1 for structured data persistence. - Use R2 for user-uploaded files if needed. - Test the main flow, persistence, and responsive layout before deploying. Make it available to all workspace users.

    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.

    The scope ranges from simple static sites to full-stack JavaScript or TypeScript web apps. That makes Sites a good fit for focused internal tools: onboarding dashboards, enablement 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.

    Give ChatGPT the workflow context

    Tell ChatGPT who the app is for, what people should accomplish, 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.

    You can also leverage Plugins to fetch or refresh data from internal sources.

    If you need live data fetching, you can connect to a 3rd party tool using an API key. But if you want to use plugin connections, you can schedule work from the current task to fetch data with plugins on a set schedule, update the app, and redeploy it.

    Choose storage deliberately

    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 static microsite may not need either one.

    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 with the link.

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

    Change this site's access to everyone in my workspace.

    Examples

    The Sites showcase includes sites 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.

    Related use cases