The explanation layer

How an AI-hosted website works, from prompt to live site

You told an AI what you wanted, and now there is a website on your screen. The question nobody answers clearly is what happens next: how does that thing in a chat window become a live site with a real address that other people can visit? This page walks the whole path, in plain English, without assuming you know any hosting jargon.

What "AI-hosted website" means

An AI-hosted website is a website built by an AI and put into production on real hosting infrastructure. Both halves matter. The AI does the building, which used to be the expensive part. The hosting does the running: an always-on server, a real domain, HTTPS, versions you can restore, and a way to update the site later. A preview link inside an AI tool gives you the first half only. An AI-hosted website gives you both.

Why there is a gap between "the AI made it" and "it is online"

When an AI builds you a website, what it really produces is a set of files. Those files exist inside a chat, an editor, or a temporary preview. None of those places is the internet. For the site to be genuinely online, the files need to live on a computer that never switches off, answer to a name people can type, and be served over a secure connection.

Traditionally, crossing that gap meant learning about servers, DNS records, certificates and file transfers. That knowledge barrier made sense when building the site was the hard part. Now that an AI builds the site in an afternoon, the barrier is upside down: the last five percent of the job blocks the other ninety-five. AI hosting exists to remove exactly that last step, by letting the same AI that built the site also publish it.

The lifecycle, step by step

  1. 1

    Describe the site to any AI

    ChatGPT, Claude, Lovable, Bolt, Cursor, or whichever assistant you already use. You explain what the site should say and look like; the AI writes the pages.

  2. 2

    The AI produces a working build

    Under the hood that is a folder of HTML, CSS and JavaScript, or the output of a framework build. You do not need to open it, but it is yours: ordinary web files, not a proprietary format.

  3. 3

    Hand the AI a place to publish

    This is the step most people get stuck on. AI-Hosted gives the AI a deployment target: a single instruction file it reads, or an MCP connection it calls directly. The AI sends the site itself, or, when its sandbox cannot reach the internet, hands you a deploy page to open in your browser. Uploading the folder yourself works too.

  4. 4

    The site goes live on a real address

    Within moments the site is served from always-on infrastructure with HTTPS, first on a subdomain, then on your own domain once you connect one. Anyone on the internet can open it, whether or not your laptop is on.

  5. 5

    Keep it running properly

    A live site is not a finished job. Your own domain, contact forms that reach your inbox, visitor analytics, versions you can restore in one click, and on the Studio plan a staging copy for checking changes first: that is the layer that separates a real website from a demo link.

The handoff: how an AI publishes a site

Step three deserves a closer look, because it is the part that makes the category work. There are two ways to let an AI publish to AI-Hosted, and both are tool-agnostic: they work with whichever assistant you build in. And if you would rather do it yourself, uploading the folder, a ZIP or a single HTML file in the dashboard always works.

The instruction file

A single file you paste into any chat; in the dashboard it is called the Magic File. It teaches the AI how to send the finished site to your account. You say "publish this", and the AI either sends the files itself and reports back with the live address, or, when its sandbox has no network, gives you a deploy page to open in your browser. No installation, and it works in a plain browser chat.

The MCP connection

For assistants that support connected tools (Claude, Cursor, VS Code and others, and ChatGPT on plans where a custom MCP server may write), AI-Hosted plugs in as a capability the AI can call directly. The assistant can then create sites, deploy updates, check analytics, manage domains and run containers as part of the conversation.

Let your AI deploy it

The MCP connection is the shortest path when your assistant supports it. You add one server address to your AI once and sign in, and from then on "publish this", "change the opening hours" or "connect my domain" are things the AI does for you, with 40+ tools for deploys, edits, domains, forms and containers. AI-Hosted runs on VibeDeploy, and the VibeDeploy MCP setup page lists the exact steps for Claude, ChatGPT, Cursor, VS Code and other clients.

After the launch: what "running it properly" involves

Going live is a moment; staying live is a practice. These are the pieces a real website needs after day one, and they are part of the hosting rather than bolted on:

What an AI-hosted website is not

It is not a website builder: there is no drag-and-drop editor you are locked into, and the files stay ordinary web files any AI or developer can work on later. It is not a preview link: preview links can expire, sit on somebody else's subdomain, and follow the rules and plans of the tool that made them. And it is not old-school hosting: there is no control panel maze or file-transfer client, because the AI or a simple upload does the technical handling for you. If you are weighing these options against each other, the comparison framework goes through them honestly, criterion by criterion, and compares the publish buttons of ChatGPT, Claude, Gemini, Lovable and Bolt with hosting.

Read the next layer

This page covers the full path. The AI-Hosted blog goes deeper on each decision and production detail:

See the lifecycle with your own site

The trial runs 14 days with one site and your own domain, and needs no card. Build with the AI you already use, publish, and put it on a real domain. Plans start at EUR 4 a month (prices include VAT where it applies), and the about page explains exactly who runs the platform.

Start Free Trial

Powered by VibeDeploy. Infrastructure in Belgium, operated by Tnet Comm.V.