TL;DR
Vercel maintains several widely used JavaScript projects, but project ownership does not settle a framework or hosting decision. Evaluate Next.js, Turbopack, SWC, AI SDK, and SWR through their project documentation, registry identities, licenses, and deployment requirements. Next.js documents both Vercel deployment and self-hosting; the right choice depends on the application’s cache, runtime, and operational constraints.
Key takeaways
- Next.js and SWR are MIT-licensed in their current project records; SWC and the Vercel AI SDK package are Apache-2.0. Do not treat the portfolio as one licensing unit.
- Next.js documents self-hosting on Node.js, Docker, or static export. Multi-instance deployments need explicit cache and deployment coordination.
- Turbopack’s supported Next.js integration is documented in the Next.js reference. Test the target project instead of inferring universal build-tool parity.
- The dated npm snapshot and GitHub repository counters below describe package distribution and repository interest, not unique users or quality.
- There is no reproducible benchmark receipt for the removed speed and platform-friction claims.
Package health snapshot
The official package and repository snapshot covers 2026-08-16 through 2026-08-22 for npm distributions and was accessed 2026-08-23 for registry and repository records.
| Project | Dated signal | Latest package tag at access time | License record |
|---|---|---|---|
| Next.js | More than 53 million Next.js package distributions during the dated week; more than 141,000 stars and more than 31,000 forks | 16.3.2 | MIT |
| SWC | More than 41 million @swc/core package distributions during the dated week; more than 34,000 stars and more than 1,500 forks | 1.16.1 | Apache-2.0 |
| Vercel AI SDK | Registry identity only | 7.0.77 | Apache-2.0 |
| SWR | Registry identity only | 2.5.1 | MIT |
The npm values are package distributions, not unique users. Stars and forks are repository counters, not adoption, reliability, or quality scores. These values form a dated snapshot; no universal ranking follows without a defined population and reproducible method.
At-a-glance decision table
| Decision | What the official sources establish | What to verify in the application |
|---|---|---|
| Use Next.js | A React framework with documented Node.js, Docker, static-export, and Vercel deployment paths | Runtime features, cache behavior, image handling, and rollback procedures |
| Use Turbopack | A supported Next.js integration with documented configuration and limitations | Plugins, loaders, source maps, and production build output |
| Use SWC | A separately licensed compiler package used by Next.js and available through its own project | Transform configuration and output for the target codebase |
| Use AI SDK | A package interface for model-provider integrations | Provider behavior, runtime support, cost controls, and error handling |
| Use SWR | A React Hooks library for remote data fetching | Cache ownership, invalidation, server/client boundaries, and testing |
Comparison matrix: project interfaces
Next.js and Turbopack
The Next.js self-hosting guide documents deployment to a Node.js server, Docker, or static export. These documented paths have different operating requirements. A single instance and a coordinated multi-instance deployment have different cache requirements, so self-hosting should be reviewed as an operating model rather than a binary portability label.
The Turbopack reference documents its supported Next.js integration. That is the documented path. It does not prove compatibility with every webpack loader, plugin, monorepo, or deployment workflow.
SWC
SWC has its own project and Apache-2.0 license record. Treat compiler selection as a build-output decision: identify the syntax transforms, module format, source-map requirements, and plugins the repository needs, then compare generated output and tests.
AI SDK and SWR
The AI SDK and SWR registry identities establish package names, versions, descriptions, engines where declared, and licenses. They do not establish a shared roadmap or deployment requirement. Read each package as a separate interface and test it against the application’s runtime and provider choices.
Hosting and pricing boundary
At access time, Vercel’s official plan grid listed Hobby at $0, Pro at $20 per user per month, and Enterprise with custom pricing. Usage is metered separately, so these entry prices do not determine the eventual bill. Pricing was accessed 2026-08-23; recheck immediately before publication and again before a purchasing decision.
Next.js self-hosting is a separately documented path. A hosting comparison should include cache coordination, observability, image delivery, deployment rollback, and staffing rather than treating the plan label as the whole cost model.
Benchmark boundary
The previous guide included speed, percentage, download-correlation, and platform-friction claims without a reproducible benchmark receipt. Those figures are omitted. A useful benchmark must preserve code, package versions, runtime, hardware, warmup, repetitions, configuration, and raw output.
Methodology
This guide uses official Next.js documentation, npm registry records, GitHub repository records, Vercel pricing documentation, and Vercel’s status API. Version and status statements are point-in-time records accessed 2026-08-23; recheck before publication.
Vercel’s public status API reported “All Systems Operational” at access time. That is a point-in-time provider signal, not an uptime guarantee. Next.js self-hosting remains a separate deployment path.
Personnel, salary, financing, and causal ecosystem-outcome claims are not established by the frozen source set and are omitted. Product capabilities are limited to project documentation and registry identities.
FAQ
Does Next.js require Vercel?
No. The official self-hosting guide documents Node.js server, Docker, and static-export paths. Teams running multiple instances must coordinate cache and deployment behavior.
Do the package and repository counters prove market leadership?
No. They are a dated snapshot. A ranking needs a defined population, comparable measures, and a reproducible method.
Are all Vercel-maintained packages under one license?
No. The records used here identify Next.js and SWR as MIT, and SWC and the AI SDK package as Apache-2.0.
Sources
Primary evidence comes from Next.js self-hosting documentation, the Turbopack reference, official npm and GitHub records for the named projects, and Vercel pricing. Source identities, accessed dates, and assertion boundaries are synchronized in the guide packet.