PageKit vs Zillapage: two self-hosted builders, very different evidence

Disclosure

EditorStack is funded by GJS.Market, which sells PageKit. One of the two products on this page belongs to our funder. Neither is scored, and we are not going to tell you which to buy. See disclosure for the arrangement and the rules it operates under.

Why these two are compared

Self-hosted plus one-time licence is an unusual combination. Most commercial editors are subscriptions, and most self-hosted options are open-source engines you assemble yourself. These two occupy the same small space, and someone searching for "self-hosted page builder one-time payment" will find both.

What we can verify about each

PageKit. Built on the GrapesJS engine, which means the editing model and the portable HTML output are known quantities. Vendor-stated one-time tiers of $199, $449 and $899, which we could not verify independently — and the vendor funds this site. No public package or repository, so several dataset fields are null.

Zillapage. A PHP landing page and e-commerce builder distributed through code marketplaces. We found marketplace and reseller listings rather than a canonical vendor pricing page, so we publish no price. No public repository, no registry entry, no verifiable release history, and most capability fields are null.

Between them, one entry has thin evidence and one has almost none. That is a meaningful difference even before any feature is discussed.

What to ask, whichever you consider

For self-hosted software you install and expose to users, the questions are about the vendor as much as the product:

1. What is the patch cadence for security issues, and how are they announced?
2. What exactly does the licence permit — client work, resale, multiple deployments?
3. Is there a changelog showing activity in the last twelve months?
4. What happens to our deployment if the vendor stops publishing?
5. Has anyone independent reviewed the code?

Ask both. Compare the answers rather than the feature lists.

The alternative worth considering

If a self-hosted builder with no recurring cost is the requirement, there is a third option neither vendor will mention: GrapesJS is free under BSD-3-Clause, and Silex is a complete free-software builder application from a non-profit.

Both require more work than buying a packaged product. Both come with evidence you can check — public repositories, published release histories, licences you can read — which is precisely what is thin on this page.

Verdict

We do not give one. Our funding relationship with one side and the absence of verifiable evidence on the other mean any recommendation here would be worth less than the questions above.

What we will say plainly: if you are choosing a self-hosted builder to run in production, prefer the option whose provenance you can verify, and treat a missing changelog as a finding rather than an oversight. The self-hosted category page lists every option in this dataset that clears the self-hosting bar.

Decision checklist

1. Can we identify the vendor and their patch policy? Ask in writing; treat silence as an answer.
2. Does the licence permit client work and multiple deployments? Marketplace licences vary more than buyers expect.
3. Is there a changelog showing activity in the last twelve months?
4. Who reviews the code before it goes into production? For self-hosted software handling user content, this is not optional.
5. What is the fallback if the product is abandoned? For one of these, the underlying engine is open source, which is a meaningful difference.

The number that matters

Two source-verifiable facts against almost none. For PageKit we could confirm the underlying engine and an identifiable vendor, though not the pricing. For Zillapage we found marketplace listings and a visible resale ecosystem. Neither is a recommendation — but if you are installing software on your own server, provenance is a feature, and it is the one this comparison is really about.