Someone finishes a page with an AI, looks at it sitting on their own machine, and asks where to host it. The answers arrive fast and confidently, and they are usually about something else.
"Where do I host this?" is rarely a request for the name of a hosting company. It is seven different problems wearing the same four words. Below is each one, taken from threads where people asked it, with a short answer.
The misreading is measurable. A search-results analysis for where to host ai generated website returned twenty-nine results, more than half of them product pages for tools that build websites. Two were about publishing a site you had already finished. Ask "I made this, where does it go" and you get an offer to make it again.
One exchange shows the pattern whole. Someone asked r/vibecoding for free hosting: "I'd like to test it in a live environment to see how it performs. Is there anywhere I can test it for free?" The top reply was "local host works for testing." True, useless, and the poster said why in one line:
I need to show others what I've done :)
They never wanted free hosting. They wanted a link. Nobody could tell, including the person asking, until the wrong answer arrived.
The question under the question
Two dozen threads across r/ClaudeAI, r/vibecoding, r/nocode and r/ChatGPTCoding keep surfacing the same seven. Find yours first; the answer gets much shorter once you have.
- Question 1Skipping the devopsYou want the result without learning the machinery
- Question 2ChoosingYou want someone to narrow the list for you
- Question 3The billYou want to know what free costs later
- Question 4A link to sendYou want one address you can give someone
- Question 5PermanenceYou want to know if it survives next month
- Question 6Changing itYou want to fix a typo without a ceremony
- Question 7What you haveYou are not sure it is a website yet
One thing sits under nearly all of them. The AI that built the site has quietly become the manual for publishing it. "if I wanted to solve this I would just ask Claude how to do it," runs one reply; "VPS and ask claude for deployment," runs another.
People do exactly that, and they can tell it is not working. One poster described asking Claude "literally what commands to run on my own VPS," then added, "It doesn't seem like a good idea for production." Another, in the same thread as the second quote: "I can hack it together if claude guides me but it's honestly still flaky."
The agent can dictate server commands. Dictating them is not the same as being the one who publishes.
"Can I do this without becoming a devops person?"
The most common version by far. Someone asked r/vibecoding how non-technical people were coping:
Claude Code has made is super easy for me to build apps locally (cue localhost joke), but how are people making sure their apps are deployed/secured/production ready?
A post in r/ChatGPTCoding hit the same wall from the other side: "overwhelmed by the amount of hosting options," no appetite for "complex setups, Github actions or servers yet," and one want:
I just want to get my code from my folder to a site easy as that.
What is actually being asked: is all this machinery required, or is there a door for people like me?
The short answer: for a finished static site, most of it is optional. Repositories, builds, environments and pipelines protect applications that hold data and run code on a server. A folder of HTML, CSS, images and browser JavaScript has none of those properties and inherits the apparatus anyway. That mismatch has an argument of its own.
The exception runs through this whole page: a real database, accounts or server-side code, and none of the machinery is overhead.
"Which one should I pick?"
The literal reading, and a real question. It produces a pile of names and no way to choose. One thread collected Vercel, Render, Firebase and Hetzner within a few replies. The top comment, at fifty upvotes, was one word:
localhost🥲
What is actually being asked: narrow this down for me, because I cannot tell what the differences mean.
The short answer: three questions settle it before any brand name matters. Site or application? Deciding which you built removes most of the list. Will you keep changing it? Hosts differ enormously in what a small edit costs, which is question six. Your own domain? Almost all of them can, but the step differs.
If the site came from Bolt, Lovable, v0, Claude, ChatGPT or Cursor, the route map for AI-generated sites starts from that source. Lovable is its own case: it hosts the site free already and only part of a project can leave, so the Lovable guide is separate.
"Is it free, and what does it cost when it isn't?"
Free is where most people start and where the confusion is thickest. From one thread:
to have it host my website with no downtime, it costs a lot, and the free option only makes sense for personal use
And, in the same post, the feeling underneath the question:
I see people with 10-20 vibecoded website hosted, so I must be missing something.
What is actually being asked: where does free stop, and will it stop somewhere embarrassing?
The short answer: storage and serving for a static site are cheap, so a free plan here is usually a real offer rather than a trick. The line falls at predictable steps rather than on traffic: your own domain, removing a host's badge, a project count, anything server-side. Bandwidth rarely catches a landing page. Free custom domains are the exception worth knowing: EdgeOne Pages includes one, and so does Google Sites, where the real question is whether an agent can publish there at all. Paid can undercut free on the same line: InstaPods bundles domains with automatic SSL from $3 a month.
Find your line before you need to know. Some free tiers hide it in a countdown, where the link expires unless you pay. That answers the second quote too: nobody with twenty sites online is paying twenty bills.
Ours falls in the same place. The free plan publishes up to 50 sites of 25 MB each and is not a trial. It holds back your own domain and the right to remove our badge, plus the size of the limits. Upgrading is self-serve, by card, effective immediately. Solo is $12 a month; the full list is on the landing.
"I just need a link I can send someone"
Often the true question behind the others, and the one least likely to be said out loud. It is also, measurably, the common case: 45.1% of published projects are not public at all. A post put the moment precisely:
At some point you want it at a proper link you can send round and keep updating.
A thread rejected every alternative in turn: sending the file ("people doesn't know they have to download it"), the code ("they can't open it"), a screenshot ("loses interactivity"), and the developer-grade options, "too technical for most people."
What is actually being asked: how do I turn this into one address a non-technical person can open?
The short answer: an address is not the same purchase as a hosting plan, and
the gap is where the confusion lives. What you have to get right is small: every
file the page refers to travels with it, and the main file is named index.html
so the address works with nothing after the slash. That and
a few details is the job. Some tools answer this
request exactly: Tiiny Host takes a zip and returns a link,
HTML Pub keeps generating and hosting together.
Check what the link is worth first. Netlify Drop is the classic answer here, and a drop made without signing in now comes back password-protected until somebody claims it, which undoes the point. Netlify's platform is a separate decision now that its free plan runs on a credit meter, and the numbers are here.
One finished page for one person, today? Paste it into the HTML viewer and share the HTML file as a link that opens for a day, no account. Markdown rather than a page? Start from the recipient's job. A folder of material rather than code? An agent can turn it into pages and publish them.
"Will it still be there next month?"
Less common, and the one people regret not asking. A thread in r/nocode put the fear plainly:
a couple of them lock the output inside their platform. If I stop paying, the site vanishes.
I want the speed of a prompt but the freedom to export.
The reply that stuck: "Most AI builders are landlords, not sellers."
What is actually being asked: whose site is this, and what happens when I stop paying attention to it?
The short answer: ask what you would be left holding. Ordinary files you can download mean the worst case is an afternoon of work. A project that lives only inside somebody's editor means the worst case is starting over.
That thread also had the only test worth trusting: build one page, export it, put it somewhere else, see what breaks. Do it on day one, when finding out is free. A page living inside a chat product belongs to that product, and temporary links deserve the same suspicion.
"How do I change it once it's live?"
Everyone hits this on day two and almost nobody asks on day one. From the thread quoted above:
if I need to fix a typo or tweak a number, I have to re-prompt Claude (which sometimes breaks other things)
A commenter turned the annoyance into a criterion: "how do you handle the case when the client comes back 2 days later asking for a small change?"
What is actually being asked: what does a one-word fix cost me, every time, forever?
The short answer: it depends on whether the host keeps your site as files you edit in place or as the output of a process it reruns. Over a year of small corrections that difference compounds. Regenerating the page from a fresh prompt is the most expensive option, because it risks everything else to fix one number. What that looks like from the inside is worth knowing before you pick, and it is the axis our Static.app comparison runs on.
Undo is the other half. Going back to the version that worked should be a decision, not a reconstruction.
"Is this even a website, and can it have my name on it?"
Two questions that turn out to be one: does this thing have an identity of its own? The clearest case is a thread title that asked four at once, because the poster could not tell which was his real one:
Published website artifacts - is hosting on Anthropic secure? Does free version support this and can I customize the url? What is better - 1) publish website artifacts (less work) or 2) develop html "package" THEN push to GitHub and manually update each web refresh
Later, someone asked r/ClaudeAI whether an artifact could carry a custom web address: "I was curious how I could host this on my website… Total noob here. Any help would be welcome!" No replies.
What is actually being asked: is what I am looking at a website, or a preview of one?
The short answer: if it only opens inside another product's interface, it is a preview with a link. That beats a real site for showing a colleague, and it is the wrong thing when you need an address that is yours, survives the chat that made it, and can carry your own domain. What a published artifact is has the specifics.
Your own name on it is two purchases joined by one DNS record. A domain is not hosting and hosting is not a domain, which is why this feels harder than it is. Which record, and where it goes takes ten minutes.
When the answer is none of these
Four cases where you are in a different conversation.
You built an application, not a site. Databases, accounts, private keys, scheduled work. The pipeline is not overhead here. Working out which one you have is the first move.
You actually wanted a builder. To keep editing a site by hand for years with no coding tool in the loop, a builder beats anything on this page, and we would rather say so. The alternatives pages go tool by tool, including Squarespace and, for anything that might really be an application, Bubble. Where each still wins is a real comparison, and for the AI builders, what Durable includes and costs is the same kind of answer.
Your content already lives somewhere that publishes it. If the page you want online is a Notion page, Notion is the shortest route: what Notion Sites gives you free, and where it stops.
You wanted to run the stack yourself. A legitimate answer, and the reader most published hosting guides are written for, which is part of why they feel wrong to everyone else.
Where Birta fits
We answer questions four, six and seven, and not all seven.
The tool that already holds your finished files sends them to a live HTTPS address, with no repository or build step in between. Images and fonts travel with the site. The last ten published versions are kept, so a wrong change rolls back instead of being rebuilt, and a later edit goes through the same connection. A custom domain points at it on a paid plan, as almost everywhere.
The limits: static sites only, so HTML, CSS, images, fonts and browser JavaScript. Video and PDF files are not served. A contact form needs no backend and replies land in the project; payments on your own site are not something we provide today. A database or server-side code means the wrong layer, and question one applies.
Someone in that June thread described the missing piece better than we would have:
your product lacks the most important feature. an mpc so any user can simple say to claude: publish this page to XXX and give me a link.
Typos and all, that is the request. The agent that built the page should publish it through one open standard rather than an integration per tool, instead of reading you server commands. How it gets from a pasted line to a live page, and where it stops to ask you, is worth reading first.
Ask the agent that built it to publish it
The last step is always the same: the tool with your finished files sends them to a live address, versions kept. Static sites only.