AI site builders: bolt, Lovable, v0, Framer AI, Wix AI, and questions for any of them

An AI site builder is a service that assembles a site from a description in words: as code, from ready-made blocks, or as a whole application with a database.

Describe a site, get a site

Since 2023 and 2024 there has been a new way to make a site: open a page, write in words “a landing page for a solo practitioner, three services, a request form, a calm tone”, and a minute later see a working site. Such tools are called AI builders. Inside them is a large language model: it writes code or assembles a page from blocks, and you are left to look and ask for changes.

First, an honest caveat: this field changes faster than any other in the textbook. Everything named below is true as of October 2026 and is taken from the products’ own pages, where they say anything about it. In half a year the names, prices and abilities will be different. So more important than the names are the questions you’ll learn to ask and the habit of checking what you’re given.

Three kinds, and a fourth that is old

Builders differ by what you get at the end. That is the main difference, and the rest is secondary.

Code on request. You write, and the tool creates the project’s files. An example is bolt.new, which describes itself as an AI builder for websites, apps and prototypes, made by StackBlitz and offering hosting with custom domains. You get a set of files you can take and publish anywhere, if you can read and check them. The freedom is big, and so is the responsibility.

An interface from a description. v0 from Vercel calls itself an AI agent that creates real code and full-stack apps. It works with Next.js, Tailwind and shadcn/ui, deploys to Vercel’s infrastructure in one click, and can open a pull request for review instead. The strength: tidy interfaces. The weakness: it is closely tied to its own platform’s ecosystem.

An application generator. Lovable calls itself a full-stack AI development platform: from a description you get an application with a front end, a back end, a database and user sign-in, and the code can be synced to GitHub, GitLab or Bitbucket. This is the most “grown-up” kind: it makes not a page but a system. And the riskiest: the database and sign-in are usually connected at a third-party service.

Blocks and templates with AI. The big website builders have added AI to their block editors. Wix offers an AI website builder that generates a site from a text description, with an agent called Aria for changes, hosted by Wix; its page also speaks of “vibe coding”, and a free start with limits (connecting a custom domain or taking payments needs a paid plan). Framer calls Framer AI a set of agents built into Framer: from a prompt they create editable pages, sections, copy and visuals, and they can edit existing sites and CMS content, all published on Framer’s hosting. Squarespace and others have similar features.

A note on the Russian market, as one comparison. Tilda, which you met in the lesson on Tilda and 1C-Bitrix, added AI that assembles a page and writes text, and a “vibe block” that makes a custom block on request, all living among Tilda’s ready-made blocks and subject to its global styles. Russian builders such as uCoz and InSales add similar features, and 2026 reviews say their AI mostly helps with draft text, while the site’s source code is often available only on a higher plan.

This is not a ranking, and there is no “best”: for a business card with a form a block builder is often wiser than an application generator, and for a small service with sign-in it is the other way round.

What really comes out

It is better to see an output once than to read ten articles about it. The diagram below takes your brief and builds three pages from it, each by the habits of one kind. The pages are written for the lesson and are not the output of real services. But the numbers in the table under them are counted by the browser from the markup itself: headings, meaningful parts, images with no alt, “buttons” made of div, fields with no label, scripts, third-party servers. You can measure any page you get from a real tool the same way.

<div class="min-h-screen bg-gradient-to-br from-indigo-600 to-purple-700 text-white">
  <div class="container mx-auto px-6 py-24 text-center">
    <h1 class="text-6xl font-bold">My project: innovative solutions</h1>
    <p class="mt-6 text-xl">What the project does</p>
    <div class="mt-10 rounded-full bg-white px-8 py-4 text-indigo-700 shadow-2xl" onclick="start()">Get Started</div>
  </div>
  <div class="grid grid-cols-3 gap-8 px-6 pb-24">
    <div class="rounded-2xl bg-white/10 p-8 shadow-xl"><span>🚀</span><h3>Quality</h3><p>A reliable partner for your business</p></div>
    <div class="rounded-2xl bg-white/10 p-8 shadow-xl"><span>⚡</span><h3>Speed</h3><p>A personal approach to every client</p></div>
    <div class="rounded-2xl bg-white/10 p-8 shadow-xl"><span>💎</span><h3>Innovation</h3><p>Trusted by 10,000+ customers</p></div>
  </div>
  <img src="https://images.example-stock.com/team.jpg">
  <script src="https://cdn.example-cdn.com/tailwind.js"></script>
  <script>function start(){location.href='#contact'}</script>
</div>

See what it teaches. None of the three won on every row. The block page is cleaner but less free. The “code on request” page carries other people’s scripts, “buttons” made of div (which you can’t reach with the Tab key) and a stock call to action: those are the very “tells of a page an AI made” from the lesson on the tells of a template page. The application page is more powerful, and it connects a database that has to be thought about separately.

Seven questions for any builder

A list of names will go out of date, but these questions won’t. Ask them before you build anything important on a tool. You already asked some of them of ordinary builders in the lesson on Tilda and 1C-Bitrix, when you counted a year’s price and planned the way out.

1. What comes out? Code, blocks or an application?
2. Can you take it all: the code, the content, the database, and at no extra charge?
3. Where is visitors’ data kept, in which country, by whom?
4. What happens if I stop paying? Do the site, the domain and the data stay?
5. Whose domain is it? Is it bought in your name, and can it be moved?
6. What does one edit cost? Many tools charge for every call to the model, and the bill grows unpredictably.
7. What are accessibility and speed by default? Measure, as in the diagram above, rather than believe a promise.

What to check separately for your visitors

Some questions depend on where your visitors are.

• Availability and payment. A service may be blocked, slow or unavailable in your visitors’ country, and a payment method may not work. Check before you build a project on it.
• Visitors’ data. If the builder connects a database and sign-in itself (especially the application kind), find out where it physically stands and who runs it. Privacy law follows the people (the GDPR for visitors in the EU, state laws such as California’s CCPA in the US), and a provider that holds the data is a processor you need an agreement with. The lesson on backups, monitoring and where personal data may be kept covers transfers. General information, not legal advice.
• Payment and messaging services. Connect those that work for your visitors, such as the standard payment providers in your country.
• Models. The tool’s own model is not the only choice: you can use a model of your own, as the lesson on your own pipeline shows.

Where it fits, and where it doesn’t

Good fits: a landing page, a business card, a prototype, an internal page, a one-off page for an event. Poor fits: a project with payments and personal data and no person to check the result; a site with a distinctive manner of its own; anything where a mistake costs money or trust. You’ll draw that line in the next lesson.

Practice

Write a record of the first run of an AI builder. First write the first prompt: take every field from the brief (who, for whom, the main action, the sections, what you offer), put the tone in words and add what must not be done. Then say which kind or builder you would choose for your project, and why.

If you are ready to make an account, try a real builder (most have a free trial mode), paste in your prompt and write down three good things and three fixes. If not, examine three pages from the diagram the same way: find what came out well and what you would have to repair. The check reads your record, not the builder: nothing is sent to your browser, and the textbook doesn’t know what you did outside.

What was wrong with 2025

In 2025 such tools were news, and many people accepted the output as it came: a page appeared in a minute, and almost nobody read it. That is why the internet filled up with samey pages with a purple gradient, invented numbers and a key right in the code. Something else turned out too: speed of creation stopped being rare, and what became rare was checking, being specific and taking responsibility for the result. The rest of the part is about that: what vibe coding is, how to write assignments and how to check the output.