// the find
plasmicapp/plasmic
Visual builder for React. Build apps, websites, and content. Integrate with your codebase.
Plasmic is a visual drag-and-drop builder that integrates with existing React codebases, letting non-developers build and edit pages using components the dev team has already written. The GitHub repo contains the SDK, loader packages, and platform code; the actual visual editor is Plasmic Studio, a cloud-hosted SaaS product. It targets teams where marketing or content people need to ship pages without waiting on engineering.
The component registration API is well-thought-out — you call PLASMIC.registerComponent() with a props schema, and designers can only touch what you explicitly expose. They cannot accidentally break your component internals. Two distinct integration modes exist: loader (runtime CDN fetch, good for CMS workflows with ISR) and codegen (generates real React TSX into your repo, good for app development where you want no runtime dependency). The example directory covers 20+ real-world integration patterns including A/B testing, Contentful, Shopify Hydrogen, and custom targeting. The platform/ directory containing the actual editor is genuinely in the repo under AGPL, not just promised as 'open-source eventually.'
Their own README dedicates a full section to warning you that npm/yarn will corrupt your package versions — you'll hit duplicate @plasmicapp packages, need npm dedupe, and sometimes have to nuke lock files. That's not a documentation gap, it's a real architecture problem with a large exact-versioned monorepo surfacing into consumers' dependency trees. The loader approach has a hard runtime dependency on Plasmic's CDN — if their service has an outage, your pages break unless you've implemented explicit fallback caching yourself. The AGPL license on platform/ is a quiet trap for any company building proprietary software who wants to self-host the editor; MIT only covers the SDK packages. And design data lives in Plasmic's cloud by default, so you're betting on their business continuity unless you commit to the codegen workflow as your exit strategy from day one.