Builder.io

What it is

Builder.io is a visual development platform with a visual CMS attached. It is made for teams that already have a codebase and a design system and want non-engineers to change the real product instead of working from mockups. The home page puts it this way: "Everyone works from the same source of truth, with the context they need and no handoffs to clean up later." The reader it serves is a product, design, marketing and engineering team at a company that ships software, not a founder looking for a drag-and-drop tool to avoid code altogether.

The about page says the founders, Steve Sewell and Brent Locks, "met on the campus of UC Berkeley in 2011." The pages do not say where the company is headquartered. The platform is organized into 2 product lines, Code and Content, and the pricing page explains how they work together: "Components created in Code can be used by your whole team as part of your design system in Content."

What you build and how

There are two ways to use it, and each one maps to a category in this directory.

The first is the CMS and campaign side, which is why Builder.io appears under blogs and content management. The home page describes an "Agentic CMS": "Ask Builder to create and manage content, run A/B tests, personalize, and schedule updates. Your team can preview, approve, and publish with brand and workflow intact." The visual editor is described as "Production code, edited like design", a visual canvas "wired directly into your components and design tokens". A marketer builds pages in that canvas out of components developers have registered. The company's wording for campaigns is "Create pages, update content, and run campaign changes on the real product. Preview, get approvals, and publish when it's ready, with brand and code still in sync." That sentence is also what puts the product in the landing-page group: pages and campaign changes are built without waiting for the next sprint. The navigation lists use cases such as Landing Pages, Marketing Sites, Headless Commerce, Mobile Apps and Multi-Brand, and it lists Shopify among the integrations.

The second is the app and product side. The web-apps page says Builder "starts from your existing codebase, design system, project rules, and Git workflow, so features and fixes stay connected to the systems your team already uses." You can "start from a new prompt or connect an existing repo". Designers, PMs and other teammates "can refine UI, copy, layout, states, and flows visually on a branch", while "Permissions, pull requests, and reviews keep engineering in control of what ships." Engineers keep their own tools: "Code in Builder or your AI tool of choice, then push the branch so designers, PMs, and QA can polish pixels, edit copy, and run tests in the real app."

Git is the integration backbone. The company says Builder supports "branch and pull request workflows, including Send PR, Update PR, and Auto-push." The enterprise page names GitHub Enterprise, GitLab and Azure DevOps. It adds multi-repo support to connect "to your component library", and "Design System Intelligence" to help the AI understand a design system. Brand consistency comes from design tokens. The page promises you can "Reuse your code components exactly as they are, with no rewrites, wrappers, or refactoring required", with the visual editor used "with any framework or architecture."

On the design side there is a Figma integration, and the site announces "Visual Copilot - Figma to production in half the time." The platform menu offers "Convert designs to clean code" and "Use your framework". Work requests can start in "Slack or Jira", and the company says Builder "integrates directly with tickets, docs, and data sources, and reaches the rest of your internal tools through MCP connectors." The enterprise page adds "pre-built or custom MCP servers" for internal systems.

The AI is credit based. Prompts run on "Agent credits", which is the unit behind the pricing and usage limits below. The company compares itself with coding tools and with AI app builders. It says Cursor, Claude Code and Codex "are developer coding environments", while Builder "gives product, design, and engineering the same branch, preview, comments, and pull request." Against AI app builders, its answer is that Builder "starts from your existing codebase", so output "fits your app". It also states plainly that "Your team still reviews, tests, and decides what gets merged."

The evidence

Pricing is published in four tiers, Free, Pro, Team and Enterprise. Free is "For individuals looking to explore the platform". Pro is "For individuals and small teams shipping projects". Team is "For teams building and iterating on larger projects". Enterprise is "For organizations needing scale, control & support" and is sold through "CONTACT SALES". The pages give no monthly price for Pro or Team. The comparison table lists spaces included, users included, "Max users per space" (the values shown are 5, 5 and 20, then Custom) and Agent credits. The pricing note says "Plan features, pricing, and limits are subject to change." A space is the unit you subscribe to: "subscriptions are per space", and spaces "keep your code, content, and projects organized."

Credit limits are stated in the FAQ. On the Free plan you get "15 Agent credits per day, with a total limit of 60 Agent credits per month. Daily credits reset at midnight UTC and monthly credits reset on the first day of each calendar month." On the Pro and Team plans for Code, "you get 500 Agent credits per user per month". If you need more, "you can purchase in increments of 500 monthly AI credits for $25/month." Running out on Free means waiting for the reset or upgrading.

On security, the enterprise page says Builder is "SOC 2 Type II compliant". The web-apps page says "Third-party LLMs never train on your data. On Enterprise plans, Builder doesn't either." It mentions "Private connectivity" to "Run behind your firewall". Enterprise support includes "Forward Deployed Engineers". The company claims "3 out of 4 of the largest US companies ship faster with Builder Enterprise plans." Everlane's CTO, Dave King, is quoted: "With Builder, we're able to see the same quality results that were only previously possible through reliance on our engineering team, who now have capacity to tackle higher-value projects."

The pages do not state a template count, an open-source license or a hosting region. They do not describe a self-hosting option, and they do not cover content-model limits such as entries or locales.

Who it suits

Builder.io suits a company with an engineering team and a design system that wants marketers, designers and PMs to ship changes safely: landing pages, copy updates, campaign tests, and UI fixes that otherwise wait for a sprint. Enterprise teams that need SOC 2 Type II, Git-provider support and no-training terms are the buyer the enterprise page is written for.

It is a weaker fit for a solo founder with no codebase, since the model depends on a repo, components and tokens, and a plain app builder will be faster to start. Credit-based AI use is a limit to budget for, especially on Free, which is capped at 15 credits a day and 60 a month. The pages show no Pro or Team prices, so a small team has to open the pricing page to see them.