Docs Developer Site
Developer Docs Next.XP next Nextjs Deployment

Deployment

Contents

A production Next.XP deployment consists of an XP service, a reachable Guillotine endpoint, and a Next.js service. Visitors connect to Next.js; Content Studio loads it directly in its preview pane.

Requirements

For Next.XP 6, the front end requires Node.js 24.15.0+ and npm 10.9.2+. The supported framework stack is listed under Starter dependencies.

Connectivity

Source Destination Purpose

Next.js server

Guillotine endpoint

Content and page queries

XP server

Next.js server

URL mappings and revalidation

Browser

Next.js server

Public site traffic and Content Studio preview

The Next.js URL configured in XP must be reachable from the XP nodes and from editors' browsers; localhost is only appropriate when all of them share a host. Use HTTPS and a private network where possible.

Configuration alignment

Before deployment, verify that:

  • ENONIC_MAPPINGS names existing XP projects and sites.

  • ENONIC_API points to the API root of the correct XP installation.

  • The same secret is used for ENONIC_API_TOKEN and the selected XP front-end configuration.

  • The Next.XP app is installed with the front-end URL configured explicitly, and added to every XP site rendered through Next.XP with its front-end configuration selected.

  • The front-end response policy allows Content Studio to embed the site.

  • Preview, mappings, and revalidation API routes are deployed with a server runtime.

Public delivery

Next.XP does not prescribe a hosting provider. Standard Next.js deployment, CDN, cache, observability, and scaling guidance applies. Preserve query parameters and cookies on the Content Studio preview path when a proxy or platform sits in front of Next.js.

See Next.js documentation for framework deployment options and XP documentation for platform operations.

Contents

Contents