TL;DR. It depends on what ChatGPT gave you. A single HTML page can go on almost any static host for free. Anything with a database, logins or a server part needs a host that runs code and keeps data, which usually means setting up two or three services and copying files across. The shortest path is to skip the copying: connect a hosting app to ChatGPT and let it deploy the app itself, database and sign-in included. (Updated October 2026.)
First, look at what you have
"An app ChatGPT built" can mean very different things, and the right host follows from which one it is:
- One HTML file (maybe with CSS and JavaScript inside it). A calculator, a landing page, a quiz. It runs entirely in the browser.
- A front end that saves things, but only in the browser (often
localStorage). It looks like an app, but every visitor sees only their own data, and it's gone if they clear their browser. - A front end plus server code: a Node or Python file, an API, SQL for a database, maybe a list of environment variables to set. This is a real app and needs a real host.
The options
| Where | Fits | What you do | Watch out for |
|---|---|---|---|
| A static host (drag-and-drop hosts, GitHub Pages and similar) | One HTML file, or a front end with no shared data | Download the files from ChatGPT and upload them | No database and no server, so nothing is shared between visitors and no secrets can be kept |
| A general app platform plus a separate database | Front end plus server code | Create the services, copy the files in, create the tables, set the environment variables, connect a domain | Every change ChatGPT makes means repeating the copy-and-deploy loop; sign-in and email are more services to add |
| OpenAI's own Sites feature | Lightweight sites and internal pages | Ask for it from Codex or ChatGPT where your plan includes it | Availability depends on plan and region, and the code and hosting stay on OpenAI's platform (see what Codex Sites is) |
| A hosting app connected to ChatGPT | All three kinds | Connect once; ChatGPT creates the project and deploys it | A one-time connect step; ChatGPT's own message limits still apply |
General characterisations based on public information as of October 2026. Check each vendor for current details.
The traps when you host it yourself
If you take the copy-and-paste route, these are the problems that catch most people:
- API keys in the browser. ChatGPT will sometimes put an OpenAI, Stripe or email key straight into the front-end code to make a demo work. On a public site anyone can read it. Keys belong in server code and environment variables.
- localStorage is not a database. It's per browser, per device. If two people need to see the same bookings or posts, you need a real database.
- The code and the host disagree. ChatGPT writes for a generic setup; your host expects a certain folder layout, start command or runtime version. Expect a few rounds of "it works locally but not there".
- Sign-in is its own project. Password storage, sessions and reset emails are easy to get wrong. Use a host or service that provides them rather than having ChatGPT write them from scratch.
- Updates drift. After a few edits, the version in your chat and the version that's live stop matching. Keep one source of truth.
The shortcut: let ChatGPT deploy it
Every trap above comes from the gap between where the code is written (your chat) and where it runs (somewhere else). Close the gap and they mostly disappear. When a hosting app is connected, ChatGPT writes straight into the project, keeps keys on the server side, creates real tables, and deploys the same code you just discussed.
-
Connect Hatchable
Open Hatchable in the ChatGPT app directory and click Connect. Approving on hatchable.com creates your free account. This works on any ChatGPT plan, free included (as of August 2026).
-
Hand over what you have
In the chat where ChatGPT wrote the app, say: "Put this app live on Hatchable. Use a real database instead of localStorage, and keep any API keys on the server." If the app lives in another chat, paste the code into a new one with the same request.
-
Get the live link
ChatGPT creates the project, writes the files, sets up the tables and deploys. You get a
your-app.hatchable.siteaddress that works for anyone. A custom domain can be added later.
Every Hatchable project includes a Postgres database, sign-in for the app's users, email, scheduled jobs and file storage. The free plan is $0 with unlimited private projects and one app published to the open web; Builder is $12 a month for unlimited published apps and custom domains. More detail in deploy an app from ChatGPT, or start from scratch with building an app with your ChatGPT subscription.
Stop copying code between ChatGPT and a host.
Connect Hatchable and ChatGPT deploys the app itself, with a database and sign-in included. Free plan, no card.
Get started free →Frequently asked questions
Can I host a ChatGPT-made website for free?
Yes. A single HTML page can go on many free static hosts. For an app with a database and logins, Hatchable's free plan publishes one app at no cost, with no card.
Why does my app lose its data on refresh or on another device?
It is probably saving to browser storage such as localStorage. That data lives in one browser only. Ask ChatGPT to move it to a real database, which a host like Hatchable provides with every project.
Is it safe to leave an API key in the code ChatGPT wrote?
Not in front-end code on a public site, because anyone can read it. Keys should live in server-side code and environment variables. When ChatGPT deploys through Hatchable, ask it to keep keys on the server.
Can I use my own domain?
Yes. Apps start on a hatchable.site address, and you can connect your own domain on the Builder plan.
Do I need ChatGPT Plus for this?
No. Listed apps such as Hatchable connect on free ChatGPT accounts as of August 2026. A paid plan mainly gives you more messages for longer builds.