Where to Host an AI-Generated Website: 7 Questions That Decide It

Someone finishes a page with an AI, looks at it sitting on their own machine, and asks where to host it. The answers arrive immediately and confidently, and they are usually about something else.

Here is the useful reframe. "Where do I host this?" is almost never a request for the name of a hosting company. It is one of seven quite different problems wearing the same four words, and the right answer depends entirely on which one you have. Below is each of the seven, taken from threads where real people asked it, with a short answer to each.

That the question gets misread is not a hunch. Running a search-results analysis for the phrase where to host ai generated website in August 2026 turned up twenty-nine results, and more than half were product pages for tools that build websites. Only two were about putting a site you had already finished somewhere. The most common response to "I made this, where does it go" is an offer to make it again.

You can watch the misfire happen in a single exchange. In March 2026 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." Which is true, and 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

Reading through two dozen threads across r/ClaudeAI, r/vibecoding, r/nocode, r/ChatGPTCoding and a handful of others, the same seven questions keep surfacing. Find yours first; the answer is much shorter once you have.

1. Question 1Skipping the devopsYou want the result without learning the machinery
2. Question 2ChoosingYou want someone to narrow the list for you
3. Question 3The billYou want to know what free costs later
4. Question 4A link to sendYou want one address you can give someone
5. Question 5PermanenceYou want to know if it survives next month
6. Question 6Changing itYou want to fix a typo without a ceremony
7. Question 7What you haveYou are not sure it is a website yet

One thing shows up underneath nearly all of them, and it is worth naming early: the AI that built the site has quietly become the manual for publishing it. In thread after thread, the recommended next step is to go back and ask the model. "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 quite 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 above, put it more bluntly: "I can hack it together if claude guides me but it's honestly still flaky."

The agent can dictate server commands. Being able to dictate them is not the same as being the one who publishes.

"Can I do this without becoming a devops person?"

The most common version of the question, by some distance. In August 2026 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 March 2026 post in r/ChatGPTCoding described the same wall from the other side: "overwhelmed by the amount of hosting options," not wanting to deal with "complex setups, Github actions or servers yet," and wanting one thing:

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 the machinery is optional. Repositories, build commands, environments and pipelines exist to 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, because the apparatus is what publishing came to mean. If that mismatch is the thing bothering you, it has a longer argument of its own.

The exception is real, and it is the same one throughout this page: if your project genuinely owns a database, accounts or server-side code, none of that machinery is overhead.

"Which one should I pick?"

The literal reading, and a real question. It reliably produces a pile of names and no way to choose between them. One December 2025 thread asking what people use collected Vercel, Render, Firebase and Hetzner within a handful of 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: we do not run a ranking, and a ranking would not help, because three questions settle it before any brand name matters.

Is it a site or an application? A folder of browser files and something with a database need genuinely different homes, and deciding which you built removes most of the list immediately. Will you keep changing it? Hosts differ enormously in what a small edit costs you, which is question six below. Does it need your own domain? Almost all of them can, but the step where that happens differs.

Answer those three and the shortlist is short. Start from brand names and you will be comparing feature tables that do not describe your situation.

If the site already came from Bolt, Lovable, v0, Claude, ChatGPT or Cursor, the AI-generated website hosting route map starts from that known source and sends you to its current native, connected or export path. Lovable is the one worth reading on its own, because it hosts the site for free already and only part of a project can leave: that is the Lovable hosting guide.

"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 a May 2026 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: for a static site, the storage and serving are genuinely cheap, which is why a free plan here is usually a real offer rather than a trick. The line tends to fall in predictable places rather than on traffic: attaching a custom domain, removing a host's badge, going past a project count, or anything that runs server-side. Bandwidth is rarely what catches a landing page. Free custom domains are the exception worth knowing about: EdgeOne Pages offers them, and the comparison with Birta is mostly about what else comes bundled with a full-stack platform. Google Sites gives one away too, so that comparison turns on something else entirely: whether an agent can publish to it at all. A paid host can undercut a free tier on exactly that line: InstaPods includes domains with automatic SSL from $3 a month, a quarter of what Birta charges for the first one.

The honest advice is to find out where your line sits before you need to know, not after. Some free tiers hide the line in a countdown, the link expires unless you pay, which is the embarrassing version of the question. That is also the answer to the anxiety in the second quote: the people with twenty sites online are not paying twenty bills, they are running twenty things that are cheap to run.

"I just need a link I can send someone"

Often the true question hiding behind all the others, and the one people are least likely to say out loud. A June 2026 post described the moment precisely:

At some point you want it at a proper link you can send round and keep updating.

A May 2026 thread worked through the alternatives one at a time and rejected all of them: sending the file ("people doesn't know they have to download it"), sharing the code ("they can't open it"), a screenshot ("loses interactivity"), and the developer-grade options, which were "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: you need an address, which is not the same purchase as a hosting plan, and the gap between them is where the confusion lives. What you actually have to get right is smaller than it looks: every file the page refers to has to travel with it, and the main file needs to be named index.html so the address works without anything after the slash. That, and the handful of details around it, is most of the job. Some tools are built around exactly this request: Tiiny Host takes a zip and hands back a link, HTML Pub bundles the generating and the hosting into one place. The Tiiny Host comparison and the HTML Pub one are about what each does after you publish.

