PageKit vs Brizy: a one-time licence against a monthly platform

Disclosure first

EditorStack is funded by GJS.Market, which sells PageKit. This page compares our funder's product with a competitor.

What we do about that: neither product is scored, PageKit's pricing is labelled vendor-stated and unverified, we have run neither hands-on, and this page gives no verdict. The rules are on the disclosure page, and if that makes this comparison less decisive than the others, that is the cost of the conflict rather than something to write around.

The structural difference

PageKit: you buy a licence, you install it, you run it. Costs are a one-time payment plus your hosting and your operations. Data stays on your infrastructure.

Brizy: you subscribe, they run it. Costs are monthly and predictable, operations are theirs, and data sits on their platform unless you reach the enterprise tier that lists on-premise.

Everything else — both are white-label, both target agencies, both produce client websites — is common ground.

What each model actually costs

A subscription is an operating expense that continues as long as the product exists. A licence is a capital cost plus an operations line that is easy to underestimate: someone patches the server, someone restores the backup, someone answers when the builder is down during a client's launch week.

Agencies that already run infrastructure absorb that easily. Agencies that do not are usually better served by a subscription even when the licence looks cheaper on a spreadsheet, and we would say the same if our funder sold the subscription instead.

What to ask both vendors

1. Total cost at our site count over three years, including hosting for the self-hosted option.
2. What exactly is rebranded — editor, dashboard, emails, published output, asset URLs.
3. What happens to client sites if we stop paying, or if the vendor stops publishing.
4. What is the update and security-patch policy? For self-hosted software this is the question.
5. Can our own systems provision sites?

Where we can be useful without a verdict

Two facts from our dataset rather than our opinion.

Brizy publishes its White Label price and what it includes; PageKit's tiers are vendor-stated and we could not verify them independently. If verifiable published pricing is part of how you evaluate vendors, that difference is visible and it does not favour our funder.

Both are proprietary. If an open dependency chain matters, the answer is neither, and building on GrapesJS — which PageKit is built on — is the route our calculator prices at roughly 520 hours.

Decision checklist

1. Do we already operate servers? If not, self-hosting is a new capability, not a saving.
2. Will any client's procurement ask where data lives?
3. How long do we expect to run this? Licence economics improve with time; subscriptions do not.
4. How much do we trust each vendor's longevity? Ask both for their patch history.
5. Would the free engine underneath cover our requirement?

The number that matters

Zero — the number of verdicts on this page. That is deliberate, and it is what a funding conflict should cost a comparison site. Use the checklist above and the white-label category page, which is computed from the dataset rather than curated by us.