Comparison framework

Builders, publish buttons, classic hosting, AI hosting: what actually differs

Once an AI has built your website, there are four realistic ways to get it, or something like it, onto the internet. They are not four flavours of the same thing; they are four different deals, each with a real catch. This page lays out the criteria first and the options second, then compares the publish buttons people actually use, so you can judge any provider with it, including us.

The one-paragraph version

Website builders bundle an editor with hosting and lock the site to that editor. Publish buttons in AI tools put a site online from inside the tool, under the tool's plans and rules, and some now connect your own domain too. Traditional hosting runs anything but hands you the server administration. AI hosting takes the files an AI built, puts them live on a domain you own, and handles the running. The right choice follows from who edits your site and who you want depending on to keep it online.

Five questions that decide it

Ask these of every option on your shortlist. They are vendor-neutral on purpose; any honest provider should have answers.

1.Who edits the site next month?

If the answer is a drag-and-drop editor, you are choosing a builder and marrying its interface. If the answer is an AI, the site needs to exist as ordinary web files an AI can read and rewrite. Builders store your site in their own internal format; AI hosting keeps it as files.

2.Do you own the address?

A site living at yourname.toolbrand.app is a tenant in somebody else's brand. Check whether a custom domain is possible, which plan it needs, and, more importantly, whether you can point that domain somewhere else later without rebuilding.

3.Does it survive the tool?

Publish buttons follow the tool's rules. Replit's Starter plan publishes one app whose link goes down after 30 days, Lovable can unpublish a project in a Free workspace after 12 months without visits or owner logins, and Bolt's Free sites stop serving once they reach the monthly traffic limit. Ask of any option: if I stop paying, or stop logging in, is the site still online?

4.What happens when an update breaks it?

Ask how you go back: can you restore the previous version in one step, for how long, and can you check a change before visitors see it? AI-built sites change often, so the answer matters more than it seems on day one.

5.How much operating do you want to do?

Traditional hosting gives total freedom and hands you the server keys, the update schedule, and the 3am problems that come with them. Be honest about whether you want to run infrastructure or just have a website.

The four options, judged by those questions

grid_view

Website builders (the Wix class)

You assemble pages in a visual editor; hosting comes bundled. It works, and for people who enjoy hand-editing it keeps working. The cost is a closed loop: the site exists only inside the builder, an AI cannot meaningfully edit it, and exporting usually means starting over. If AI is how you build, a builder is the one option that cannot absorb that.

Verdict: Right when a human wants to drag and drop forever. Wrong when an AI does the building.

ios_share

Publish buttons inside AI tools

ChatGPT Sites, Claude artifacts, Gemini Canvas, Lovable and Bolt can all put what they built on a link, and some go much further: ChatGPT Sites, Lovable and Bolt connect custom domains on paid plans, and Lovable and Bolt bring their own databases. What they share is that the site lives inside the tool, under its plans, its sharing model, its storage and its rules.

Verdict: Right when the tool's limits fit the project. Wrong when the site has to outlive the tool.

dns

Traditional hosting (cPanel and FTP)

The classic path: rent server space, upload files, configure the domain, install certificates, keep everything patched. Nothing about it is impossible, and full control is real. But the friction lands exactly on the people AI just liberated from needing a developer: every step assumes vocabulary the AI era stopped teaching.

Verdict: Right for teams who want the server keys. Wrong if the whole point was not becoming an admin.

rocket_launch

AI hosting

The category AI-Hosted sits in: hosting designed to receive work from AIs. Any assistant builds the site; the platform gives that assistant a way to publish, then runs the result like a grown-up website, with your domain, SSL, forms, analytics and versioned deploys you can restore in one click, plus staging on higher plans and containers when the site needs a backend. The editor lock-in of builders and the manual labour of classic hosting both fall away.

Verdict: Right when an AI builds and a real site has to come out the other end.

Publish buttons compared with AI hosting

The publish button in your AI tool is often the first thing you try, and for many projects it is enough. This is what each one offers today, from the vendors' own documentation, next to AI-Hosted. The pattern is simple: a publish button keeps the site inside the tool that made it, while AI hosting keeps the files on a host you chose, whichever tool you use next.

ChatGPT Sites

Where it lives
On OpenAI's hosting, at a Site URL. Plus, Pro and workspace plans; not Free or Go.
Your own domain
Add domain in the Site's settings, where custom domains are available; not in Enterprise workspaces at launch. Sites does not sell domains.
Who can see it
The owner and admins, invited people who sign in, the workspace, or anyone once public publishing is enabled.
Server-side code and data
D1 database and R2 file storage. OpenAI notes that some frameworks, databases and background services may not be supported, and every deploy goes straight to production.

