Next.js compatibility
Supported
| Area | Supported |
|---|---|
| Next.js | 16.3.8 and later 16.x releases |
| Routers | App Router and Pages Router |
| Flowpane route | Node.js runtime, Node 22 or later |
| Hosting | Ordinary self-hosted Node.js deployments |
Other routes in your application can keep using Edge, server rendering, static generation or ISR. Only the Flowpane route at /api/flowpane must run on Node.js.
Not supported
- Edge-only hosting for the Flowpane route
- Pure static export
- A configured
basePath - Next.js versions below 16.3.8
- Other or future major Next.js versions, until Flowpane has reviewed them
Other hosting environments are not currently supported.
What the evidence covers
A static public/robots.txt is compared byte for byte with the public Site. A static public/sitemap.xml is part of the source evidence, so a change to it is recorded as Source activity, but its bytes are not compared with the public sitemap; the Integrations page shows that comparison as unproven. For robots and sitemap sources written in code, Flowpane records that the implementation changed; it does not know what the code returns, so the public check remains the result. Page metadata, imported dependencies, content from a CMS or API, and request-time changes are not covered by the build evidence.