What is OpenAI Sites?

Sites is a Codex feature OpenAI launched in June 2026 that turns plain-text prompts into hosted, interactive web apps — dashboards, internal tools, knowledge bases. It deploys to OpenAI-managed hosting and gates access behind Sign in with ChatGPT. At launch it's a preview limited to ChatGPT Business and Enterprise workspaces.

How is Repage different from OpenAI Sites?

OpenAI Sites is an app builder tied to ChatGPT. Repage is a vendor-neutral place to share AI-generated HTML and get feedback on it. You can publish from Claude, ChatGPT, Cursor, Windsurf, or any agent over MCP or the REST API, and anyone with the link can view and comment — no ChatGPT seat required. Repage focuses on static HTML documents (reports, plans, prototypes), not hosted backend services.

Can I use Repage with ChatGPT too?

Yes. Repage connects to ChatGPT just like it connects to Claude and other agents. So you can keep using ChatGPT to generate the HTML and use Repage as the shareable, commentable home for it — including on plans where OpenAI Sites isn't available.

Do the people I share with need an account?

No. A Repage link works for anyone — they open it, read the rendered HTML, and leave inline comments. You can add a password if you want to gate it. OpenAI Sites, by contrast, requires viewers to sign in with ChatGPT through your workspace.

Repage has a free tier you can publish on today. OpenAI Sites is currently a preview restricted to ChatGPT Business and Enterprise plans.

Repage vs OpenAI Sites (ChatGPT)

Two different jobs

They sound similar — both take AI-generated HTML to a URL — but they solve different problems. OpenAI Sites is a builder: it spins up interactive internal apps and hosts them. Repage is a sharing-and-review layer: it takes HTML an AI already produced — a report, a plan, a one-off dashboard — and gives it a home where people can read it, leave inline comments, and track versions over time. If you want a maintained internal application, Sites is aimed at that. If you want to send a rendered document to teammates and get feedback, that's Repage.

Side by side

Capability	Repage	OpenAI Sites
Works with any AI assistant	Claude, ChatGPT, Cursor, Windsurf — via MCP or REST	ChatGPT / Codex only
Inline comments from reviewers	Yes — threaded, with reactions	No — built for apps, not review
Version history & revert	Yes	Limited
Viewers need a vendor account	No — just the link (optional password)	Yes — Sign in with ChatGPT
Available on free / personal plans	Yes — free tier	Preview, Business & Enterprise only
Group documents into shareable projects	Yes	n/a
Builds hosted backend apps	No — static HTML documents	Yes — that's its focus

Use Repage with the agent you already use

You don't have to be in ChatGPT Enterprise to share AI-built HTML. Repage connects to whatever you're using — so the same workflow works whether the HTML came from Claude, ChatGPT, Cursor, or Windsurf. Ask your agent to publish to Repage and it returns a link you can drop into Slack or email.

What people actually share

Repage is built around static HTML — no backend, no servers to keep alive — which is exactly what most AI output is. A few common ones:

Data reports. Your agent turns last quarter's numbers into a styled dashboard, you share the link with your team, and they comment inline on what stands out.
Plans and proposals. A roadmap, a PRD, a project brief — published as a rendered page people can react to and thread comments on, instead of a wall of chat text.
Interactive workout plans. Ask Claude or ChatGPT to build your training plan as an HTML page with rest timers and check-off buttons for each set, publish it to Repage, and pull it up on your phone at the gym — or send it to a coach for notes.
Anything you want to reference later. Because every version is kept, the link stays the same even as the content evolves.

The common thread: the AI has full creative freedom to build rich, interactive HTML, and Repage gives that output a durable, commentable home — without locking you into one assistant.

Publish AI HTML from any agent — not just ChatGPT

Publish HTML from any AI assistant, collect comments, keep every version.

Publish a document

Frequently asked questions

What is OpenAI Sites?: Sites is a Codex feature OpenAI launched in June 2026 that turns plain-text prompts into hosted, interactive web apps — dashboards, internal tools, knowledge bases. It deploys to OpenAI-managed hosting and gates access behind Sign in with ChatGPT. At launch it's a preview limited to ChatGPT Business and Enterprise workspaces.
How is Repage different from OpenAI Sites?: OpenAI Sites is an app builder tied to ChatGPT. Repage is a vendor-neutral place to share AI-generated HTML and get feedback on it. You can publish from Claude, ChatGPT, Cursor, Windsurf, or any agent over MCP or the REST API, and anyone with the link can view and comment — no ChatGPT seat required. Repage focuses on static HTML documents (reports, plans, prototypes), not hosted backend services.
Can I use Repage with ChatGPT too?: Yes. Repage connects to ChatGPT just like it connects to Claude and other agents. So you can keep using ChatGPT to generate the HTML and use Repage as the shareable, commentable home for it — including on plans where OpenAI Sites isn't available.
Do the people I share with need an account?: No. A Repage link works for anyone — they open it, read the rendered HTML, and leave inline comments. You can add a password if you want to gate it. OpenAI Sites, by contrast, requires viewers to sign in with ChatGPT through your workspace.
Is Repage free?: Repage has a free tier you can publish on today. OpenAI Sites is currently a preview restricted to ChatGPT Business and Enterprise plans.

Repage vs OpenAI Sites