Next.js tied to Vercel creates vendor lock-in Planned
Planned: Scoped for the next release.
Claim the Vercel page
Claiming is free. You prove you work at Vercel with an email address at vercel.com; Friction sends a link there.
- 46 reports from users of Vercel
- 53 separate source threads
- 2017–2026 the years they cover
- Most recurring theme: Difficulty self-hosting Next.js without Vercel, 7 threads
These are public today, under your product's name. A reply from Vercel sits under the report, on the record, marked as verified at vercel.com: the next person who reads it sees you answered.
What Vercel would post on the top report
Built on the report people repeat most on this page. Nothing appears until you post it.
A first reply, under the report
A board post, with a public status
A changelog entry, linked to the report
Fixed: Next.js tied to Vercel creates vendor lock-in
Resolves: Next.js tied to Vercel creates vendor lock-in
Reports are not edited or removed by the vendor; a wrong one is flagged and reviewed within 3 working days. More on what vendors get.