ChatGPT Sites hits the Hacker News front page: 209 points, 218 comments — prototype or production?
On October 3, 2026, Hacker News put Sites in ChatGPT near the top of the front page with roughly 209 points and 218 comments, turning the quiet public-beta hosting feature into a practitioner debate about whether it is a prototype host or production-ready.
What happened
On October 3, 2026, Hacker News put "Sites in ChatGPT" near the top of the front page — roughly 209 points and 218 comments by the time the thread settled. The link was not a surprise launch post; Sites in ChatGPT has been in public beta for months. The thread forced the practitioner questions product pages skip: is it a toy, a prototype host, or something you would put a real audience on?
The core debate — prototype vs production
Top comments described Sites as underrated for quick, same-day app ideas (a maze game spun up after a concert, an offline-friendly festival schedule, a campus food guide). Several commenters called it "not production-capable" while others shipped real (if small) tools. OpenAI's own docs settle the URL semantics: every Sites deployment is a production deployment — the product gives you no separate staging hostname; discipline is in the "save a version" step before "deploy a version".
Doc-backed answers HN actually wanted
(a) Sign in with ChatGPT is optional on public Sites; headers carry the authenticated user's email (oai-authenticated-user-email) and optional full name, and OpenAI advises keeping authorization decisions in server-side code. (b) Storage: D1 relational storage up to 10 GB per Site, R2 object storage with no fixed limit; temporary UI state should not burn durable storage. (c) Custom domains exist where available — you own and map your own DNS; custom domains are not available in Enterprise workspaces at launch. (d) No data or inference residency at launch, so OpenAI's docs say do not use Sites for PHI, payment-card data, or under-13 audiences.
Honest limitations from the thread
HN roasted parts of OpenAI's own showcase demos — Tidal House for unreadable text on an image, and "Below the Surface" called AI slop "on first contact". Unsupported frameworks, no raw TCP, beta usage limits that can block new or high-usage public Sites, and the .chatgpt.site lock-in aesthetic ("early-2000s free host vibes") all came up. The takeaway: hosted polish is not automatic — showcase prompts from OpenAI staff still need a human pass.
Why it matters
The thread marks Sites' transition from a quiet public beta to a practitioner-vetted hosting option: real small tools are shipping, but the docs-backed limits — no staging hostnames, no residency, beta usage caps — decide whether your use case is a prototype or a production fit.
Verified October 3, 2026
Sources
Sources
Get updates like this every morning
- ② Card on Stripe
- ③ 7 days free
Then $2/month · cancel anytime in one click