Codex Sites and Jiayang Cloud
Updated
Codex Sites hosts a site you build in ChatGPT or Codex, for people in your ChatGPT workspace and those you invite. Jiayang Cloud hosts apps from Codex, Claude Code, Cursor or a terminal, runs servers in Python, Go and other languages, and gives your code a signed token saying who is calling.
What follows about Codex Sites comes from OpenAI's docs, read on 16 October 2026 and listed at the end.
What Codex Sites does
- You build, host and share a website by describing it in ChatGPT or Codex.
- A new site is open to its owner and the workspace's admins until you change who can visit. The choices are people or groups in the workspace, the whole workspace, invited outside viewers, and anyone on the internet when public publishing is on. Where a choice is available depends on the workspace.
- Invitations to people outside the workspace are rolling out on Plus, Pro, Business and Enterprise. An invited visitor signs in with the account that received access.
- In Enterprise workspaces, public publishing is off by default, and admins decide whether members may invite outside visitors.
- A site can add sign-in. The signed-in visitor's email reaches the site in the
oai-authenticated-user-emailheader. The docs don't say whether the header is signed. - Sites serve HTTP, HTTPS and WebSockets, with a D1 database of up to 10 GB and R2 for files. The docs say some frameworks, private networks, databases and background services aren't supported, without listing them.
Side by side
| What | Codex Sites | Jiayang Cloud |
|---|---|---|
| Built from | ChatGPT or Codex | Codex, Claude Code, Cursor, the CLI, the dashboard or GitHub Actions |
| New apps | Open to the owner and the workspace's admins | Private: open to the people you share them with |
| Who you can let in | People and groups in the workspace, the workspace, invited outside viewers, or anyone | Any email address, everyone at your company's domain, a group, or the workspace. The internet only on public paths a person adds, for webhooks |
| The caller, in your code | An email header. Signing not stated | A token signed by our edge, made out to your app for 60 seconds, checked by SDKs for Node, Python, Go and Rust |
| What runs | Not stated by language. Some frameworks and background services aren't supported | Workers and static sites on every plan. Python, Go, Rust and Node servers in containers on Team and above |
| An audit log of visits | Not stated | Every request let in or refused, and every change with who made it, on every plan |
| One list for IT | Not stated | Every app, who can open it, where it sends data and when it was last opened, on every plan |
| Moving an app in | Not stated | Import from Vercel, Netlify, Replit, Lovable, Bolt, v0 or any repository, with its variables |
When Codex Sites is the better fit
When everyone who uses the site is in your ChatGPT workspace, the site fits what Sites runs, and you'd rather not install anything. It's there in the tools you already use.
Deploy from Codex to Jiayang Cloud
Add jiayang mcp to Codex, start Codex in the project, and ask it to deploy:
codex plugin marketplace add ss2d22/jiayang
codex plugin add jiayang-cloud@jiayang-cloudThe app goes live at its own address, private until you share it. Codex works with your permissions, and what it does shows in the audit log under your name. The Codex guide has the rest, including what to set when you start Codex outside the project.
Sources
- Sites, OpenAI's docs. Checked 16 October 2026.
- Publish and share, OpenAI's docs for Sites. Checked 16 October 2026.
- Data and connections, OpenAI's docs for Sites. Checked 16 October 2026.
Next
- Deploy what Codex builds, privately
- How we differ from other ways to keep an app private
- Use with Claude Code, Codex and Cursor, in the docs