Next.js
React with the hard parts solved — rendering on the server, shipping to the edge, fast by default.
What it is, and why we use it.
Next.js is a framework on top of React that decides the hard architectural questions for you: pages render on the server (so they load fast and Google can read them), static pages get pre-built, and dynamic pieces hydrate only where needed. It's the closest thing the React world has to a default choice.
Nearly every web product we ship runs Next.js — marketing sites, dashboards, full SaaS apps. We hold every build to a performance budget: server components by default, client JavaScript only where interaction demands it, sub-200ms TTFB on real connections.
Next.js vs React SPA (Vite) vs Remix.
Next.js versus a classic React single-page app versus Remix — three ways of shipping the same React, with very different results on slow networks.
| Dimension | Next.js | React SPA (Vite) | Remix |
|---|---|---|---|
| Where pages render | Server first, hydrates on client | Entirely in the browser | Server first, web-standards flavoured |
| First load on a slow phone | Fast — HTML arrives ready to read | Blank screen until the JS bundle lands | Fast — same server-first story |
| SEO | Excellent out of the box | Needs workarounds (prerendering, SSR add-ons) | Excellent out of the box |
| Data fetching | Server components + actions, co-located | Client-side hooks; you build the conventions | Loaders & actions per route — very clean |
| Static + dynamic mix | Per-page choice: static, ISR, or fully dynamic | All dynamic, all client | Dynamic-first |
| Best hosting story | Anywhere, best-in-class on Vercel/edge | Any static host + your API | Anywhere Node runs |
Next.js wins when
- Public-facing products where SEO and first-load speed pay rent
- One codebase mixing marketing pages, app screens and API routes
- Teams that want conventions instead of architecture debates
React SPA wins when
- Internal tools behind a login — SEO irrelevant, sessions are long
- Highly interactive canvas/editor-style apps
- You already have a separate, settled API backend
Remix wins when
- Form-heavy, mutation-heavy apps — its action model is elegant
- You value web standards over framework magic
- Deploying to non-Vercel infrastructure as a first-class citizen
Next.js is our web default and the safest large-team React bet right now. We go SPA for logged-in tools where bundle size matters less than interactivity, and we keep an admiring eye on Remix for mutation-heavy products.
Thinking about Next.js?
Tell us what you're building — we'll tell you honestly whether Next.js is the right tool for it.