Engineering·2026-06-28·5 min read

Why We Build Everything on Next.js (And When We Do Not)

Next.js has become our default framework for web applications. But defaults should be challenged. Here is our honest assessment of when Next.js is the right choice — and when it is not.

Next.jsReactWeb DevelopmentArchitecture

Our Default Stack

For the past two years, Next.js has been our go-to framework for web applications. It gives us server-side rendering, API routes, excellent developer experience, and a deployment story that is hard to beat.

When Next.js Excels

  • **Content-heavy applications** where SEO matters
  • **SaaS dashboards** that benefit from server components
  • **Marketing sites** that need to load fast
  • **Full-stack applications** where you want one codebase

    • When We Choose Something Else

  • **Real-time applications** with heavy WebSocket usage (we use plain Node.js or Go)
  • **Mobile-first products** (React Native with a separate API)
  • **Compute-heavy backends** (Python or Go microservices)
  • **Simple APIs** that do not need a frontend (Express or Fastify)

    • The Key Insight

    The best technology choice is the one that matches your problem. We love Next.js, but we love solving problems more.

    Written by

    Wevly Engineering

    All Posts