Where to host a website you built with Claude

Building a site with Claude takes an evening now. Our guide on how to publish a website made with Claude covers the mechanics of getting it online: export, upload, connect the domain. This article is about what comes next, the part the tutorials skip. A website isn't finished at launch. It gets a contact form, a cookie banner, a second editor, a new price list. Each of those lands on whoever hosts it.

You're early, by the way. In our study of companies founded in Germany in 2026, 36% of the new websites were built as code without any CMS or website builder, and only 2.5% carried a clear fingerprint of an AI site builder (up to 15% looked like AI-written code). Among established small businesses it is rarer still: of 2,538 websites in 16 cities in Germany, Austria and Switzerland, 0.4% were made with an AI site builder and at most 3.1% look AI-written. Details are in New companies 2026: what their websites run on and our study of AI-built small-business websites.

Key takeaways

• Claude's Publish button is not hosting. The page stays on Claude's domain, with no custom domain and no form back end.
• Two of the four big free hosts exclude business use on their free plans: GitHub Pages and Vercel Hobby. Cloudflare Pages and Netlify Free don't.
• The real work starts after launch. Among the sites we copied in 2026, about one in five had forms, one in five a cookie consent tool and almost a quarter Google Tag Manager. Each needs someone to own it.
• Add-ons cost speed. In our PageSpeed data, sites with a tag manager or tracking pixel had a median load time for the main content of 11.0 seconds, against 6.4 seconds without.
• Self-hosting is cheapest in money and most expensive in attention. Managed costs more and takes the attention off you.

Can Claude publish a website by itself?

Partly. On claude.ai you can publish an artifact, which gives it a public link anyone can open. That link lives on Claude's domain. You can't put your own domain on it, add a page title or Search Console verification, or receive form messages, because the page around your content isn't yours. Use it to show someone a draft. For a business, take the files out and host them, which every route below does.

The free hosts, compared (November 2026)

What Claude builds is a static website: plain HTML, CSS and images. Any static host can serve it, and the big ones have free plans. They differ in one way that matters more than speed: whether you may run a business site on the free plan at all.

Sources: the official pages of each host, read in November 2026: Cloudflare Pages limits, Netlify's pricing page and forms billing docs, GitHub Pages limits and Vercel's pricing FAQ. Hosts change these terms often, so check before you commit.

For a small business, that leaves Cloudflare Pages or Netlify for a free start. Our GitHub Pages guide is still useful for a portfolio or a club, where the commercial rule doesn't bite.

What you take on after launch

The host serves files. Everything a business site does beyond showing pages is extra, and with self-hosting it's yours. To see what that means in practice, we looked at what the small-business sites we copied in 2026 actually used.

ShiftPress data, 2026: features our copier detected on the small-business sites we copied, most of them WordPress. Share of sites. What a static website can and can't do goes through shops, bookings and logins in detail.

1. Forms, and where the mail goes

A static page has no server, so a form needs somewhere to send its data: Netlify's built-in forms, a form service, or a small function you write. Then come the questions nobody asks at launch. Who reads the messages when the person who set it up is on holiday? What happens to spam? Does the mail land in a shared inbox or one person's private account? Send a test message every few months, because a silently broken form looks exactly like a quiet month.

2. A second person who wants to change something

Self-hosted, the site is a folder of files and a deploy step. That works for one technical person. The day a colleague needs to change the opening hours, they need access to the repository or the host, and they need to know how a change goes live. In practice, they send you a message, and you become the bottleneck. Our guide on how to edit a static HTML website compares the ways around that.

3. Changes without the terminal

With Claude Code, a change is a session: open the project, describe the change, check it, push it. Quick for you, impossible for anyone who doesn't use a terminal. It also means every change depends on your laptop and your Claude subscription.

4. Speed, which slowly leaks away

A fresh Claude site is fast. A year later it carries a tag manager, a cookie banner, a chat widget and a slider. Our PageSpeed data shows where that ends. We tested more than 130 small-business websites with Google PageSpeed (mobile) in 2026, before rebuilding them. The median site took 7.1 seconds to show its main content, where Google calls 2.5 seconds good, and 90% were slower than that.

ShiftPress data, 2026: Google PageSpeed Insights, mobile lab test, one measurement per site. These sites were slower, which doesn't prove the add-on alone made them slow. The lesson for a self-hosted site still holds: every script you add is yours to justify.

5. Search and AI search

Page titles, meta descriptions, a sitemap that stays current, redirects when a page moves, structured data. None of it is hard, and all of it is easy to forget when the site changes by hand. Our guide to static website SEO lists what to keep up with.

6. Security

Here self-hosting a static site is genuinely strong. There's no PHP, no plugins and no login page to attack, which removes the main ways small WordPress sites get broken into (see WordPress security flaws). What's left is your accounts: the host, the domain registrar, the Git repository. Turn on two-factor login for all three.

What it costs over a year

The domain costs the same in every row, so it's left out. The row that's hardest to price is your own time. If you'd enjoy running it, self-hosting is the cheapest website there is. If every small change means opening a terminal on a Sunday, it isn't cheap at all.

What a managed setup takes off your plate

This is the model ShiftPress runs, and the comparison in ShiftPress vs self-hosting goes feature by feature. In short, for a site you built with Claude:

• Upload instead of deploy. The Claude Design ZIP, or a ZIP of plain .html pages (up to 30 per file), becomes real pages you can edit.
• Forms that arrive. Submissions land in a leads inbox, are forwarded by email, and spam is flagged and not forwarded.
• A team, not a folder. Owners and editors with their own logins: 2 people on Basic, 5 on Premium, 10 on Growth.
• Changes by chat. You describe the change, see it in a preview, and approve it before it goes live. A version history lets you step back.
• Search basics kept current. The sitemap and robots.txt are rebuilt when you publish, and Premium writes and publishes two articles a month.

Your own domain comes with a paid plan. The code stays yours, and you can download it and host it anywhere, including on the free hosts above. Already have a design, or just a few sentences about your business? That's enough to start a new site on ShiftPress.

Which one fits you

• Host it yourself if you're the only person who changes the site, you're comfortable with Git, and the site has at most a contact form. Start on Cloudflare Pages or Netlify.
• Go managed if someone else needs to make changes, leads have to arrive without you checking a form service, or you'd rather spend Sundays on the business. That's what our done-for-you plans are for.
• Either way, keep the files in a Git repository. That's what keeps you free to switch later.

Frequently asked questions

The bottom line

Hosting a Claude-built site is free and takes an afternoon. Running it takes a year of small jobs: forms, consent, edits, search. Choose the setup by who does those jobs, not by who serves the files fastest.