Docs Developer Site
Developer Docs Next.XP 5.x 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 connects to it through the Next.XP app.

Requirements

For Next.XP 5, the front end requires Node.js 24.15.0+ and npm 10.9.2+. The supported framework stack is listed on the Next.XP overview.

Connectivity

Source Destination Purpose

Next.js server

Guillotine endpoint

Content and page queries

XP server

Next.js server

Content Studio preview, renderability checks, and revalidation

Browser

Next.js server

Public site traffic

The Next.js URL configured in XP must be reachable from the XP nodes; localhost is only appropriate when both services 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 addresses the correct Guillotine installation.

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

  • The Next.XP app is installed and added to every site that needs Content Studio preview.

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

  • Preview 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 request headers 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