PageKit review: a self-hosted white-label builder on GrapesJS

Read this first

EditorStack is funded by GJS.Market. PageKit is GJS.Market's product. That is a direct commercial interest, and it is why this page is shorter and more hedged than the others: there are fewer facts here that we can verify independently, and we would rather say so than pad the page.

Concretely, three things are true of this entry that are not true of most others in the dataset: its pricing is vendor-stated and unverified by us, several capability fields are null because we could not confirm them from a source we trust, and it carries no score. See disclosure for the full arrangement and the rules it operates under.

What PageKit is, and who it is for

PageKit is a packaged website builder application built on GrapesJS, sold under a one-time licence and installed on your own infrastructure. Its intended buyer is an agency or a SaaS product that wants a branded builder without a per-site or per-seat subscription.

The category it competes in is small. Most commercial editors are subscriptions, and most self-hosted options are either open-source engines you must assemble or marketplace scripts of uncertain provenance. A packaged, self-hosted, one-time-licence builder sits between those and is a real gap in the market — which is presumably why it exists.

Whether it fills that gap well is a question we cannot answer from primary sources, and we are not going to answer it from our funder's marketing copy.

Architecture

Built on the GrapesJS engine, so the editing model is the one in the GrapesJS review: an iframe canvas, a component tree, a style manager, and portable HTML and CSS as the output. That inheritance matters for exit risk — what you store is web standard markup, not a vendor document format.

The product layer supplies what the engine does not: the application shell, project management and the branding controls that make a white-label deployment possible. Because it is self-hosted, the operational responsibilities — updates, backups, uptime — are yours.

How we assessed it

We have not run PageKit hands-on. There is no npm package or public repository to verify against the registry, so unlike most entries in this dataset there is no primary source behind the technical fields, and they are null where we could not confirm them.

Applying our methodology strictly here is the point. A funder's product is exactly where a comparison site's standards get quietly relaxed, and the visible test of whether ours have been is that this page has no score, no measured bundle size and several empty fields.

Strengths

A one-time licence. For an agency running many client sites, replacing a recurring per-site fee with a fixed cost is a substantially different business model — and it is the main reason to look at this category at all.

Self-hosted data. Page content stays on your infrastructure, which clears the procurement objection that ends most hosted-SDK conversations in regulated industries.

Portable output, inherited from the engine. HTML and CSS rather than a proprietary format, so leaving is a migration rather than a rewrite.

White-label by design. Branding controls are part of the product rather than an enterprise upsell.

Limitations

Proprietary, on a small vendor. The engine underneath is open; the product is not. Assess vendor longevity as you would for any small software vendor, and ask what happens to your deployment if support ends.

Unverified pricing. The $199 / $449 / $899 tiers are vendor-stated. We could not confirm them independently, and our funding relationship means you should not treat our repetition of them as verification.

No independent benchmarks here. No measured bundle size, no time-to-editor figure, no score. Our own conflict is the reason, and it means this page gives you less evidence than any other review on the site.

Self-hosting is operational work. Updates, backups, storage and uptime are yours. The one-time licence is not a one-time cost.

Not a React-component editor. Inherited from GrapesJS: your own React components do not become editable units on the canvas.

Pricing

Vendor-stated one-time tiers of $199, $449 and $899. Confirm current pricing with the vendor.

If you are weighing this against building on the free engine yourself, the build-versus-buy calculator is the right tool, and it will tell you to build whenever the arithmetic says so. If you are weighing it against subscription SDKs, PageKit vs GrapesJS Studio SDK sets a one-time licence against a subscription on the same engine.