Site builders · Source-available · Next.js + TypeScript
A production Next.js app around the open-source GrapesJS core: auth, multi-tenant projects, page storage, publishing, custom domains, lead capture, checkout and a plugin loader. Sold as source. Self-hosted. Yours to modify.
Early birdFirst 20 buyers get Agency at the Developer price — and lifetime updates.
A self-hosted landing page builder and micro-ecommerce app, built as a real Next.js application rather than a demo wired to an editor.
The open-source core with editor chrome that ships as source: block palette with search, layer tree, style manager, traits, device switching, and autosave guarded by an optimistic version token so two tabs can't silently overwrite each other.
Publishing renders to a cached publication row that visitors hit without ever loading the editor bundle. Wildcard subdomains through middleware, plus custom domains with Caddy on-demand TLS validated against your own domain table.
Per-page title, description, canonical, OG image generation, and a per-tenant sitemap.xml and robots.txt. Pages carrying JSON-LD emit it into the published document. Measured at 100/98/100/91 on Lighthouse.
A form block with a field builder in the trait panel, honeypot plus optional Turnstile or hCaptcha, email and webhook notification on submit, and a leads inbox with CSV export.
Products, cart and checkout behind one payment adapter. An offline test provider is the default so you can evaluate without keys; Stripe and PayPal drop in with your own credentials. Orders inbox and confirmation emails included.
A Zod-validated manifest, ESM plugins registered before project load, semver range checks against the installed GrapesJS, and an in-admin gjs.market browser with one-click install. Two plugins ship bundled; the catalogue endpoint is configurable.
Weighted variant serving with impression and conversion tracking and a declared winner, plus exit-intent and timed popups. Both are ordinary blocks and screens — no separate service to run.
Workspaces with owner, editor and viewer roles, email invitations with expiring tokens, a last-owner guard, and an opt-in review gate: editors submit, an owner approves, then it publishes.
Rebrand the admin for your clients, and an offline Ed25519 licence check that degrades to a dismissible notice. A vendor outage never blocks the dashboard and never touches a published page.
Full source, the operational scaffolding to run it, and the tests that prove it works. No compiled blobs, no phone-home requirement.
Two deploy targets, both supported on day one: docker compose up on a plain VPS, or Vercel with managed Postgres.
| Runtime | Node.js 20 or newer |
|---|---|
| Database | PostgreSQL 16 |
| Host | A VPS with Docker, or Vercel + managed Postgres |
| Memory | ~1 GB RAM for the primary Docker path |
| DNS | A wildcard record, for subdomain routing |
Not shared hosting. Shared hosting will not work. Next.js needs a Node runtime — we would rather say so here than sell you a refund.
No. PageKit is sold as source under a one-time licence. You deploy it on your own infrastructure and, on the SaaS tier, can run it as your own product. We host nothing for you.
The open-source grapesjs core only, currently 0.23.5. Never the commercial Studio SDK, whose per-domain licence cannot be redistributed to you. All the editor chrome is built on the core API and ships in the source you receive.
A plain VPS via docker compose — Postgres, the app and a Caddy reverse proxy — or Vercel with managed Postgres. Both are documented and supported. Shared hosting will not work, because Next.js needs a Node runtime.
The Agency tier covers up to ten client projects and includes white-label admin branding. The SaaS / Unlimited tier lets you run your own hosted product and charge end-users, with priority support. The Developer tier is one production project.
Twelve months of updates are included with every tier; renew afterwards at 40% of the licence price per year. Because you self-host, you download and upgrade on your own schedule. Updates are never force-applied to a running install.
Nothing. The licence check verifies an Ed25519-signed token offline and has a long grace period. A failure degrades to a dismissible notice in the admin panel — it never blocks the dashboard and never touches a published page. Test it; that is the intended behaviour.
No. An offline test payment provider is the default, so the full cart and checkout flow runs on a laptop with no accounts and no network. Stripe and PayPal are drop-in once you add your own credentials.
Version 0.1.0, pre-release. The editor, publishing, domains, leads, ecommerce, the plugin loader, A/B tests, popups, team roles, approvals and white-label are all built and covered by tests. Multi-language pages and AI copy generation are on the roadmap and are not written yet. Joining the waitlist is how you get the source first.
Counted, not claimed
These are repository counts, not marketing rounding. Run them yourself against the source you receive.
Not a mockup
The gallery above is drawn in CSS so it stays in step with the product. Everything below is a capture of the running application, untouched. Open any of them full screen to read the detail.
Hard-won
If you have integrated GrapesJS before, you have met at least one of these. They are the reason a weekend prototype takes a month to make production-ready.
getProjectData() returns what restores an editing session. getHtml() and getCss() produce what you publish. Store the wrong one and you either ship editor scaffolding to visitors or hand your users a page they can no longer edit.
Two separate stores: pages.project_data holds the session, a publications row holds the rendered artifact. Published pages are served from the second and never touch the editor code path.
Fonts, CSS resets and any runtime library the rendered content needs must be injected into the frame. Adding them to the host page does nothing at all, which reads as a styling bug and gets debugged in the wrong file for an afternoon.
Everything the canvas needs goes through the editor's canvas.styles and canvas.scripts config, so what you see while editing is what the published document actually loads.
It executes inside the canvas frame and cannot close over the surrounding scope. A script referencing an imported symbol type-checks cleanly and throws at runtime — invisible until a user drags that component onto a page.
Every custom component passes its dependencies through script-props. The rule is enforced in review rather than discovered in production.
Content referencing a type that isn't registered yet quietly degrades to plain elements and permanently loses its behaviour for that session. Nothing errors. The page just gets worse every time it is opened.
The plugin loader resolves and registers a project's plugins before the load path runs, and refuses version-incompatible plugins loudly instead of failing silently inside the canvas.
Where it sits
The comparison that matters is not against other page builders. It is against the four weeks you were about to spend building this.
| Capability | PageKit | A $55 builder script | Studio SDK | Build it yourself |
|---|---|---|---|---|
| Stack | Next.js 15 · TypeScript strict | Typically PHP 7 | Your app plus a vendor SDK | Whatever you already run |
| Editor licence | OSS core, redistributable | Varies, often unstated | Per-domain, not redistributable | Your choice to make |
| Multi-tenant + custom domains | Wildcard subdomains, on-demand TLS | Rarely, and rarely well | Not in scope — you build it | Roughly a fortnight |
| Publish pipeline separate from the editor | Cached publications table | Usually renders through the editor | Your responsibility | Easy to get subtly wrong |
| Automated tests | 12 E2E specs, 10 unit suites | Almost never any | Not applicable | Time you would rather spend elsewhere |
| Source yours to modify | Full, unobfuscated | Usually | SDK is a closed dependency | By definition |
| Time to a published page | One docker compose up | Hours of setup, then hope | Days, once you wire the rest | Weeks, honestly |
Extend it
The plugin loader is a first-class part of the product, not an afterthought — and the gjs.market storefront is built into the admin, so extending an install does not mean forking it.
npm run create-plugin scaffolds one, and the same loader takes it from any URL.No surprises
Current state as of August 2026, version 0.1.0. We would rather you read this now than discover it after buying.
Early access
One email when it ships, the early-bird bonus, and the public roadmap. Nothing else — no drip campaign, unsubscribe any time.
One email at launch. No spam, no drip campaign, unsubscribe anytime.