---
title: "Deployment options for JSS Next.js apps"
slug: "deployment-options-for-jss-next-js-apps"
abstract: "An overview of hosting options for JSS Next.js apps"
---
# Deployment options for JSS Next.js apps

Next.js applications can be hosted using various services, depending on the prerendering form and your preference.

> [!important]
> [Headless server-side rendering using the JSS proxy](https://doc.sitecore.com/xp/en/developers/hd/23/sitecore-headless-development/walkthrough--rendering-a-jss-app-server-side-using-the-headless-jss-proxy.html "Walkthrough: Rendering a JSS app server-side using the headless JSS proxy") is *neither needed for, nor compatible with, Next.js JSS applications*.
>
> Production hosting of Next.js JSS applications in [integrated mode](https://doc.sitecore.com/xp/en/developers/hd/23/sitecore-headless-development/start-a-jss-app-in-integrated-mode.html "Start a JSS app in integrated mode") is not supported.

## Deploying on Vercel

The creators of Next.js, Vercel, offer deployment and hosting solutions *optimized for Next.js*. They support all Next.js features out of the box, including incremental static site (re-)generation, hybrid rendering, and internationalization. Your application can be deployed directly from source control and optimized through Vercel's edge network and serverless functions. Refer to the following resources for more information about deploying to Vercel:

- [Walkthrough: Deploying JSS Next.js apps to Vercel](https://doc.sitecore.com/xp/en/developers/hd/23/sitecore-headless-development/walkthrough--deploying-jss-next-js-apps-to-vercel.html "Walkthrough: Deploying JSS Next.js apps to Vercel").
- [Next.js documentation on Vercel deployment](https://nextjs.org/docs/deployment#vercel-recommended).

## Node.js Server

Next.js JSS apps can be deployed to any hosting provider or environment that supports Node.js. For more information refer to the following resources:

- [Next.js documentation on Node.js Server deployment](https://nextjs.org/docs/deployment#nodejs-server).
- [A discussion on Next.js and Docker](https://github.com/vercel/next.js/discussions/16995).

## Static HTML Export

If you want to deploy your Next.js JSS app using a fully static HTML export, you must be aware of the [limitations in supported Next.js features](https://nextjs.org/docs/advanced-features/static-html-export#caveats) when using `next export`. For more information refer to the following resources:

- [Walkthrough: Exporting a JSS Next.js app to static HTML files with next export](https://doc.sitecore.com/xp/en/developers/hd/23/sitecore-headless-development/walkthrough--exporting-a-jss-next-js-app-to-static-html-files-with-next-export.html "Walkthrough: Exporting a JSS Next.js app to static HTML files with next export").
- [Next.js documentation on Static HTML export](https://nextjs.org/docs/advanced-features/static-html-export).
- [A Microsoft guide for deploying static-rendered Next.js websites on Azure Static Web Apps Preview](https://docs.microsoft.com/en-us/azure/static-web-apps/deploy-nextjs).

> [!important]
> To be able to use an advanced Sitecore editor with your JSS Next.js application, even if you export the app as static HTML with `next export` you must run a Next.js instance that is accessible to your Content Management role.

## Triggering Webhooks when publishing content

When prerendering the application with static generation or deploying static HTML with `next export`, you must trigger a `next build` and site deployment on publishing new content. To facilitate this, Sitecore Headless Services and Sitecore Experience Edge for XM can invoke a webhooks. You can leverage Sitecore webhooks with Vercel deploy hooks.