Your users want a page builder. You don’t want the mess.

Teams keep shipping “content editing” as a pile of forms, then wonder why marketing still pings engineering for every landing page change.

So you try a generic builder. It breaks your design system, bloats your stack, and turns your app into a theme park ride you can’t steer.

Here’s the deal: Puck flips the model. You bring your React components. Puck gives your users a visual editor that can only assemble what you allow.

What Puck actually is

Puck is an MIT-licensed, open-source visual editor for React apps (see puckeditor.com). It’s built for product teams who want “Webflow vibes” inside their SaaS - without handing the keys to a third-party CMS.

It gets better: Puck also ships an AI page builder flow. Users can prompt a draft page, then tweak it with the same blocks you already ship.

Why devs care (and why users stop filing tickets)

Constrained editing, not chaos

Puck lets end users build pages constrained to your components. That means fewer broken layouts, fewer one-off CSS hacks, and fewer “can you just move this 2px?” threads.

Block-based authoring that maps to real code

You define blocks. You define fields. You decide what “a page” means in your product. Users drag, edit, and reorder without learning your codebase.

AI drafts without the blank-page tax

Puck’s AI mode can generate a first pass using the blocks you expose. The AI can’t invent random widgets you don’t support. You keep the rails on.

Extend it with plugins

Puck exposes a plugin rail and editor surface you can shape around your workflow - custom pickers, internal data, guardrails, the stuff real apps need.

Who it’s for

If you ship a React SaaS and your users need to assemble pages (docs, help centers, landing pages, in-app content, templates), Puck gives you a fast path.

If you want another generic site builder, look elsewhere. Puck wants you to own the experience.

Category "React Page Builders" on Achiv

1. Puck