Next.js has long been considered one of the most powerful frameworks in the React ecosystem. Backed by Vercel, it made server-side rendering (SSR), static site generation (SSG), and API routes accessible to React developers. But despite its strengths, a surprising number of companies are choosing to walk away from Next.js.
So what’s driving this shift? Let’s break it down.
1. Complexity Is Creeping In
Next.js started as a relatively simple abstraction over React. But with the introduction of the App Router, server components, middleware, and other new concepts, the learning curve has grown significantly.
“What used to be a simple SSR app now feels like managing a microservices ecosystem inside my frontend codebase.” — A Senior Engineer on Hacker News
Key Concerns:
- Fragmented documentation
- Confusing routing between
pages/andapp/ - Difficulty debugging server components
2. Vendor Lock-In and Vercel Bias
Many developers feel that Next.js is increasingly optimized for deployment on Vercel, rather than being fully platform-agnostic. This tight integration can create friction for teams using AWS, Netlify, or their own infrastructure.
Signs of Vercel Bias:
- Features like ISR and Edge Middleware are easier to use on Vercel
- Complex build steps when self-hosting
- Limited caching control off-Vercel
3. Performance Paradox
Next.js promises blazing fast performance — and it can deliver — but it often requires careful tuning. Out of the box, developers may face:
- Overloaded JavaScript bundles
- Hydration issues with server/client components
- Inconsistent Time to First Byte (TTFB) with ISR or SSR
Many devs expect speed “for free,” but real-world results often require constant optimization.
4. Developer Experience (DX) Fatigue
With React Server Components, streaming, edge functions, and more, some developers feel like Next.js is trying to be too many things at once. Teams are spending more time understanding how things work under the hood than actually building product features.
5. Better Alternatives Are Emerging
As the frontend landscape evolves, other frameworks are stepping in to fill the gaps — with better DX and performance out of the box.
Popular Alternatives:
- Astro: Great for static sites with zero-JS by default
- SvelteKit: Lightweight, reactive, simple routing
- Remix: Embraces web fundamentals and works well across platforms
- Nuxt (Vue): Preferred by teams migrating away from React
6. Overkill for Simple Sites
For basic websites, Next.js is often seen as overengineered. Static site generators like Hugo, Astro, or Eleventy are faster, simpler, and easier to deploy — especially for blogs, documentation, and marketing sites.
Final Thoughts
Next.js isn’t dying — not by a long shot. It’s still a robust and widely adopted framework. But as it grows in power and complexity, it may no longer be the default choice for every use case.
Companies are re-evaluating their needs, and many are favoring tools that are leaner, simpler, and more focused on their specific use cases.
TL;DR:
- Next.js is powerful but increasingly complex
- Vendor lock-in concerns with Vercel
- Performance tuning required for best results
- Alternatives like Astro, SvelteKit, and Remix offer fresh approaches
👉 Whether you’re staying with Next.js or considering a switch, it’s a good time to step back and ask: Is this still the right tool for the job?