Brizy review: a white-label builder sold to agencies and SaaS

What Brizy is, and who it is for

Brizy occupies a space this site's readers ask about constantly and that few products serve: a finished website builder that an agency or SaaS can put its own name on.

The buyer is a delivery business. You have clients who need sites, you do not want to run fifty WordPress installations, and you do not want your clients logging into a product with someone else's logo on it. Brizy's White Label plan answers exactly that, with client management included rather than assembled.

What it is not is an editor you embed inside your own application's interface. Your customers go to a branded platform; they do not edit inside your product's own screens. If that distinction matters — and for a SaaS adding page building as a feature it usually does — the embeddable category is the right place to look instead.

How we assessed it

We have not run Brizy hands-on under our test procedure, so this page carries no score, no code sample and no bundle measurement, in line with our methodology. There is no npm package or public repository to verify against a registry, so the technical fields in our dataset are sparse and several are null. Pricing is recorded from the vendor's published white-label page with the date we checked it.

Strengths

White-label is the product, not an upsell. Own logo, own domain, own client-facing platform, at a published price — which is more than most of this category offers at any price.

Ten sites included at the entry tier, which changes the per-site arithmetic that pushes agencies off Webflow and similar per-site platforms.

Client management included. The part agencies underestimate when they consider building: not the editor, but the accounts, permissions and hand-off around it.

An enterprise path with on-premise. Rare in this category, and the answer to the data-residency objection that ends most hosted-platform conversations.

A free tier exists for evaluating the builder itself before the white-label conversation.

Limitations

Not embeddable in your own UI. The recurring theme of this profile, and the reason it is not an alternative to GrapesJS or Puck despite the overlapping vocabulary.

Quote-only enterprise. The tier that carries on-premise and API integration has no published price, so the case that most needs budgeting is the one you cannot budget.

Little independent verification available. No public repository, no registry entry, no independently published benchmarks. Compared with the npm-distributed libraries in this dataset, more of what you know comes from the vendor.

Proprietary throughout. If a fully open dependency chain is a requirement, this is not a candidate.

Per-site costs beyond the included ten need modelling before comparing with a build.

Questions to ask before you buy

1. What exactly is white-labelled — the editor, the client dashboard, the emails, the published output? Clients notice vendor domains in asset URLs.
2. What happens to client sites if we stop paying? Get the answer in writing before migrating a portfolio onto the platform.
3. What does the eleventh site cost, and the hundredth?
4. Is on-premise a real product or a roadmap item? Ask for a reference customer running it.
5. Can we provision sites through an API? That is the difference between a builder and a platform your own product can drive.

Where it sits in this dataset

Brizy is one of a small group that can be resold under your own brand — Duda, PageKit and, with substantially more engineering, an open-source engine. Against Duda it is more explicitly white-label-first; against PageKit it is a subscription rather than a one-time licence, and hosted rather than self-hosted.

The white-label category page lists everything in the dataset that clears the branding bar, and the agency use case works through the arithmetic that decides between buying one of these and building on an engine.