Claude artifacts

Where it lives
Inside Claude, shared by link or by invitation.
Your own domain
None described in Anthropic's article on sharing artifacts.
Who can see it
People signed in to Claude who have the link or an invitation. Legacy artifacts published from a chat, and pages Claude Code shares with a public link, open for anyone with the link.
Server-side code and data
Some artifacts keep personal or shared storage; unpublishing deletes it permanently.

Gemini Canvas

Where it lives
In Gemini, behind a public share link.
Your own domain
None described; Google says shared links only open in gemini.google.com.
Who can see it
Anyone with the public link.
Server-side code and data
Apps can save data across sessions and share it between users, and anyone with the public link can view and edit that data.

Lovable

Where it lives
At an address on lovable.app.
Your own domain
On paid plans; Lovable can also sell you the domain.
Who can see it
Public or Invite only on Free and Pro plans; workspace or custom audiences on Business and Enterprise.
Server-side code and data
A built-in backend, Lovable Cloud, with database, authentication, storage and functions.

Bolt

Where it lives
At a free bolt.host address.
Your own domain
On paid plans; Bolt can also sell you the domain.
Who can see it
Public on every plan; private sites for your team and invited people on paid plans, but not on a custom domain.
Server-side code and data
Bolt databases and server functions.

AI-Hosted (AI hosting)

Where it lives
On a Kubernetes cluster in Belgium, at an ai-hosted.com address, whichever AI made the files.
Your own domain
Every plan, the 14-day trial included: link one you own or buy one in the dashboard.
Who can see it
Public by default; a password, invitations, team sign-in or a network allowlist from the Maker plan.
Server-side code and data
Containers next to the site, deployed by your AI: your own server, Postgres, MySQL, Redis or workers. Container data is not yet included in snapshots.

Go deeper: guides for sites built in ChatGPT, for private sharing and for leaving a builder:

Where AI-Hosted fits, said plainly

AI-Hosted is a home for the fourth option. It is the hosting half of the AI-hosted equation: you bring any AI, we give it a deployment target it can use, and the result is a live site on your domain with the running-it-properly layer included. How that handoff works step by step is covered in how AI-hosted websites work. If your site already lives inside a builder, the guide on how to migrate off an AI website builder shows what each builder lets you take with you and how to move without downtime.

And the honest boundaries. Static sites and single-page apps are served directly. A site can also run containers next to it (your own server, Postgres, MySQL, Redis or workers; up to 6 services with 2 CPU and 2 GiB in total), deployed by your AI through the MCP tool deploy_app and isolated with gVisor. Container data is not yet included in snapshots, the platform runs in one region in Belgium rather than on a global edge network, and there is no drag-and-drop editor: changes go through your AI or your files. Who operates the platform, and what happens to your account, is documented on the about page.

Common follow-up questions

Is AI hosting just a website builder with AI on top?

No, it is closer to the opposite. A website builder bundles an editor with hosting and locks the site to that editor. AI hosting decouples the two: any AI builds the site as ordinary web files, and the hosting serves the files the AI produced. You can switch AI tools tomorrow and keep the same site and host.

My AI tool already has a publish button. Why is that not enough?

Sometimes it is. ChatGPT Sites publishes on Plus, Pro and workspace plans and connects a custom domain where that is available; Lovable and Bolt do the same on their paid plans. The limits show up elsewhere: who can see the site, whether you can check a change before it goes live, where the data is stored, which backend it can run, and whether the site can leave the tool. Check those against your project before you rely on a publish button.

When is a classic website builder the better choice?

When you positively want to edit visually by hand, never want to touch an AI, and are comfortable staying inside one vendor's ecosystem for the life of the site. Builders are mature products with big template libraries. The trade is lock-in: leaving one later usually means rebuilding from scratch.

When is AI hosting the wrong choice?

When you want a drag-and-drop editor, when the site depends on a builder's booking or shop features, or when you need a global edge network: AI-Hosted runs in one region, in Belgium. A full application is no longer out of scope: next to the site, your AI can run containers with your own server, Postgres, MySQL, Redis or workers. Container data is not yet included in snapshots, and container logs are available through your AI rather than in the dashboard for now.

Apply the five questions to us

The trial is the honest way to test the claims on this page: 14 days, one site with your own domain, no card. See what it costs after that; prices include VAT where it applies.

Start Free Trial

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

Sources

Vendor facts on this page come from each vendor's own documentation, checked on 13 October 2026.