Builder is a visual development platform that connects to an existing site or app so teams can edit visually and generate code using components they already own, aimed at frontend developers and no-code builders working across React, Vue, Svelte, Qwik, Angular, Next.js, and Gatsby.
What it is
Builder is a visual development platform for modern web experiences, housed in a TypeScript monorepo published under the MIT licence. The repository contains the SDKs, usage examples, starter projects, and plugins that make up the open-source side of the Builder.io platform. The platform itself connects to an existing site or app rather than requiring a rebuild, so visual editing and code generation happen against the components a team has already written.
The concrete problem it solves is the gap between design and shipped code. Instead of hand-authoring page markup and styling for every marketing page, landing page, or content-driven screen, a team can take Figma designs or drag and drop its own components, then export the resulting code or publish the update through the SDKs. It also serves as a headless CMS, which means content authors work in a visual editor while developers keep the component library and the codebase as the source of truth. In practice it replaces the manual coding of pages that would otherwise be written by hand for each new campaign, experiment, or section.
Key capabilities
- Turns Figma designs into code through the visual editor workflow.
- Drag-and-drop editing of components already present in a connected site or app.
- Publish updates with a click, or export the generated code instead of publishing.
- SDKs that connect Builder to an existing app and push updates to it.
- Headless CMS behaviour for content-driven pages alongside visual editing.
- Starter projects and usage examples for frameworks including React, Vue, Svelte, Qwik, Angular, Next.js, and Gatsby.
- Plugins distributed from the same repository as the SDKs.
Who uses it and how
- Frontend teams with an existing React, Next.js, or Vue application that want visual editing without abandoning their component library.
- No-code and low-code builders producing landing pages and campaign pages without writing markup.
- Design and content collaborators who convert Figma files or drag-and-drop layouts and hand the result back to developers through export.
- Plugin and SDK consumers who pull packages from the repository to wire Builder into a live site.
- Teams that prefer publish-through-SDK updates over a separate hand-built CMS front end.
Getting started
The README directs new users to sign up for a free account at https://builder.io/signup, then connect the platform to an existing site or app using the SDKs in the repository's packages directory.
How it compares
No comparable products are named in the facts provided, so this project stands alone in this registry rather than being positioned against named alternatives. The frameworks it integrates with — React, Vue, Svelte, Qwik, Angular, Next.js, and Gatsby — are targets it connects to, not competitors.
When to use it — and when not to
Pick Builder when an existing component library should stay in place and non-developers need to edit pages visually, with MIT-licensed SDKs in the repository. Be aware that the README describes a hosted platform signup and defers technical detail to external Builder.io documentation, so anyone expecting self-hosting instructions in this repository will need to look further afield. The repository carries 148 open issues, which is worth reviewing against your own use case before committing.
