Type “AI website builder” into Google and most of what comes back lives in the same place: inside a dashboard, behind a signup form, generating a site from a text box before you have installed anything. That is one entire category of “AI builds my WordPress page.” There is a second category that barely shows up in the same search results, because it does not live in a dashboard at all. It lives in a terminal, or an editor sidebar. A developer who already has an AI coding assistant open points it at a theme’s own documentation and asks for a page. Astra, through its companion plugin Starter Templates and the AI engine it embeds (ZipWP, also a Brainstorm Force product), is a clean example of the first category. Brndle, the free WordPress block theme this blog runs on, is a clean example of the second. It happens through its own /brndle-pages Claude Code skill.

We have covered Brndle’s half of this comparison in detail already, in How Brndle Generates Landing Pages with Claude Code: An Architecture Walkthrough, which read the theme’s public repository rather than take the feature on faith. This post reuses those confirmed facts and puts them next to what we could independently confirm about Astra’s AI site-building path, researched directly against the Starter Templates plugin listing, the ZipWP product itself, and Brainstorm Force’s own product page. We are the company behind Brndle, so we are not a neutral third party here, and we are going to be explicit, the same way the sibling post was, about which claims are sourced and quoted versus where we are drawing a reasonable inference. Astra is a genuinely well-built, enormously popular theme; the point of this post is not to declare a winner, it is to describe two structurally different answers to the same question honestly enough that you can tell which one fits the job in front of you.

In this guide

The two different places “AI page building” can live
How Astra’s AI site builder actually works, confirmed against the plugin listing and ZipWP
How Brndle’s Claude Code integration actually works, recapped from the architecture post
Accessibility, guardrails, technical requirement, extensibility: a side-by-side table
A worked scenario for each: who would actually reach for which one
The bottom line
Questions people ask

Two different places “AI page building” can live

Before comparing features, it is worth naming the structural difference, because it explains almost everything else in this post. One approach puts the AI inside the content management system itself, reachable from a setup wizard or a plugin screen the moment WordPress is installed. The person using it never leaves wp-admin, never opens a terminal, and in most cases never needs to know what an API key is. The other approach puts the AI outside the CMS, in a general-purpose coding tool that happens to be pointed at a WordPress theme’s codebase. The person using it is, by definition, already running that tool for other work, and the “page builder” is really a documented interface the coding assistant reads and follows, not a button in wp-admin.

Neither placement is automatically better. A tool bundled into wp-admin reaches far more people, because it has no prerequisite beyond installing WordPress and a free plugin. A tool that lives in an external coding assistant reaches fewer people, because Claude Code (or any comparable coding agent) is not something every site owner has installed, but it inherits whatever structure the codebase hands it. Those two placements are what actually separate Astra’s AI feature from Brndle’s, more than any claim about which AI model is smarter.

How Astra’s AI site builder actually works

Astra itself, the theme, does not ship an AI feature in its own codebase as far as we could confirm. The AI capability associated with Astra lives in Starter Templates, the free companion plugin (listed on WordPress.org under the slug astra-sites) that Astra’s own documentation points to for building out a new site, and it is powered by a sister product from the same company, Brainstorm Force, called ZipWP. We confirmed the relationship directly: Brainstorm Force’s own site lists Astra, Starter Templates, Spectra, and ZipWP together under a “Web Creation” product group, describing the stack as “Start with Astra, launch fast using Starter Templates or ZipWP, design with Spectra.” So the honest framing is not “Astra has an AI builder.” It is “the plugin Astra’s own team tells you to install to build a site embeds an AI builder made by the same company.”

Here is what the Starter Templates plugin listing says the AI feature does, quoted directly: it describes an AI website builder where you “describe your business and the AI selects a design, generates professional copy, and curates visuals to match your brand, producing a complete website in under two minutes.” The documented flow, step by step, per that listing, is:

Enter your website name and the type of site you’re building
Describe your business in plain language
Add contact details and social media links
Choose from AI-suggested images, or let it pick for you
Select a website structure (which pages to include)
Pick the site features you want
The AI assembles a complete website, in under two minutes by the plugin’s own claim
Customize the result afterward in the normal WordPress editor

One detail in the plugin listing matters more than it first looks like it should: “To access AI-generated templates and websites, you’ll need a ZipWP account. Signing up is quick, easy, and 100% free.” That is the plugin’s own wording, not ours. It means the feature is reachable entirely inside wp-admin, no terminal, no code editor, but it is not reachable with zero external accounts either, you are handing a business description and contact details to a connected service (ZipWP) to generate the result. That is a meaningfully different privacy and dependency profile than a feature that runs entirely against your own install, and it is worth knowing before you start the wizard, not after.

