What is WizeStudio?
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.
Do I have to use your components?
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.
Where is the page layout stored?
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.
What happens to my site if I cancel or my subscription lapses?
Your site keeps rendering exactly as before. The packages that serve pages in production — the renderer and the schema — are MIT-licensed and contain no licensing code at all, so there is nothing in the production path that can expire or fail closed. A lapsed subscription disables the editor and nothing else. This is structural rather than a policy we promise to honour.
What happens if your licence servers go down?
Nothing happens to you. Licences are Ed25519-signed tokens verified offline on your own server, so a licence check never depends on reaching us. An unreachable or slow server is treated as unknown, never as invalid. Tokens also carry a 28-day grace window past expiry, so a firewall rule or an expired card in dunning cannot take your editor away mid-recovery.
Is it really free on development machines?
Yes, with no time limit and no account required. localhost, 127.0.0.1, ::1, any .local or .test hostname and private network ranges such as 192.168.x.x are classified as development hosts. They never need a licence and never count against your domains, so you can evaluate the entire product before paying anything.
How many domains does a licence cover?
One live domain per licence, plus unlimited development and staging hosts. You register your live domain from the dashboard and can change it when you need to — during a migration, for example.
Which CMS platforms are supported?
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.
Does it work with Next.js?
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.
Can editors bind components to CMS content?
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.
Is the page output good for SEO and performance?
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.
How do I install it?
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.