You’re live on Pantheon.

This page is being served by your new Next.js site — built from the nextjs16 upstream, deployed through Pantheon’s Git-based workflow, and delivered over our Global CDN. Everything worked. Now make it yours.


What just happened

Deployed via Git.

Your code lives in a repo wired to Dev, Test, and Live environments. Push a commit and Pantheon builds and deploys it — no pipeline to configure, no servers to babysit.

Rendered by Next.js 16.

Server components, ISR, API routes — the full framework runs here in production, managed.

Delivered by the CDN.

This page is already cached at the edge. Your site stays fast under traffic spikes, and your backend stays protected from bots — from day one, not after a config project.


Make it yours

  1. 1

    Clone your repo.

    Grab the connection info from your dashboard, run npm install && npm run dev, and you’re editing locally in minutes.

  2. 2

    Open a pull request.

    Every PR gets its own full preview environment — a real URL your whole team can review before anything ships.

  3. 3

    Connect a backend.

    Pair this frontend with WordPress, Drupal, or Content Publisher for a decoupled architecture your content team will actually enjoy.

  4. 4

    Replace this page.

    To make this homepage feel like home, edit app/page.tsx, commit and push.


Bringing an existing site?

Most teams move their first Next.js site to Pantheon in under an hour. Talk to your Customer Success Manager to book a 30-minute working session and we’ll migrate one live, together.


Go deeper

Docs

Watch

  • Platform Tour: Next.js in Pantheon

    On-demand webinar going step-by-step from zero to a live Next.js site, including a Content Publisher to Next.js content update demo.

  • LinkedIn Lives from Pantheon

    Conversations on modern web development, including the Figma to Claude to Next.js to Pantheon rebuild, the PHP-to-JavaScript talent shift, Going Headless Without Losing Your Head, and Next.js for Grownups.

Read