ZipWP also exists as its own standalone product at zipwp.com, independent of installing the Starter Templates plugin at all. There, the pitch is similar but the mechanics are more generous: describe a business in plain English, and the service generates a complete, live WordPress site, hosting and a free domain included, in what the product calls under 90 seconds, auto-matching from a stated library of 900-plus templates and writing AI content to fill it. The free tier on zipwp.com’s own pricing is limited to three AI site generations. Unlimited generation sits behind a $29/month Starter plan or a $399 one-time Lifetime plan, per the pricing page we fetched directly. Whether a given Astra user hits the plugin-embedded flow or the standalone zipwp.com flow, the underlying mechanism is the same, and so is the underlying business model: a free taste, with paid unlimited use.

What this architecture is actually doing, mechanically, is template selection plus generated fill content, not freeform code generation. The AI is not writing arbitrary HTML or CSS for your specific brief; it is matching your description to the closest template among hundreds already built by Astra/Brainstorm Force’s design team, then writing copy and choosing images to populate that template’s existing slots. That is a meaningfully different kind of “AI building a page” than an agent writing original markup, and it is also different from Brndle’s block-and-token approach below, closer in spirit to “pick the best-fit pre-built design” than to either extreme.

How Brndle’s Claude Code integration actually works

We covered this in full in the architecture walkthrough linked above, so this is a recap with the same confirmed-vs-inferred labeling that post used, not a re-investigation. Brndle’s public GitHub repository carries a CLAUDE.md file and a .claude/skills/brndle-pages.md skill file, invoked inside Claude Code from the theme directory with the slash command /brndle-pages. The repository’s own documentation states the skill generates “complete landing pages from a text description” using the theme’s native blocks rather than hand-written markup. A second file, docs/AI-USAGE-GUIDE.md, is a real reference document: a block-by-block attribute schema for all 18 registered blocks, a decision tree mapping content needs to block choices, a worked JSON example for a full landing page, a REST curl example, and a pre-publish checklist.

Structurally, the agent is not writing HTML or CSS. It is choosing block types from a closed catalog of 18, split into 14 built for marketing sections like brndle/hero, brndle/pricing, and brndle/faq, and 4 built for long-form editorial content. Then it fills each one’s attributes object, in the shape the usage guide documents. Every block renders through one shared PHP callback in BlockServiceProvider, which resolves a Blade view by naming convention and hands it the parsed attributes. The agent is filling named slots in a template someone already designed. It cannot, through that interface, invent a new layout or introduce a color the view was not built to render.

Appearance is controlled separately, through a REST endpoint at brndle/v1/settings that accepts one of 12 named color schemes and one of 8 named font pairs, both validated server-side, not free text. Two filter hooks, brndle/color_presets and brndle/font_pairs, let a developer extend either closed set, but that is a PHP-level change made by a developer, not something the agent widens on its own by passing an arbitrary value. We made this same point in general terms in A Design System an AI Agent Can Follow: this is a design system where the enforcement moved from a rules file an agent has to read and obey into the registration and rendering code itself, a closed system rather than a policed one. And exactly as the architecture post was careful to note, this is a documented interface contract, not a captured transcript of an actual Claude Code session. We confirmed the skill file, the usage guide, and the registration/render code against the public repository. We did not audit every individual Blade view line by line, and we are not claiming to have watched a live run.

Accessibility, guardrails, technical requirement, extensibility

Dimension	Astra’s AI site builder (Starter Templates + ZipWP)	Brndle’s Claude Code integration (`/brndle-pages`)
Where it lives	Inside wp-admin, via a plugin setup wizard (or standalone at zipwp.com)	Inside Claude Code, an external AI coding tool, pointed at the theme’s own repository
Accessibility to a non-technical user	High. No code, no terminal; a free plugin install plus a free ZipWP account signup is the whole prerequisite	Low on its own. Requires Claude Code already installed and a working familiarity with it; not reachable from wp-admin at all
Output guardrails	Soft. Output is matched from a stated library of 900-plus pre-built templates, which keeps results generally professional, but the match is a best-fit selection, not an enforced closed vocabulary; there is no documented hard stop against an off-template visual result	Structural. Output is restricted to 18 registered blocks and 12 named color schemes / 8 named font pairs, enforced by the same PHP render callback and REST validation that renders every other page on the install, so there is no code path for the agent to emit an off-brand value even if it tried
Technical requirement	None beyond basic WordPress admin use; a business description, contact details, and a ZipWP account	Claude Code installed and configured, and someone comfortable reading a skill/usage-guide file and running a slash command against a codebase
Extensibility for a developer	Limited and indirect: the generated site is normal WordPress/Spectra content afterward, editable in any page builder, but the AI step itself is not something a developer scripts or extends; it is a closed wizard flow	Direct: two documented filter hooks (`brndle/color_presets`, `brndle/font_pairs`) extend the closed token sets in PHP, and the whole mechanism (block markup, REST settings, WP-CLI page creation) is scriptable by any tool, not only Claude Code, per the sibling post’s own FAQ on that point
Dependency on an external account/service	Yes, confirmed: the plugin listing states a free ZipWP account is required to access AI-generated templates	No external account beyond Claude Code itself and whatever AI provider it is already configured against; the block and settings surfaces are standard WordPress REST/WP-CLI, not a third-party service call

