Security

Define the trust boundary

Pagiera provides editor and publishing primitives, not an authentication product. Your application decides who can list projects, open a draft, upload assets and publish a page.

Protect editor routes

Require an authenticated session and an explicit editor role before rendering the studio. Repeat the authorization check in API handlers; hiding a navigation link is not access control.

Keep secrets on the server

PostgreSQL, Redis and OpenRouter credentials must never use the NEXT_PUBLIC_ prefix. Do not serialize them into the editor bootstrap or return them from health endpoints.

Validate external data

Treat template registries and APIs used by Request blocks as external input. Use HTTPS, allowlist hosts when possible, limit response sizes and avoid forwarding arbitrary user-provided headers.

Production checklist

• Editor and preview routes require authentication.
• Publishing requires a narrower role than ordinary editing when appropriate.
• Database and Redis connections use production credentials and encryption.
• Preview pages send noindex.
• Backups and a document recovery process exist.
• Logs do not include secrets or complete authorization headers.