NextJS With ISR

Heya, @renewablezip01

With App Platform, you don’t really get “CDN everywhere for anything generated at runtime” by default.

For ISR: when a page is first generated (or re-generated after the revalidate window), that generation happens on your app container (the Node runtime). The resulting HTML can be cached at the edge depending on cache headers, but it’s not the same as a guaranteed “static export pushed to a CDN like a pure static site.” So expect the first request after a revalidate to be slower (it’s doing the build), and then subsequent requests are fast while cached.

For assets: your _next/static/* (JS/CSS/chunks) are static and are typically served via the platform’s CDN/edge caching. That part is usually great.

For next/image: image optimization is done by the Node server at request time (unless you’re using a custom loader). So the first request for a given transformed image hits your app, and then it may be cached downstream if cache headers allow it. If you want “always CDN” behaviour, the common approach is to use an external image CDN (Cloudflare Images, Imgix, etc.) or put originals in Spaces + CDN and use a loader that points there.

If you share whether you’re deploying as “Static Site” or “Web Service” on App Platform (and your Next.js version), I can tell you what behaviour you can realistically expect with ISR + images on DO.

Hope that this helps!