Free Website Builders Meet AI-Generated Code: What the Free Tier Costs You at Deploy Time

There's a genre of pricing page that looks like generosity and behaves like a trap.

Free tier, free hosting, "no credit card required" — all true. But the comparisons you find online rank these plans by feature counts: how many pages, how much storage, whether there's a form. That framing assumes you built the site by hand inside the builder. It falls apart when you didn't — when the site was written by Claude or ChatGPT in a chat window, and the free tier's job is suddenly to accept code that was born outside its walls.

That's the audit worth doing: not what the free tier includes, but what it does to your AI-generated code the moment you try to deploy. We've covered the general case in Easy Hosting Solutions, Ranked by What "Easy" Means When Your Site Came Out of ChatGPT; this post is specifically about the free tiers, where the tradeoffs hide.

The three ways a free tier can reject your AI-built site

Almost every failure falls into one of three buckets. When you're evaluating a builder's free plan for a site you built with AI, check these in order — they're the difference between deploying in ten minutes and discovering you need a paid plan, a rebuild, or both.

1. The export lock

Some builders host your site but don't let you take it with you — or only let you export on paid plans, or export something lossy (a template skeleton without your content, or a format that doesn't run anywhere else).

This matters enormously for AI-built sites, because the export question is inverted. If you built by hand, losing the code means re-doing work. If Claude wrote the code, the code is already yours — it's sitting in your chat history. The question isn't whether you can export from the builder; it's whether the builder can import what you have.

And most can't. A builder whose input is a drag-and-drop canvas has no natural place to put a folder of HTML, CSS, and JavaScript that an LLM handed you. Some offer a "paste your code" escape hatch; more often, the practical answer is copying your AI-generated code into their code-block components section by section, which is tedious enough that you'll be tempted to let the builder regenerate the design — at which point you're no longer building with AI, you're using the builder's templates with extra steps.

2. The subdomain rule

Most free tiers will publish your site, but only at an address on their domain — something like yoursite.buildername.com — with the custom domain reserved for paid plans. The free version of the site is also usually stamped with the builder's branding: an ad banner, a "made with" badge, or both.

For a weekend project, a subdomain is fine. For anything a real customer will see, it usually isn't — and this is where "free" quietly becomes the most expensive option on the table. You launch on the free tier, you send traffic to it, it gets indexed, it's on your business cards. Then you discover the custom domain requires an upgrade, and the migration isn't just a settings toggle: depending on the builder, moving off-platform later can mean leaving your design behind entirely.

3. The deploy-time feature wall

The sneakiest one. The free tier publishes the site fine — until it doesn't, because the thing your AI-generated code actually does lives behind a paid feature. Custom form handling, custom scripts in the head tag, API integrations, e-commerce, removing the badge: these are the features that an LLM-generated landing page tends to lean on, and they cluster suspiciously at the paid boundary.

The pattern to watch: everything visual is free, everything functional costs money. Since a landing page's entire job is functional — capture the lead, route the submission — the free tier often gets you a beautiful page that can't do the one thing it exists for. If your form needs somewhere to send submissions on a static host, we mapped the options in Your AI Landing Page Gets Traffic — But Where Do the Leads Go?.

The four questions to ask any free tier

Skip the feature grid. Ask these instead, in this order:

1. Can it accept my code? Can you paste or import a folder of files an LLM wrote, or must the site be born inside the builder?
2. What's the publish URL? Custom domain or subdomain — and if it's a subdomain on free, what does the upgrade actually cost per year?
3. What leaves with me? If I outgrow this in six months, does my content, design, and code come with me, or am I starting over?
4. What's paywalled that my site needs? Not "what's paywalled" in general — specifically, forms, scripts, integrations, and badge removal. That's where AI-built sites get caught.

If a builder fails question 1, the other three barely matter — you're not deploying your site, you're rebuilding it. If it fails question 3, you're not getting free hosting, you're renting it with your design as collateral.

Where the free-tier logic actually works in your favor

None of this means free tiers are bad. It means the order of operations matters when you're building websites with AI.

The genuinely free path for an AI-generated site isn't a website builder at all — it's a static host with a free plan that takes your files as-is. Claude writes the code, you hand the files to a host, and the host's job is dumb in the best way: serve the pages, don't reinterpret them. There's no export question because there's nothing locked in, and a custom domain usually costs only the price of the domain itself. We walked through what a host needs to support this in AI Domain Hosting Is a Feature Set, Not a Host: The 5 Requirements Your AI-Built Site Actually Needs, and the end-to-end path from chat window to live domain in ChatGPT Built Your Site. Now Who Hosts It? The Path From Code to Live Domain.

Where builders do make sense on a free tier: when you want to prototype inside their canvas before committing, or when you're fine staying on a subdomain indefinitely and the site needs nothing beyond static pages. If you're pre-launch and just need a coming-soon page up today, the waitlist-page path in "Launching Page" Means Something Different: Build a Waitlist Page With Claude and Put It Live Today is faster than any builder signup flow.

The real price of "free"

Here's the framing to carry into any free-tier comparison: free is only free if the exit is free.

A free tier on a builder that locks your design in isn't free hosting — it's deferred cost. The bill arrives later, as either a subscription, a migration you didn't budget for, or a rebuild you do by hand because the builder's format doesn't travel. Meanwhile, a free static-host plan that takes your AI-generated files as-is costs nothing today and nothing at exit, because there's nothing to exit from. Your code was portable the moment Claude wrote it; the only question is whether you hand it to a platform that respects that.

So before you sign up for the free plan with the nice demo video, run the four questions above. Two minutes of checking beats an afternoon of discovering that "no credit card required" had fine print about where your domain, your code, and your design were allowed to go.