TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: Risk of Vendor Lock-In with Next.js

1 pointsby StefanWestfalover 1 year ago
I appreciate the new features that Next.js is rolling out, such as the app router. However, I'm curious if there's a risk of future features working exclusively, or at least best, when hosted on Vercel. This could be a strategic move by Vercel, creating vendor lock-in to get people to host on their platform. On the other hand, it might not pose any issues, and Next.js may perform well on other platforms after overcoming initial obstacles. Do you believe that choosing Next.js could lead to vendor lock-in in the mid-to-long term?

2 comments

flagged24over 1 year ago
I think app router and react server components optimize for serverless&#x2F;edge. That optimization comes at a cost that I think is best visible in this GitHub issue: <a href="https:&#x2F;&#x2F;github.com&#x2F;vercel&#x2F;next.js&#x2F;discussions&#x2F;42732">https:&#x2F;&#x2F;github.com&#x2F;vercel&#x2F;next.js&#x2F;discussions&#x2F;42732</a><p>As someone who runs Next.js with a custom server setup on a VPS, I think the haydays of Next.js are behind us. I&#x27;m looking to simplify my frontend stack. I love how stable my Node.js backend is and want the same for my frontend.
fintechieover 1 year ago
You can bet that their ultimate goal is increasing the number of customers... Personally I&#x27;ve grown tired of riding the hype du jour, this whole saga of server&#x2F;client components reminds me of Meteor.js. We keep going in circles.