21 questions covering what Pagiera is, what it needs to run, how pages stay editable, where the data comes from and what the AI is allowed to touch.
The short version, before the setup details.
Pagiera is an open-source visual website builder distributed as an npm package for React and Next.js. It combines an editable responsive canvas, reusable components, layouts, page management and a server-rendered publishing runtime inside your application.
The Pagiera package is open source under the MIT license. Hosting, PostgreSQL, Redis, AI provider usage and other services can have separate costs. You are responsible for configuring and securing the application.
For pages, yes. Pagiera stores every page as a document in your own PostgreSQL database, keeps drafts separate from published revisions, and gives non-developers a visual editor to change them — which is the job a CMS does. It is not a headless CMS in the content-modelling sense: you do not define arbitrary collections and query them over an API. Instead, pages bind to the APIs you already have through Request and Repeat blocks.
Yes, and that is the common case. Install the package in your Next.js app, mount the editor behind your authentication, and render published documents on the server with pagiera/runtime. Marketing edits a page visually, previews the draft and publishes it; the content never leaves your infrastructure and no separate CMS service sits in the request path.
Both, deliberately. Pagiera is an npm package a developer installs into a React and Next.js application, and the thing it installs is a visual editor that non-developers can use. The developer owns the integration; the editor is where the pages get designed.
A hosted builder keeps your pages on its own platform and serves them from its infrastructure. Pagiera runs inside your application: the documents live in your PostgreSQL database, the pages are rendered by your own Next.js server, and the package is MIT-licensed, so there is no vendor account between you and your site.
What you need before the editor opens.
Yes. Install pagiera, connect PostgreSQL and Redis, mount the protected editor and API routes, and render published documents with pagiera/runtime. Your application manages authentication, infrastructure and deployment.
Node.js 20 or newer, React 18.3 or newer, the Next.js App Router for the full-stack integration, PostgreSQL and Redis. An OpenRouter API key is needed only for AI generation.
No. Pagiera creates the PostgreSQL tables it requires when the server initializes. Redis is used for published-page caching, template bundle caching and AI rate limiting.
Open /api/pagiera/health after starting the application. It verifies PostgreSQL, Redis and the configured OpenRouter model, which turns a silent misconfiguration into a readable answer.
No. Pagiera does not ship an authentication layer. You mount the editor route and the /api/pagiera route inside your own application and protect them with the authentication and authorisation you already use.
How a page stays editable after the first draft.
Use reusable components and linked layouts for shared structure. Layouts can include a children placeholder for page-specific content, so you do not need to rebuild navigation and footers for every page.
Pagiera includes editable carousel slides, carousel controls, marquees with child elements, customizable form fields, shader colors, icon libraries, and text hover and scroll effects. Check the installed version for each block's available controls.
Yes. The canvas shows responsive artboards side by side, and breakpoints carry isolated overrides, so a change made at one width does not silently rewrite the others.
Where the content comes from and when it goes live.
No. Saving updates the draft. Preview the draft, then publish to update the public page. The home slug maps to /. Publishing content does not deploy your host application or configure a domain.
Yes. Request blocks bind one returned object to their descendants and Repeat blocks iterate array results. Both support GET, POST, PUT, PATCH and DELETE sources, and request URLs, headers, query fields and bodies can reference route parameters and query values.
Yes for published pages. Request blocks are resolved on the server and finish before HTML is returned, so API-backed content is part of the initial response rather than being fetched in the browser afterwards.
No. Publishing updates the public page content and refreshes the cached revision. Deploying your host application, configuring DNS and managing your domain remain your own pipeline's responsibility.
What the model is allowed to change, and when.
Yes. The package includes an AGENTS.md integration guide for coding agents. Ask your agent to create native Pagiera document elements rather than a separate hardcoded page. The resulting document can be saved, opened in the visual editor, previewed and published.
Select a layer or use @ to choose a target in Luma. Supported requests propose text, style, hover or element additions. Review the old and new values before applying. Breakpoint-targeted requests are limited to supported layout updates. AI generation requires an OpenRouter key; supported operations depend on the installed version.
Yes. AI generation requires an OpenRouter key, and everything else — the canvas, components, layouts, data binding, previewing and publishing — works without one.
Still deciding?Install the complete visual builder, choose a starting point and shape it into something unmistakably yours.
