--- title: Why Companies Are Saying Goodbye to Next.js 🚪💨 | daily.dev description: Developers and companies are increasingly moving away from Next.js due to issues like performance bottlenecks, overengineering, and vendor lock-in with Vercel.... canonical: https://daily.dev/posts/why-companies-are-saying-goodbye-to-next-js--yy6j25jkw twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Why Companies Are Saying Goodbye to Next.js 🚪💨 | daily.dev og:description: Developers and companies are increasingly moving away from Next.js due to issues like performance bottlenecks, overengineering, and vendor lock-in with Vercel.... og:url: https://daily.dev/posts/why-companies-are-saying-goodbye-to-next-js--yy6j25jkw og:image: https://api.daily.dev/og/posts/yy6J25jkW.png og:image:alt: Why Companies Are Saying Goodbye to Next.js 🚪💨 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Why Companies Are Saying Goodbye to Next.js 🚪💨 **[Community Picks](https://daily.dev/sources/community)** · 3 min read · 683 upvotes · 96 comments ## Summary Developers and companies are increasingly moving away from Next.js due to issues like performance bottlenecks, overengineering, and vendor lock-in with Vercel. While Next.js offers benefits such as fast performance and SEO-friendly architecture, its complexities and limitations have made alternatives like Astro, Remix, and Qwik more appealing. For simpler, faster solutions, some developers are resorting to using React with Vite instead. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@jamesdavis7** · 154 upvotes > Finally, we can move on to overcomplicating something else! **@emrekyk** · 33 upvotes > I think this post raises some valid points about evolving complexity, but many of the issues mentioned here seem to stem more from individual developer experience than from fundamental flaws in Next.js itself. > > I've been using Next.js for over two years, building multi-tenant B2C applications in the food delivery space, and I’ve found that most of the so-called “overengineering” becomes an advantage when used properly. Features like the App Router, Middleware, and RSCs might have a learning curve, but they also offer serious flexibility and performance when applied thoughtfully. > > Every tool... **@jream** · 30 upvotes > I'm tired of next js and react In general > I've been enjoying the way svelte 5 does things. **@elevenbits** · 24 upvotes > Would be nice to see the data proving these statements. Without them I do not believe you. **@alx\_dsz** · 24 upvotes > We just said hello ## Similar posts on daily.dev - [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 1 upvotes · 0 comments - [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments - [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments - [CNCF Unveils Schedule for KubeCon \+ CloudNativeCon Europe 2026](https://daily.dev/posts/cncf-unveils-schedule-for-kubecon-cloudnativecon-europe-2026-ikhcoa5cb) · CNCF · 2 upvotes · 0 comments - [CNCF Debuts KubeCon \+ CloudNativeCon Japan 2026 Schedule](https://daily.dev/posts/cncf-debuts-kubecon-cloudnativecon-japan-2026-schedule-xp5pyudub) · CNCF · 1 upvotes · 0 comments --- Tags: [#webdev](https://daily.dev/tags/webdev), [#react](https://daily.dev/tags/react), [#performance](https://daily.dev/tags/performance), [#nextjs](https://daily.dev/tags/nextjs) [View this post on daily.dev](https://daily.dev/posts/why-companies-are-saying-goodbye-to-next-js--yy6j25jkw) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Why Companies Are Saying Goodbye to Next.js 🚪💨","url":"https://daily.dev/posts/why-companies-are-saying-goodbye-to-next-js--yy6j25jkw","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/why-companies-are-saying-goodbye-to-next-js--yy6j25jkw"},"datePublished":"2025-04-18T09:06:42.422Z","dateModified":"2025-04-18T09:07:16.412Z","description":"Developers and companies are increasingly moving away from Next.js due to issues like performance bottlenecks, overengineering, and vendor lock-in with Vercel....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/68b8cec34f23eacb120603d2a43fe8a4?_a=AQAEuj9","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/68b8cec34f23eacb120603d2a43fe8a4?_a=AQAEuj9","isAccessibleForFree":true,"articleSection":"Community Picks","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Community Picks","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1655817725/logos/community","url":"https://daily.dev/sources/community"},"commentCount":96,"discussionUrl":"https://daily.dev/posts/why-companies-are-saying-goodbye-to-next-js--yy6j25jkw","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":683},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":96}],"keywords":"webdev,react,performance,nextjs","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Community Picks","item":"https://daily.dev/sources/community"},{"@type":"ListItem","position":3,"name":"Why Companies Are Saying Goodbye to Next.js 🚪💨"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/why-companies-are-saying-goodbye-to-next-js--yy6j25jkw","comment":[{"@type":"Comment","text":"Finally, we can move on to overcomplicating something else!","datePublished":"2025-04-18T15:32:09.682Z","dateModified":"2025-04-18T15:33:12.663Z","url":"https://daily.dev/posts/yy6J25jkW#c-o2br8uGjP","author":{"@type":"Person","name":"James Davis","url":"https://daily.dev/jamesdavis7","image":"https://media.daily.dev/image/upload/s--LfM5k4Xi--/f_auto,q_auto/v1700407141/avatars/avatar_7Ou187uVNzn7pA4dhApKU"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":154}},{"@type":"Comment","text":"I think this post raises some valid points about evolving complexity, but many of the issues mentioned here seem to stem more from individual developer experience than from fundamental flaws in Next.js itself.\nI’ve been using Next.js for over two years, building multi-tenant B2C applications in the food delivery space, and I’ve found that most of the so-called “overengineering” becomes an advantage when used properly. Features like the App Router, Middleware, and RSCs might have a learning curve, but they also offer serious flexibility and performance when applied thoughtfully.\nEvery tool has trade-offs, and of course Next.js isn’t perfect or one-size-fits-all — but generalizing isolated struggles into a blanket “Next.js is broken” narrative doesn’t do the ecosystem justice.\nConstructive critiques backed by data and real use cases would be much more helpful for developers trying to make informed decisions. Just my two cents!","datePublished":"2025-04-21T10:47:51.081Z","url":"https://daily.dev/posts/yy6J25jkW#c-lH554abAE","author":{"@type":"Person","name":"emre kyk","url":"https://daily.dev/emrekyk","image":"https://lh3.googleusercontent.com/a/ACg8ocLCXV9oT1uNnlFkReD1t0hbzCQpO4oh7isu2V290IvxYnZ4BQ=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":33}},{"@type":"Comment","text":"I’m tired of next js and react In general\nI’ve been enjoying the way svelte 5 does things.","datePublished":"2025-04-21T04:37:16.616Z","url":"https://daily.dev/posts/yy6J25jkW#c-fcmGYUEy4","author":{"@type":"Person","name":"Jesse Ω","url":"https://daily.dev/jream","image":"https://lh3.googleusercontent.com/a-/AOh14GiqSafa30VIvU5cJZh-cYztO7Pz8_deN-l5HmT_Uy0=s100"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":30}},{"@type":"Comment","text":"Would be nice to see the data proving these statements. Without them I do not believe you.","datePublished":"2025-04-21T07:20:20.972Z","url":"https://daily.dev/posts/yy6J25jkW#c-bs74XXqWM","author":{"@type":"Person","name":"Elevenbits","url":"https://daily.dev/elevenbits","image":"https://avatars.githubusercontent.com/u/19406?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":24}},{"@type":"Comment","text":"We just said hello","datePublished":"2025-04-19T07:38:07.013Z","url":"https://daily.dev/posts/yy6J25jkW#c-aWHKRmWJy","author":{"@type":"Person","name":"alx","url":"https://daily.dev/alx_dsz","image":"https://lh3.googleusercontent.com/a/ACg8ocK27JxxI9GyvuY0vk7NgjHzYn6YthC6MLcXppn4X6JlodQZeQ=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":24}}]} ```