Editors drag and drop your own React components onto a canvas that renders your real site. Layouts are saved as structured JSON in your own CMS. No shortcodes, no page-builder markup, nothing you cannot read.
Free and MIT · Unlimited sites · No account, no key, no limits
01 What makes it different
Every widget is an ordinary React component plus a manifest. The builder reads only manifests. The renderer imports only components. WizeStudio never needs to know what a pricing table is — it just orchestrates the one you wrote.
Not a preview, not an approximation. Your real Next.js app loads in the canvas and the editor drives it over a versioned message protocol. What an editor arranges is produced by the same code path that serves your visitors, so “looked fine in the builder” stops being a category of bug.
Point any component property at a CMS field instead of typing it in. Repeat a component over a collection to build product grids and post lists that stay in sync with your data. Nested loops each get their own alias, so a category can contain its products without the two fighting over a name.
WizeStudio{
"type": "wize/card",
"repeat": { "source": "products", "as": "product" },
"props": {
"title": { "kind": "binding",
"source": "product", "path": "name" },
"price": { "kind": "binding",
"source": "product", "path": "price.amount",
"fallback": "—" }
}
}02 In the box
Style any property per breakpoint. The canvas resizes to match, so you are editing the layout you are looking at.
Colours, spacing and type live as tokens that render to CSS custom properties. A rebrand is one edit, not a hundred.
Save a section once, use it everywhere. Edit the original and every instance updates — instances are references, not copies.
Every change is an invertible patch. Undo, redo, autosave and history are one mechanism, so they can never disagree.
Manifests declare what may nest inside what. Editors get real composition without being able to build something broken.
A full tree of the page. Select, reorder and reparent anything, including elements a click cannot reach.
Referential integrity is enforced as an invariant, not hoped for. A layout that would render broken cannot be saved.
Editing takes a lease. Two people opening the same page see who holds it and can take over deliberately.
03 Integration
There is no migration, no content rewrite and no proprietary runtime. You install a plugin, register the components you already have, and render a document.
Restart Strapi. It registers itself and adds WizeStudio to the admin sidebar.
npm i @wizestudio/plugin-strapi
A component plus a manifest describing its props and slots. The manifest is data.
defineWidget({ type, props, component })Hand the layout and your component pack to the renderer. That is the integration.
<WizeRenderer document={doc} />04 Honestly compared
Most teams choose between a WordPress-style builder and hand-built components. Both trades are real. This is what each one costs you.
| WizeStudio | Classic page builders | Hand-built components | |
|---|---|---|---|
| Editors can build pages | Yes, visually | Yes, visually | No — needs a developer |
| Components stay yours | Your React, unmodified | Their widget system | Your React, unmodified |
| What gets stored | Normalized JSON in your CMS | HTML or shortcodes | Typed CMS fields |
| Leaving later | Read the JSON, it is documented | Rewrite every page | Nothing to leave |
| New layout without a deploy | Yes | Yes | No |
| Production runtime cost | None — it is your component tree | Builder runtime and CSS | None |
| If the vendor disappears | Renderer is MIT; site keeps working | Site depends on their runtime | Unaffected |
05 Licensing, stated plainly
Not a trial, not a limited edition, not free-until-you-go-live. The entire builder is MIT licensed with no licence check anywhere in it — which you can verify before you install it, rather than take on trust.
Unlimited sites, pages, editors and layouts. No account, no key, no host classification, no expiry. There is no paid version of this software.
No licence server, no telemetry, no runtime dependency on us. Our uptime cannot affect your CMS, because nothing in it ever calls us.
The Agency Pack is two additional packages solving problems a single-site user does not have. It adds; it does not unlock.
06 Pricing
Everything above costs nothing and always will. What is sold is a separate pair of addons for people running many sites — the problems you only get once one Strapi is not one website.
WizeStudio
MITEverything on this page. No account needed.
Agency Pack · Monthly
Agency Pack · Yearly
Two months freeTwo months free, billed annually.
The pack is a pre-order and does not ship yet. You are charged today and can have every penny back, no questions asked, at any point before the addons ship. Email support@wizeb.com and it is done. You almost certainly do not need it until you are running more than one site or more than a few dozen pages.
What is in it07 Questions
WizeStudio is a visual page builder for headless CMS platforms, currently shipping for Strapi. Editors compose pages by dragging your own React components onto a canvas that renders your real site. Layouts are saved as structured JSON in your own content type, so nothing is locked in a proprietary format.
No, and that is the central design decision. A WizeStudio widget is an ordinary React component plus a manifest describing its props and slots. The builder reads only manifests and never imports your component; the renderer imports your component and never reads a manifest. WizeStudio does not need to know what a pricing table is in order to let someone arrange yours.
In a JSON field on your own content type, as a normalized document of typed nodes with stable IDs. It is queryable, diffable and migratable, and any other tool you build can read it. WizeStudio never stores rendered HTML.
Yes — all of it, MIT licensed, with no account, no key and no limits. Unlimited sites, pages, editors and layouts. There is no feature switched off and no trial that ends. The paid Agency Pack is separate software that adds things a single-site user does not need: a block library shared across projects, and component change impact analysis across every stored page.
The page builder keeps working, because it never depended on a subscription — it is free software you already have. You lose the shared library and the impact analysis; the blocks already pulled into your projects stay where they are, since they are ordinary blocks once installed. Your published site is untouched either way: the packages that render pages contain no licensing code at all.
Nothing happens to the page builder — it has no licence check in it at all, so there is nothing for our uptime to affect. The Agency Pack verifies offline against an Ed25519-signed token, so it does not depend on reaching us either. An unreachable or slow server is treated as unknown, never as invalid, and tokens carry a 28-day grace window on top of that.
No — it is a pre-order, and we would rather say so plainly than imply otherwise. Both addons exist as tested libraries; what is missing is the Strapi plugin around them. Buying now funds the work and reserves the price, and you can have a full refund at any point before it ships — email support@wizeb.com. The page builder is free, finished, and does not depend on any of this.
Two addons. The shared block library lets you publish a section once and pull it into every project you run, then shows which sites are behind, which have been edited locally, and what a pull would overwrite. Component change impact analysis tells you which stored pages a manifest change breaks before you merge, generates a migration plan, dry-runs it, and reports what would still be broken. Both are separate packages; neither is the page builder with a switch flipped.
One live site. The domain checked is the website being edited, not the Strapi instance editing it, so if you run one Strapi behind several websites each of those needs its own licence — and the plugin holds them side by side, so there is nothing to switch between. Development hosts (localhost, .local, .test and private networks) never need a licence and are never counted. You register a live domain from the dashboard and can change it at any time, during a migration for example.
Strapi 5 today. The core is CMS-agnostic by design: platform support is a thin adapter package, so adding a new CMS does not touch the builder, the renderer or the document format.
Yes. The renderer is a React package and ships a Next.js integration. The editor canvas loads your real Next.js app in an iframe and drives it over a versioned message protocol, so what an editor arranges in the builder is produced by exactly the same code path that serves your visitors.
Yes. Any component property can be pointed at a field in your CMS instead of being typed in by hand. A component can also repeat over a collection, which is how product grids and post lists are built without the core knowing what a product or a post is.
The output is whatever your components render — WizeStudio adds no wrapper markup, no runtime JavaScript of its own and no inline style blobs to the production page. Server rendering, streaming and static generation all work normally because the renderer is an ordinary React component tree.
Install @wizestudio/plugin-strapi in your Strapi project and @wizestudio/renderer-react in your front end, register your widgets, and point the plugin at your front-end URL. The whole integration is fetching a layout document and handing it to the renderer along with your component pack.
WizeStudio is free, MIT, and complete. There is nothing to sign up for and nothing to evaluate against a clock — build a real page with your real components and decide afterwards whether you ever need the Agency Pack.