Read the guardrails row twice if you only read one. “Soft” versus “structural” is not a value judgement about which experience feels nicer, it is a claim about what kind of mistake is physically possible. In Astra’s flow, nothing in the documented mechanism stops a generated page from landing visually generic or slightly off from the business it describes; the AI is doing its best match against a large but finite template library, and the plugin description does not claim a closed, validated vocabulary the way Brndle’s REST schema does. In Brndle’s flow, the agent cannot drift the accent color one shade darker than intended, because “one shade darker” is not a value the settings endpoint accepts, full stop. That does not make Brndle’s output better-looking by default; a closed catalog of 18 blocks is also a smaller canvas than 900-plus templates. It makes the kind of failure each system is capable of different in kind, not just in degree.

Scenario one: a non-technical business owner who needs a site this week

Picture someone opening a two-person landscaping business. They have a logo, a handful of job photos on their phone, and no interest in learning what a block or a render callback is. For this person, Astra’s path through Starter Templates is the right tool, not a compromise. They install the free plugin, answer the wizard’s questions about the business, pick from the AI-suggested images, and have something live in the two minutes the plugin’s own description claims, that they can then open in the normal block editor or Spectra and nudge. The ZipWP account requirement is a minor friction, a free signup, not a blocker, and the 900-plus template library behind it means the result is very unlikely to look broken even if it is not bespoke. Nothing about Brndle’s Claude Code integration is reachable to this person at all; it requires a tool they have never heard of and would have no reason to install for one landscaping site.

Scenario two: a developer shipping repeatable, on-brand landing pages

Picture a different person: a developer already running Claude Code for most of their actual engineering work, who has been handed a brief to ship five campaign landing pages for the same product this month, each with different copy and a different pricing offer, but all needing to land on exactly the same brand (one of Brndle’s 12 color schemes, one font pair, chosen once). For them, writing each page by hand in the block editor is slower than it needs to be, and asking a general chatbot for raw HTML risks exactly the generic-gradient, invented-spacing failure mode the architecture post opened with. Running /brndle-pages against the brief for each page lets the agent choose from Brndle’s native block catalog and fill attributes, with the shared render callback guaranteeing every page stays inside the same 12-color, 8-font system without the developer re-explaining brand rules in every prompt. This is also the person for whom the two filter hooks matter: if the brief later calls for a 13th brand color, extending brndle/color_presets in PHP is a few lines, not a redesign. Astra’s AI builder is not built for this job at all, it is a one-shot “generate a new site” flow, not a repeatable “generate another on-brand page in an existing site” flow, and nothing in its documented mechanism is meant to be scripted the way Brndle’s REST/WP-CLI surface is.

The bottom line

These are not two competitors racing toward the same finish line. They are solving different problems for different people, and the honest comparison says so plainly instead of forcing a winner. Astra’s AI site builder, through Starter Templates and ZipWP, solves “I need a professional-looking WordPress site today and I do not write code,” by matching a description against a large template library and filling it with generated copy and curated images, reachable by anyone who can fill out a wizard, at the cost of a free third-party account and a softer guarantee about staying on-brand. Brndle’s Claude Code integration solves a narrower, different problem: “I already use an AI coding assistant, and I want every page it generates for this theme to be structurally incapable of drifting off my design system,” at the cost of requiring that coding assistant in the first place and offering a smaller catalog of starting pieces than a 900-template library.

If you are choosing a theme or a plugin based on “which one has AI,” the more useful question is where you want that AI to sit. If the honest answer is “inside wp-admin, for someone who will never open a terminal,” Astra’s path is the better-fitting tool, and we would say that even though we did not build it. If the honest answer is “inside the coding tool I already run every day, generating pages that cannot visually drift from a design system I control,” that is the problem Brndle’s /brndle-pages skill was actually built to solve, and the closed block-and-token architecture is what makes that guarantee structural rather than a sentence in a rules file hoping to be followed.

Questions people ask

Is Astra’s AI feature built into the Astra theme itself?