Check what the link is actually worth before you send it, though. Netlify Drop is the classic answer to this exact request, and a drop made without signing in now comes back password-protected until somebody claims it, which undoes most of the point if the whole idea was one address a non-technical person can open.

If the thing you have is Markdown rather than a finished page, start with the recipient's sharing job: source review, co-editing, a fixed snapshot, and an updateable public page need different handoffs. And if the folder holds material rather than code, an agent can turn it into pages and publish them without you assembling anything first.

"Will it still be there next month?"

Less common, and the one people regret not asking. A July 2026 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. If your site exists as ordinary files you can download, you can move it, and the worst case is an afternoon of work. If it exists only as a project inside somebody's editor, you cannot, and the worst case is starting over.

A commenter in that thread suggested the only test worth trusting, and it is a good one: build one page, export it, put it somewhere else, and see what breaks. Do it on day one, when it costs you nothing to find out. Temporary links deserve the same suspicion. Plenty of quick-share tools are honest that the link expires, and a page living inside a chat product belongs to that product rather than to you.

"How do I change it once it's live?"

Everyone hits this on day two, and almost nobody asks about it on day one. From the same May 2026 thread:

if I need to fix a typo or tweak a number, I have to re-prompt Claude (which sometimes breaks other things)

A commenter asked the question that turns this from an 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 your host stores the site as files you can edit in place, or as the output of a process it has to run again. Changing one line and publishing the whole site again are different operations, and the difference compounds over a year of small corrections. Regenerating the page from a fresh prompt is the most expensive option of all, because it puts everything else on the page at risk to fix one number. What that actually looks like from the inside is worth understanding before you pick, not after. It is also the axis our Static.app comparison is built on: not features, but what an update costs a year in.

Being able to undo is the other half. If a change goes wrong, 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 small questions that turn out to be the same one: does this thing have an identity of its own? The clearest example is a thread title from August 2025 that asked four questions 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

Seven months later, someone asked r/ClaudeAI whether an artifact could have a custom web address: "I was curious how I could host this on my website… Total noob here. Any help would be welcome!" The thread received no replies at all.

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 can be exactly the right thing, because it beats a real site for showing a colleague. 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 actually is covers the specifics.

As for your own name on it: a custom domain and a host are two separate purchases, joined by one DNS record. Buying a domain does not get you hosting, and hosting does not get you a domain, which is why this feels harder than it is. Which record to add and where it goes takes about ten minutes once you know which one you need.

When the answer is none of these

Four cases where the honest answer is that you are in a different conversation.

You built an application, not a site. Databases, user accounts, private keys, scheduled work. The pipeline is not overhead here, and you should use something built for it. Working out which one you have is the first move, and it is not always obvious from the outside.

You actually wanted a builder. If you want to keep editing a site by hand for years without a coding tool anywhere in the loop, a website builder is a better answer than anything on this page, and we would rather say so. The alternatives pages go tool by tool on exactly that question, including Squarespace and, for anything that might really be an application, Bubble. Where each of them still wins is a real comparison, not a courtesy, and if the builder you have in mind is one of the AI ones, what Durable includes and what it costs is the same kind of straight answer for that corner.

Your content already lives somewhere that publishes it. If the page you want online is a Notion page, the shortest route is Notion itself, and this whole list is beside the point. What Notion Sites gives you free, and the one case where it stops being the right answer, settles that in a page.

You wanted to run the stack yourself. Some people asking this have a server and want the right way to use it. That is a legitimate answer, and most published guides on hosting AI-generated sites are written for exactly that reader, which is part of why they feel wrong to everyone else.

Where Birta fits

We are the answer to questions four, six and seven, and we are upfront that we are not the answer to all seven.

The tool that already has your finished files sends them to a live HTTPS address, without a repository or a build step in between. Images and fonts travel with the site. The last ten published versions are kept, so a change that turns out wrong can be rolled back instead of rebuilt, and a later edit goes through the same connection rather than starting a fresh upload. A custom domain points at it when you want your name in the address bar; that one is a paid plan, as it is almost everywhere. Project analytics show you basic traffic without adding anything to the page.

The limits, stated plainly: static sites only, meaning HTML, CSS, images, fonts and browser JavaScript. Video and PDF files are not served, so those still need a public URL somewhere else. A contact form works without you writing a backend, and replies land in the project; taking payments on your own site is not something we provide today. If your project needs a database or server-side code, this is the wrong layer and question one applies.

There is a reason the connection matters more than the storage, and someone in that June thread put it better than we would have, not as a request for hosting but as a description of the missing piece:

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 be able to publish it, using one open standard rather than a separate integration per tool, instead of reading you server commands. How that agent goes from a pasted line to a live page, and where it stops to ask you, is worth reading before you connect anything.

Frequently asked questions