When we reach for it
Public sites that have to be fast and indexable, and product interfaces sitting next to them. Rendering per route is the reason we pick it: the decision is made where the content is, not once for the whole application.
Web and application frameworks
Next.js development
A React framework that lets each route choose how it is rendered, so a marketing page can be static, a dashboard can be dynamic, and both can live in one codebase.
What we reach for first
When we would argue against it
A heavily interactive application behind a login gains little from server rendering and inherits a framework’s opinions along with it. If nothing needs to be indexed, a plain React build is often the simpler answer.
What it looks like in delivery
This site is a Next.js application, and it is the closest thing to a live specimen we can offer: server components by default, JavaScript shipped only where an interaction needs it, and content validated at build time so an invalid page fails the build instead of reaching a visitor.
Where this appears on the site
Published work that names it
Derived from the stacks published on those pages, not written here — so this list cannot claim something the page it points at does not say.
Working in Next.js?
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.