AI makes pages now. Pages need somewhere to live.
The output of an assistant is increasingly an interactive thing, not a paragraph. A page needs a home, and the sharing built into each AI tool was designed for its own users. Two tests decide whether a home is good enough: control, meaning you decide who opens it, and longevity, meaning the link outlives the chat. Here is how the options score, and what to ask for.
No card · 3 pages free · about a minute
Where should a page that AI made for you live?
Somewhere you control and that outlives the conversation. Control means you choose who can open it: a passcode, a company email gate, your own domain. Longevity means the link keeps working, shows the current version after an update, and can be taken elsewhere as a file. The sharing inside ChatGPT, Claude and personal agents usually passes one test. A lightweight host is built to pass both.
Why this is a question now
Ethan Mollick put it plainly on 6 September: because AI outputs are often interactive programs, "more non-technical people will need to find a lightweight hosting service". He uses Netlify. Most of the people he is describing have never deployed anything, and the tools they use offer a share button that seems to make the question go away.
It does not, because each share button was designed for the tool's own users. The moment the reader is a client, a contractor, a board, or a friend on a different app, the button either makes the page public or asks the reader to create an account. Neither is what you meant by "send them the link".
Test one: control
Who can open this, and did you choose that? The honest answers, from each tool's own documentation as of 19 September 2026:
- Claude artifacts. Private to you until shared. On Team and Enterprise, shared with people in your organisation or all of it, and public only if an owner allows it. On Pro and Max, public is the only way to share. There is no "this one person outside the company".
- ChatGPT Sites. Can invite named outside viewers since September, but every viewer needs a ChatGPT account to open it. Otherwise public.
- Instinct Files. Private or anyone-with-the-link, including people who do not use Instinct. No passcode, no domain of your own.
- A lightweight host. Depends on the host. The bar is: unguessable by default, a passcode or an email gate on top, your own domain when it goes to a client under your name.
Test two: longevity
Will the link you sent still open the current version later? Three things break this. A page tied to a plan or an account that changes. A revision that mints a second link, so the reader has two and opens the wrong one. And a page you cannot get out as a file, so when the tool changes, the work goes with it.
The features that pass the test are unglamorous: update in place at the same address, a version history you can restore from, and an export that is just the HTML. Ask for all three.
What to ask a host for
- Private by default, with an unguessable link.
- A passcode or a company email gate when the page is not for everyone.
- Your own domain, so a client sees your name and not the host's.
- Updates that keep the link, and a history you can put back.
- A signal that it was opened, and a way for the reader to answer.
- Readable by the reader's assistant as well as the reader: a plain Markdown form of the page.
- An exit: the page as a file, on your terms.
Stacktree was built to that list, and it is deliberately boring about it. Your assistant publishes with one request or one sentence, the link is private, the gates are a switch each, the page lives on your domain if you want, updates keep the address, and every page is also readable as Markdown at its own URL. If you leave, you take the files.
The two tests, per option
| Criterion | Built-in sharing (Claude artifacts, ChatGPT Sites, Instinct Files) | A lightweight host built for it (Stacktree) |
|---|---|---|
| Send to one person outside the tool | Public link, or they need an account | Private link, no account |
| Passcode or email gate | No | Yes |
| Your own domain | ChatGPT Sites only | Yes |
| Update keeps the same link | Claude yes, others vary | Yes, with version history |
| Know it was opened | No | Yes |
| Readable by an agent as Markdown | No | Yes, at the same URL |
| Zero setup, inside the chat | Yes | One sentence to your agent |
| Take the page elsewhere as a file | Export where offered | Always |
Frequent questions
Where should I host a page that AI made for me? +
Is a ChatGPT Sites page private? +
Can I share a Claude artifact with someone outside my organisation? +
What does longevity mean for an AI-made page? +
Do I need to be technical to host a page? +
What should I ask a host for? +
Related guides
- Share a Claude artifact without making it public The plan-by-plan sharing rules and the way around them.
- What ChatGPT Sites is, and what it is for The honest limits and who it suits.
- Private HTML hosting The unguessable-link model and the gates you can add.
- Self-hosting Stacktree The exit, documented.
- Ask this page A page that can take the reader's question.
Sources and further reading
- Ethan Mollick, 6 September 2026 ↗ The post: interactive outputs mean non-technical people need lightweight hosting; the built-in options have control and longevity problems.
- Publish and share artifacts (Claude Help Center) ↗ Audiences per plan, and what sharing outside an organisation allows.
- Instinct: shareable Files ↗ Private or anyone-with-the-link pages from a personal agent, 18 September 2026.
Give the page a home you control.
Private by default, your domain, updates that keep the link. Three pages free, no card.
Sign up free →