Not as far as we could confirm. The AI capability is in the companion Starter Templates plugin (astra-sites), which Astra’s own team recommends for building a new site, and the generation engine behind it is ZipWP, a separate product from the same company, Brainstorm Force. Installing the Astra theme alone does not give you the AI builder; installing Starter Templates and signing up for a free ZipWP account does.

Do I have to pay to use Astra’s AI site builder?

The plugin listing describes the AI builder as requiring a free ZipWP account, not a paid one, to access AI-generated templates. The standalone zipwp.com product, separately, caps its free tier at three AI site generations per its own pricing page, with unlimited generation behind a $29/month or $399 one-time plan. Which limits apply depends on whether you go through the Starter Templates plugin flow or the standalone zipwp.com flow; we found the plugin listing itself does not state a generation cap the way the standalone pricing page does.

Does Brndle’s Claude Code feature require a paid Claude subscription?

It requires Claude Code, Anthropic’s coding tool, which runs against whatever Anthropic plan or API access you already have configured; Brndle’s skill file and usage guide are free and open in the theme’s public repository, there is no separate fee from Brndle for the skill itself. What it costs you is whatever your existing Claude Code usage already costs, not an additional theme-specific charge.

Can a non-developer use Brndle’s AI page-building feature?

Not directly, and that is a real limitation worth stating plainly rather than talking around. The /brndle-pages skill is invoked inside Claude Code, a developer tool, against the theme’s codebase. There is no wp-admin button. A non-technical site owner using Brndle would either build pages by hand in the block editor using the same 18 blocks, or have a developer run the Claude Code skill on their behalf.

Can a developer use Astra’s AI builder as part of a scripted workflow?

Nothing in the Starter Templates plugin listing we reviewed describes a scriptable or API-driven path into the AI generation step; the documented flow is a setup wizard, step by step, inside wp-admin. Once the AI generates the site, the resulting content is normal WordPress/Spectra markup that a developer can edit or script against like any other site, but the generation step itself appears to be a one-time, UI-driven flow rather than something built for repeat, automated use the way Brndle’s REST and WP-CLI surfaces are documented to be.

Which approach produces a more “on-brand” result?

That depends on what “on-brand” means for the job. For a brand-new site with no existing brand system, Astra’s large template library, matched to a business description, is likely to produce something that looks professional and fits the stated industry reasonably well, because the match is drawn from hundreds of pre-designed options. For an existing brand that has already chosen a specific color scheme and font pair and needs every new page to stay inside those exact choices without drift, Brndle’s closed 12-color, 8-font token system, enforced by the renderer rather than by instruction, is the stronger structural guarantee, because there is no code path for the agent to pick a value outside that set.

Does either tool write the page’s copy, or just the layout?

Astra’s AI builder, per the plugin listing, generates “professional copy” as part of the same flow that picks a design and curates images, so copy generation is part of the documented feature. Brndle’s /brndle-pages skill, per its usage guide, is given a text description as a brief and fills block attributes including headline and body text from that brief; the architecture post was explicit that nothing in the block schema checks whether the resulting copy is factually accurate, a fabrication risk that applies to both systems’ generated text and that neither architecture removes on its own.

If I start with Astra’s AI builder, am I locked into Astra forever?

The content the AI generates becomes standard WordPress post content once the site is live, so it is portable in the same sense any WordPress content is. If the generated page relies on Astra- or Spectra-specific blocks or styling, as Brndle’s architecture post notes about its own theme-registered blocks, switching themes later means those specific elements will not render the same way without the original theme or a compatible block library, which is the normal tradeoff of theme-level custom blocks generally, not something unique to Astra.

Could a future version of either theme close the gap?

Plausibly, and we want to flag this as our own forward-looking speculation rather than a confirmed roadmap item for either product. There is nothing architecturally stopping Brainstorm Force from exposing Starter Templates’ AI flow through a documented API a developer could script, the way Brndle exposes its settings through REST, and there is nothing stopping a future Brndle skill update from widening its catalog closer to a template-library model. As of what we could confirm researching this post, though, the two sit where this comparison describes them: one bundled into wp-admin behind a free account, one living inside an external coding assistant behind a closed block-and-token schema.

Which one should I actually pick?

Pick based on where you are standing, not on which name sounds more advanced. If you are opening WordPress for the first time this week with a business to describe and no interest in a coding tool, Astra’s AI builder through Starter Templates is built for exactly that moment. If you are a developer already living inside Claude Code who needs a theme that will not let an agent wander off-brand while generating pages, that is the problem Brndle’s /brndle-pages skill and its closed 18-block, 12-color, 8-font system were built to solve. Both are honest tools for honest, different jobs; the mistake is assuming “AI page builder” means the same thing every time you read the phrase.

Astra’s AI Site Builder vs Brndle’s Claude Code Integration: Two AI Page-Building Approaches