Web app foundation
Next.js
Use a React framework with server rendering, routing and server-side application features.
Sources checked
Our recommendation
When to choose it
Choose Next.js when server rendering or server routes are a real requirement. For a frontend that only calls an existing API, start with Vite instead.
A good fit for
- A React app needing request-time server behavior
- A project combining server and browser code
Choose something else when
Choose Vite when static frontend output and an independent backend are enough.
Watch out for
- Server and browser code have different credential and execution boundaries.
- Select a host and adapter that support the features you use; a static export cannot preserve every server feature.
How costs work
Framework tooling; hosting and backend costs are separate
Choose the production runtime before estimating infrastructure. The framework is not a database or hosting account.
Check current official terms and pricing ↗This is a pricing model, not a monthly quote. Check your region, intended usage and current plan before buying.
What connects to it
- React
- Framework-compatible hosting such as Vercel
These are technical connections you can configure. Selecting a card creates no accounts or resources.
Compare the alternatives
Learn the boundary before you connect it
Lessons open through your account and the kits you own.
Check the evidence
Feature sources were reviewed on 4 Oct 2026. Plans and availability can change.
- Framework features ↗
React framework, routing and server/client application features.
- Compatible hosting ↗
One supported framework-aware deployment route.