Builder.io

Agents clone and push to repositories on GitHub, GitLab, Bitbucket and Azure DevOps, with enterprise and self hosted Git providers on higher plans, and deliver every change as a pull request.

Built in MCP servers connect Supabase and Neon for database work, Netlify for deployments, Linear for tickets and Zapier for hundreds of other services, and custom MCP servers reach a company's own databases and tools, so generation can replace placeholder data with real records or read the related Jira ticket and implement against it. A Figma plugin turns designs into code, and the Chrome extension pushes visual edits from a running site straight into the codebase.

Sourcebuilder.io/c/docs/builder-code-integrationsread 2026-10-18

Hundreds of agents can run at once, each in its own cloud container with a full development environment, code access and a live browser preview, so a team can assign a batch of tickets and come back to finished pull requests, monitoring and steering the work across streams from one dashboard.

People and agents share a branch in real time: an engineer can start hard work locally, push the branch, and a designer, product manager and QA continue on it while the engineer reviews the final diff. Review agents check each change and push fixes to the pull request on their own, closing review loops before a person steps in.

Sourcebuilder.io/llms.txtread 2026-10-18

Design System Intelligence indexes a company's component library, design tokens and coding standards so every generated change uses its own patterns instead of one off components, with up to three design systems on Pro and unlimited on Enterprise, and Figma tokens can be mapped to code. Projects can be pointed at chosen design systems, environment variables and runtime dependencies, and connected MCP servers let agents pull requirements from Jira tickets or data from Supabase while generating. An asset library holds shared images and files for projects.

Sourcebuilder.io/c/docs/builder-code-project-settingsread 2026-10-18

Every change ships as a pull request with a clear description, engineers approve everything before it ships, and the team's existing Git review and merge process stays in place. The Team plan adds commenting and peer reviews inside Builder and password protected previews, and teammates can watch and edit alongside an agent in real time. There is no step to approve a plan before an agent starts editing, and review agents push their own fixes to the pull request before a person reviews it.

Sourcebuilder.io/llms.txtread 2026-10-18

Builder.io reports SOC 2 Type II compliance, with a trust center for review.

Team plans add Admin, Developer, Designer and Editor roles, Enterprise adds role based access control in which designers can edit the interface but not backend logic, file level permissions set with glob patterns for sensitive code, and private projects with permissions per role or user.

Enterprise single sign on connects Okta, Google Workspace or Microsoft Entra, privacy mode and training opt out are on by default for Enterprise, and site access control and a desktop only access setting restrict where projects can be opened.

Sourcebuilder.io/c/docs/enterprise-hubread 2026-10-18

A single dashboard shows the progress of every running agent across workstreams, each agent exposes a live browser preview of its work, and pull requests carry descriptions of what changed. Pro keeps 30 days of activity history and Team adds usage metrics, with Enterprise organization insights listing the most active users. A step by step record of an agent's commands and decisions, or an export of agent activity to outside monitoring, is not offered.

Sourcebuilder.io/pricingread 2026-10-18

Projects, branches, design systems and settings persist in a space, Pro keeps a 30 day activity history, and agent credits can roll over between months. Context for each task comes from the repository, the indexed design system and the ticket or thread that started it. There is no memory of past tasks, decisions or team preferences that agents write to and draw on beyond the code, project settings and history the team already keeps.

Sourcebuilder.io/pricingread 2026-10-18

Builder runs as a cloud service with agents in cloud containers, and development can also run locally in Docker or through the Builder Desktop app, with Enterprise able to supply custom Docker images with exact configurations and to restrict a project to the desktop app. Code stays in the customer's own repositories and reaches production through its CI/CD, and Enterprise can connect self hosted or custom Git providers. There is no self hosted Builder service and no choice of the region where Builder processes data.

Sourcebuilder.io/llms.txtread 2026-10-18

Teams start from their own repositories and design systems rather than from a catalog of packaged agents, and Figma designs or a captured web layout can seed a change. On Enterprise, templates can be shared across spaces and a whole space can be duplicated within an organization, while Builder Content brings its own page and content templates for marketing teams. There are no ready made agents for particular roles or jobs.

Sourcebuilder.io/c/docs/enterprise-hubread 2026-10-18

Work starts from an @Builder.io mention in a Slack channel, where the bot reads the thread and posts updates and previews back, from a Jira ticket assigned to or mentioning the bot, which it reads for acceptance criteria, from a branch pushed from Claude Code, Cursor or VS Code, from the Chrome extension on a running site or localhost, from Figma, or from the web and desktop apps.

Slack and Jira agents come with the Team plan, and the Agents Run API lets a CI pipeline or internal tool hand the agent a prompt. Each of these begins with a person's request or a call the team scripts; nothing in Builder starts an agent on a schedule or a monitoring signal.

Sourcebuilder.io/llms.txtread 2026-10-18

Teams can pick among Claude, Codex, Gemini and other models for each task and switch between them freely, with the same models a team already uses wrapped in Builder's collaboration layer, and Enterprise supports custom models for compliance needs. Agent credits carry a fixed dollar value covering the underlying model cost plus Builder's margin, so model choice changes how fast credits are spent.

Sourcebuilder.io/llms.txtread 2026-10-18

The Agents Run API starts Builder's agent from a team's own systems, such as a CI pipeline or an internal tool: a POST to api.builder.io/agents/run, authenticated with the space's private key as a bearer token, carries the prompt, the Builder user the run acts for and optional images, files or reference URLs, and returns the branch and project URL where the agent keeps working in the background.

A Metrics API reports code generation usage, projects and agent events by organization or space. The builder.io CLI launches a local repository, a multi repo workspace or the desktop app, AGENT.md files give the agent standing instructions, and custom MCP servers, the VS Code and Chrome extensions and a Figma plugin extend where work comes from.

Sourcebuilder.io/c/docs/agents-run-apiread 2026-10-18

Review agents run static analysis on every change, catch style violations, flag security vulnerabilities and performance issues, and validate generated code against ESLint rules, accessibility standards and performance budgets, then fix what they flag and update the pull request. Each agent's live browser preview lets people check the result as it builds. Automated browser testing that clicks through updates and reports bugs with video is still coming soon, so tests are not yet run against the app for the team.

Sourcebuilder.io/llms.txtread 2026-10-18

The Chrome extension connects a person to a running site, localhost or a page behind a login, lets them select elements and change them visually, and captures layouts from any web page into Builder, with the person doing the driving. Agents show a live browser preview of their own work, and the Agents Run API can point an agent at a live webpage it fetches and analyzes for reference. Browser testing by QA agents is still coming soon, so no agent yet clicks through a site, operates a desktop or works in outside software on its own.

Sourcebuilder.io/llms.txtread 2026-10-18