Builder.io review
Best for marketer-built landing pages
Builder.io began as the visual CMS that let marketers assemble pages from a developer's real components, and that product still exists and still works. What has changed is everything around it. The platform is now organised around AI agents: the meter is Agent Credits, the plans are per user per month, and the headline capabilities are design-to-code, MCP servers and Design System Intelligence.
For a headless CMS evaluation that matters more than it might sound. You are no longer comparing content platforms on documents, API calls and locales. You are comparing a development tool that happens to include a visual CMS, priced on how much AI work your team does rather than how much content you store.
The visual editing itself remains the strongest argument. Editors drag and drop against your actual React, Vue or Svelte components rather than a parallel set of Builder primitives, so what marketing builds is what engineering shipped. If the requirement is landing pages assembled by non-developers on a real design system, that combination is still rare.
Our scorecard
Our editorial read across six dimensions, scored 1 to 5. This is our own assessment, not an aggregate of user reviews, and it is deliberately kept out of the page's structured data.
- Content modelling3/5
Structured data models exist, but the centre of gravity is visual composition rather than a content model.
- Developer experience4/5
Real component registration across frameworks, built-in MCP servers, and Git integrations on every tier.
- Editor experience5/5
Drag and drop against your own components is still the best version of this in the directory.
- Pricing2/5
Per user AND per credit, with the free allowance stated differently on two of their own pages.
- Governance3/5
Roles arrive on Team, along with commenting and peer review. RBAC and SSO are Enterprise.
- Ecosystem4/5
Broad framework support and strong commerce integrations, plus Mitosis as a genuine open-source contribution.
An editorial read, not an aggregate of user reviews, and deliberately kept out of this page's structured data.
What you can query
Content API
REST, with framework SDKs on top
Published pages and structured content models as JSON, including the component tree a page was composed from
Visual editor SDKs
The core of the product
Register your own React, Vue, Svelte or Angular components so editors compose with real production code rather than Builder primitives
Write API
Server-side
Programmatic creation and update of content entries, used for migrations and automated publishing
Agents and Agent Credits
The primary meter on every plan
AI operations across design-to-code, content generation and codebase work, metered in credits rather than seats or storage
MCP servers
Pro and above
Built-in Model Context Protocol servers on Pro, and custom MCP servers on Team, so agents reach your own systems
Git integrations
Free tier included
GitHub, GitLab and Bitbucket on every tier including free, with enterprise Git and Azure DevOps on Enterprise
Who Builder.io is for
Marketing and growth teams that need to ship landing pages continuously against a real design system, inside organisations that already have engineering. The visual editor working on your own components rather than a parallel component set is the thing that stops these tools producing pages nobody wants to maintain.
It is a poor fit if you want a conventional headless CMS. The pricing is per seat and per AI credit rather than per document or API call, the platform's direction is development tooling, and a team that just wants structured content with an API will find the model confusing and expensive.
Strengths and limits
What it does well
- Visual editing against your own production components across React, Vue, Svelte and Angular, so marketing output uses the real design system.
- Git integration with GitHub, GitLab and Bitbucket on every tier including the free one.
- Built-in MCP servers on Pro and custom MCP servers on Team, which is further than most of this directory on agent integration.
- Content delivery is not metered in Agent Credits, so serving pages does not consume your AI allowance.
- The free tier supports up to five users per space, which makes it a genuine small-team plan rather than a solo one.
- Agent Credit rollovers on Pro, so an unused month is not simply lost.
- Strong commerce integrations, which is why it shows up disproportionately in retail stacks.
- Mitosis, Builder's open-source component compiler, is a real contribution independent of the paid product.
Where it falls short
- The pricing is per user AND per credit, which makes it hard to compare against per-organisation or per-document competitors.
- Builder's own two pricing pages disagree on the free Agent Credit allowance: one says 25 daily and 75 monthly, the other says 60 monthly. Confirm in-app.
- Per-seat prices did not render on either pricing page we could read, so the $24 and $40 figures come from Builder's published comparison content rather than the pricing table.
- Additional Agent Credits are $25 a month per 500, so heavy AI use escalates quickly and separately from headcount.
- The product's direction is AI development tooling. If you want a stable content platform, you are buying into a roadmap aimed elsewhere.
- Roles and peer review only arrive on Team, so smaller paid teams have a thin permission model.
- No self-hosting, and SSO and RBAC are Enterprise-only.
- builder.io hangs headless browsers, which is a small thing but tells you how heavy the marketing site is.
Builder.io pricing
Four tiers, and a meter that is unlike anything else in this directory. Free supports up to five users per space with a monthly Agent Credit allowance. Pro and Team are priced per user per month, at $24 and $40 billed annually or $30 and $50 monthly according to Builder's published comparison material, and both include 500 monthly Agent Credits per user. Enterprise is quoted.
Agent Credits are the thing to model, because they meter AI operations rather than content. Additional credits cost $25 a month per 500, which is a separate escalation path from headcount, and Pro adds rollovers so an unused month is not lost. Content delivery does not consume credits, so serving pages is not part of this calculation.
One caveat we could not resolve. Builder's two pricing pages state the free tier's credit allowance differently: builder.io/m/pricing says 25 daily and 75 monthly, while site.builder.io/m/pricing says 60 monthly. Neither page rendered the per-seat prices as readable text either. Confirm both numbers in-app before planning around them.
The honest summary is that this is priced as a development platform. If you are comparing it against a CMS billed on documents, locales and API calls, you are comparing two different kinds of product and the cheaper-looking one is probably the one you are measuring wrongly.
Free
$0
Up to 5 users per space
- Git integration, public previews, admin-only role
- A monthly Agent Credit allowance, see the note below
- Builder's two pricing pages state that allowance differently
- Enough to evaluate the visual editor properly
Pro / Team
From $24 / $40 per user/mo
Billed annually; $30 and $50 monthly
- 500 monthly Agent Credits per user on both
- Additional credits at $25/mo per 500
- Pro: 5 users per space, credit rollovers, built-in MCP
- Team: 20 users per space, roles, custom MCP, peer review
Enterprise
Custom
Custom seats and credits
- SSO, RBAC, privacy mode and faster environments
- Enterprise Git: Bitbucket, GitLab, Azure DevOps
- Design System Intelligence
- Optional self-hosted Git add-on
Query example
A minimal fetch against the live API, with credentials read from the environment rather than pasted inline.
curl -s -G "https://cdn.builder.io/api/v3/content/page" \ --data-urlencode "apiKey=$BUILDER_PUBLIC_KEY" \ --data-urlencode "url=/landing/spring-campaign" \ --data-urlencode "limit=1" # The response contains the component TREE the editor composed, # not rendered HTML. Your app maps each node to the React, Vue or # Svelte component you registered, which is why what marketing # builds is genuinely what engineering shipped. # # Note what is NOT metered here: this call does not consume Agent # Credits. Credits are for AI operations, not content delivery.
Limits and quotas
- Free: up to 5 users per space, with a monthly Agent Credit allowance Builder states inconsistently across its pricing pages.
- Pro: up to 5 users per space, 500 monthly Agent Credits per user.
- Team: up to 20 users per space, 500 monthly Agent Credits per user.
- Additional Agent Credits: $25 per month per 500 credits.
- Agent Credit rollovers are a Pro and above feature.
- Activity history is 30 days on Pro.
- MCP servers: built-in on Pro, custom on Team.
- SSO, RBAC, privacy mode and Design System Intelligence are Enterprise only.
- Enterprise Git integrations cover Bitbucket, GitLab and Azure DevOps, with an optional self-hosted Git add-on.
What developers say on Reddit
A sweep across the front-end and CMS subreddits returned no usable practitioner discussion of Builder.io as a platform. What surfaces instead is Mitosis, Builder's open-source component compiler, which developers do discuss and which tells you nothing about the commercial product.
That absence is worth interpreting carefully rather than reading as a negative. Builder sells largely to marketing and growth teams inside mid-size and enterprise organisations, and those buyers do not post build threads on r/webdev the way solo developers and agencies do. A platform can be widely used and quietly discussed.
It does mean there is very little independent peer evidence available on this one, particularly about how the shift toward AI agents has landed with existing customers. Weigh a trial more heavily here than you would for a platform with a visible community.
Verdict
Choose Builder.io when the requirement is marketers building pages on your real design system, and when you have engineering to register the components. That specific job is what it does better than anything else here, and the fact that editors compose with production components rather than a parallel set is why the output is maintainable.
Understand that you are buying an AI development platform now. The meter is Agent Credits, the plans are per seat, and the roadmap is design-to-code and agent tooling. That is a coherent product and it is not a headless CMS in the sense the rest of this directory means, so comparing it on documents and API calls will mislead you in both directions.
Confirm the numbers before you commit. Builder's own pricing pages disagree on the free credit allowance and did not render the per-seat prices for us. That is a small thing that matters when the whole model is per user and per credit, so get both figures from inside the product rather than from any page, including this one.
Builder.io FAQ
How much does Builder.io cost?
Free supports up to five users per space. Pro and Team are per user per month, reported at $24 and $40 billed annually or $30 and $50 monthly, each including 500 Agent Credits per user. Extra credits are $25 a month per 500. Enterprise is quoted.What are Agent Credits?
The meter for AI operations on the platform: design-to-code, content generation and agent work on your codebase. They are not consumed by content delivery, so serving pages does not draw them down. Pro and above include 500 per user monthly, and Pro adds rollovers.How many Agent Credits does the free tier include?
Builder states this inconsistently. One pricing page says 25 daily and 75 monthly; another says 60 monthly. We could not reconcile the two and are not guessing which is current, so confirm the figure inside the product before planning around it.Is Builder.io still a CMS?
Yes, and it is still a good one for visual page building. But the platform is now organised around AI agents, priced per seat and per credit, with design-to-code and MCP servers as headline features. If you want a conventional content platform billed on documents and API calls, the model will feel wrong.What makes the visual editor different?
Editors drag and drop your actual registered React, Vue, Svelte or Angular components rather than a parallel set of Builder primitives. What marketing assembles is therefore built from production code on your real design system, which is what stops these tools generating pages engineering refuses to maintain.Does Builder.io support MCP?
Yes, and unusually thoroughly: built-in MCP servers on Pro and custom MCP servers on Team, so agents can reach your own systems rather than only Builder's. That is further than most platforms in this directory have taken agent integration.Can I self-host Builder.io?
No. It is hosted only, with SSO, RBAC and privacy mode reserved for Enterprise. Enterprise does offer an optional self-hosted Git add-on, but that concerns where your repository lives rather than where the platform runs.Builder.io or Storyblok?
Storyblok if you want a visual editor attached to a conventional, predictably priced headless CMS. Builder.io if you want visual composition against your own component library and are buying into AI-agent tooling as well. Storyblok is the safer CMS purchase; Builder is the more ambitious platform bet.
Other platforms worth a look
This is an independent review. We have no affiliate relationship with Builder.io, earn nothing if you sign up, and no vendor pays for placement in the directory. Prices were read from the vendor's own pages in September 2026 and change without notice.