You built a page with an AI tool. Three places it can live — the builder's own share URL, a public deploy, or a private link — and a clear way to decide between them based on whether the page has a backend and who is supposed to reach it.
You typed a sentence, the AI tool wrote the page, and now it runs — the form submits, the chart redraws, the calculator returns a number. The build was the fast part. The decision that follows is quieter, and it is the one people rush: this page has to live somewhere, and wherever you put it quietly decides who can reach it.
That is the part worth slowing down for. Leave the page on the tool's URL and the audience is "whoever has an account on that tool." Push it to a public deploy and the audience is "anyone, plus search engines." Put it behind a private link and the audience is "the people you sent it to." You are not picking a host, you are picking a reach. So settle reach first, then the host falls out of it.
Before comparing destinations, answer two things about the page in front of you.
Does your server run anything? Not "does it call an API" — does code you own execute on a server somewhere. A database it writes to, a login, server-side routes, a payment webhook. If yes, this page is not a file; it is a project, and it needs a platform that runs your server. That is the honest boundary, and it is worth naming plainly: Vercel and Netlify are the right tools for that job. No static-file host replaces them, and you should not try to make one.
Who is supposed to see it? Three answers, mapping cleanly to three destinations:
Most AI-built pages — a landing draft, a one-page proposal, an interactive demo, a portfolio, a private dashboard — have no backend and a specific, non-public audience. That combination points at the private link, which is the option people skip past because the tool's share button sits right there in the editor.
Every AI builder ships a share path. Claude has artifact links, v0 publishes to a .v0.app subdomain, Lovable to its own, and Replit, Cursor, and Bolt each have theirs. One click, instant, free.
What it is for: a glance from someone already inside that world. A co-founder who also uses the tool, a quick "does this look right" before you go further.
Where it gets awkward: the viewer often needs an account on that platform to see it properly, the link can drag the whole prompt history and construction site along with it, and the URL ends in someone else's domain — which reads differently to a hesitant client than a clean link does. It also pins the page's lifespan to that project inside that tool. The moment you hand the page to someone outside the tool, this option starts working against you, and the share link quietly failing to open for them is the most common way that surfaces. Tool-specific exports have their own walkthroughs — for instance, a multi-file Codex bundle as a ZIP, and a Claude or ChatGPT artifact shared privately.
Export the page and push it to Vercel, Netlify, or Cloudflare Pages. This is the right shape when the page is meant to be found — a launched product landing, a marketing page anyone should reach — or when it carries the backend from question one.
The cost is that you now own a project: a deploy pipeline, a build step, a thing to maintain. For a page that changes weekly and runs no server logic, that is more weight than the moment needs. The full breakdown of when a deploy platform earns its overhead is its own piece; the short version is that a deploy is correct precisely when the page is public and either dynamic or frequently changing.
If the page is self-contained and meant for specific people, you don't need a deploy pipeline. Drop the HTML or ZIP, get a private link in under a minute — the viewer needs no account.
Export the page as a self-contained .html file or a .zip bundle (HTML + CSS + JS + assets), drop it at a private-link host, and get back an unguessable URL. The page renders in any browser — JavaScript runs, CSS applies, CDN libraries load — and it is private and hidden from search by default. The viewer needs no account: you send the link, they open it.
This is the fit for the large middle of AI-built pages — no backend, a specific audience, and a life that should outlast the project that produced it. It is the same slot whether the page started as a vibe-coded app, a portfolio, or a client proofing link.
The controls sit on top, not behind a wall. Password-protect the page when you want a second factor — free on every plan. A link that never expires when the page should stay up — that is Solo. A custom domain and white-label when the page should read as fully yours — that is Studio. And the escape hatch for the "I changed my mind, make it public" case is a per-page searchable opt-in: one page flips to indexable while everything else in your account stays private.
Run the page through it: Backend? → deploy. Public and findable? → deploy or a searchable opt-in. Specific people, self-contained? → private link. Just a glance, just you? → the tool's own URL is fine.
Most AI-built pages land on the third answer — the exact one the tool's share button trains you to skip. Decide reach first, and the host stops being a guess.
Private and password-protected are free on every plan, with one always-on link (free links default to a 7-day expiry). Solo ($4.99/mo) makes links permanent and adds detailed analytics; Studio ($14.99/mo) adds a custom domain and white-label. The searchable opt-in starts free — one page on the free tier, five on Solo, unlimited on Studio.
A private link is not a deploy platform, and it does not pretend to be. It runs no server and hosts no database — that is Vercel and Netlify's job, and they do it well. It owns the slice they make heavy: the self-contained page that specific people should reach, without a build step and without putting an unfinished thing on the open web.
Not to a public link — on any plan. On Pro and Max, a connector-backed artifact can't be shared at all. Here's the mechanism that makes that rule inevitable, and what to do once you know which page you're actually building.
Hit a ChatGPT Sites usage limit? Your Sites aren't gone. Here's how to tell the ones that are just pages, which travel, from the ones that need Sites underneath them.
The AI tool built the page. Sending it to a client is a second job: stripping the construction site, making it read as yours, and putting it behind a private link. A practical checklist for turning AI output into a client-ready handoff.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.