// the find
BuilderIO/builder
Visual Development for React, Vue, Svelte, Qwik, and more
Builder.io is a visual CMS and page builder that lets non-developers edit pages built with your existing React/Vue/Angular/etc. components, without touching code. It sits between your design system and your content team — you register components, they drag and drop. Primarily aimed at marketing teams at companies that already have a mature frontend.
The SDK-first model is the right call: you define what components are editable and with what props, so content editors can't break your design system by going rogue. The multi-framework support is genuine — they maintain separate SDKs per framework rather than shipping one blob and hoping. The Figma-to-code path is useful for teams where design and implementation are constantly out of sync. The monorepo is well-organized with changesets and per-package publishing, which matters for a project with this many moving pieces.
This is fundamentally a SaaS product — the OSS repo is the SDK half, but the visual editor, content API, and hosting all live on builder.io's servers. You're not self-hosting this; you're integrating with their cloud. The local development story is painful: you need a Builder.io account, an API key, and a live internet connection just to see the editor. Several examples are stale (angular-gen1 still uses protractor, gatsby example is empty), which signals the SDK surface area is growing faster than the examples are maintained. The abstractions Builder uses to bridge your components into their editor (Mitosis under the hood) add a non-trivial debugging layer — when something renders wrong in the editor but correctly in your app, good luck tracing which side owns the bug.