Vendor Lock-in Definition & Misconceptions

• Vendor lock-in = intentional effort to create obfuscation/barriers
• Innovation resulting in new paradigms ≠ vendor lock-in
• Vercel getting bad reputation due to amount of Next.js innovations they support
• Conversation triggered by Ryan's tweet claiming Next.js "isn't really open source software, only runs on infra with internal code"

OpenNext Project Introduction

• Open source project announced early due to SST community buzz
• Purpose: easier Next.js deployment to AWS with full feature support
  • Image optimization
  • Edge middleware
  • Server-side rendering
  • Static site generation
  • Incremental Static Revalidation (ISR)
• Many providers don't support ISR, creating appearance of Vercel lock-in
• Community effort to extend Next.js 13 innovations to other platforms

Next.js & Vercel Innovation Process

• Vercel uniquely positioned to innovate due to revenue model
• ISR was new concept when introduced, not supported by infrastructure platforms directly
• Required Next.js + Vercel collaboration to create new paradigms
• Code/documentation made publicly available
• Historical pattern: public efforts, extensive documentation
• Vercel/Next teams actively support other deployment platforms

Platform Innovation Examples

• Original middleware patterns initially flawed (file-based routing)
• Tested on Vercel infra (actually deployed on Cloudflare)
• Multiple runtimes in single Next.js app experimentation
• Architecture rebuilt after learning limitations
• Build output platform now used by multiple frameworks:
  • Solid Start
  • Remix
  • Astro

Competition & Adoption Strategies

• Next.js = current go-to full stack web app option
• Doesn't need multi-platform support for adoption (unlike Remix)
• Remix competes by supporting platforms Next.js doesn't support as well
• Community responsibility to build integrations, not Vercel's obligation

SST Founder Perspective on OpenNext

• Creator: founder of SST (Serverless Stack) - open source AWS deployment tool
• Praised Vercel's work on Next.js
• Good experience working with Vercel team
• Goal: "Vercel experience on their own infra"
• Next.js deployment complexity: serverless functions, CDNs, edge functions, image optimization
• Most frameworks don't support all features unless deployed on Vercel

OpenNext Technical Details

• Addresses complex integrations requiring deep understanding for self-deployment
• Next.js = infrastructure, not just Node.js/JavaScript runtime
• Build output lacks some Vercel features, OpenNext patches gaps
• Consolidates previous community attempts (some closed-source SaaS products like Netlify/Amplify)
• Standardized approach for running Next.js across different platforms

Vercel's Approach & Priorities

• Not actively blocking other platform support
• Self-hosting support lower priority vs. core experience optimization
• Focus: best possible developer experience as full stack web majority holder
• Create groundbreaking web development methods
• Best innovations eventually reach broader community
• Working to improve development without blocking competitors/infrastructure companies

Community Impact Assessment

• Testament to Next.js/Vercel quality that others want to replicate experience
• Sets high bar for full stack infrastructure deployment experience
• High standards drive demand for equivalent experiences across platforms
• Vercel receives criticism despite not actively blocking community efforts