← All tools

Web app foundation

Vite

Develop and build a frontend, then publish its output to a compatible host.

Sources checked

Our recommendation

When to choose it

Start with Vite for a frontend-only app. Choose Next.js when the architecture needs request-time server rendering or server routes.

A good fit for

  • A frontend calling an existing API
  • Learning browser UI without a full-stack server framework

Choose something else when

Choose a server framework when your app must run private logic or render pages on each request.

Watch out for

  • The development server is not your production backend.
  • Anything bundled into browser code can be read by the browser user; keep private credentials on a separate server.

How costs work

Build tooling; hosting and backend costs are separate

Estimate the host and API you will deploy, rather than treating a local development server as infrastructure.

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

  • Frontend frameworks
  • Static hosting and independent APIs

These are technical connections you can configure. Selecting a card creates no accounts or resources.

Compare the alternatives

Vite vs Next.js →

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.