Comparative: Deploying Sitecore XM Cloud on Vercel vs. Netlify

Deploying Sitecore XM Cloud requires a platform that not only supports your technology stack but also complements your development workflow. Vercel and Netlify each offer unique capabilities that cater to different deployment needs. This comparison, enriched with detailed deployment steps, aims to help you decide which platform is the best fit for your project.

Vercel Deployment Details

Pre-Requisites for Deployment

To deploy a Next.js XM Cloud app on Vercel, ensure that your application is connected to a GitHub repository. This setup will leverage Vercel's seamless GitHub integration for continuous deployment.

Environment Setup

Configure your project by setting up environment variables in Vercel for API keys and Sitecore API hosts, essential for connecting your Next.js application to the Sitecore instance.

Deployment Process on Vercel

The deployment on Vercel starts from its dashboard where you link your GitHub project. Vercel automatically detects and builds your Next.js application, managing deployments through its powerful edge network to ensure optimal performance.

Incremental Static Regeneration (ISR)

Vercel utilizes ISR for Next.js applications, enabling updates to static content without full rebuilds, enhancing content freshness with minimal delay.

Netlify Deployment Details

Pre-Requisites for Deployment

For deploying a Next.js XM Cloud app on Netlify, it's crucial to have your app ready with content already pushed to Experience Edge. Key environment variables include the Experience Edge API key and the GraphQL endpoint.

Environment Setup

Generate an API key through the XM Cloud deploy app, allowing Netlify to connect to Sitecore's staging environment. Configuring GraphQL endpoints and setting a public URL are also necessary steps.

Deployment Process on Netlify

Connect your GitHub project to Netlify and manually configure the project settings including the base directory, build command, and publish directory. Adjustments post-deployment include setting the runtime to Next.js and configuring the public URL.

Automating Updates with Webhooks

Utilize Netlify's deploy hooks to enable automatic rebuilds by integrating with Experience Edge. A webhook in Experience Edge can be set up through the admin API to trigger Netlify builds upon content updates.

Conclusion

Choosing between Vercel and Netlify for deploying Sitecore XM Cloud depends on your specific requirements for performance, ease of use, and automation capabilities. Vercel is best for projects needing fast performance and seamless integration with GitHub, while Netlify is suited for those requiring detailed control over build processes and content updates via webhooks.

For more detailed information on integrating with each platform, visit:

• Vercel Sitecore Integration
• Netlify Sitecore Integration