Our Expertise - Open Source Frameworks
Vercel owns, contributes, and sponsors many of the most popular open source frameworks in web development. Overall, the frameworks Vercel supports represents 89 million weekly downloads, and over 300k GitHub stars.
Original author Guillermo Rauch is also the CEO and Founder of Vercel
Package author Shu Ding employed at Vercel (@shuding on GitHub)
Package author Tobias Koppers employed at Vercel (@sokra on GitHub)
Author Rich Harris employed at Vercel
Author Jared Palmer employed at Vercel
Author shadcn employed at Vercel
React:4 out of 5 core contributors now at Vercel
Gatsby vs Next.js
Netlify decided to back the Gatsby framework, while Vercel has authored and continues to invest in building the Next.js framework. Since February 1st, 2023 after Netlify had acquired the Gatsby framework, the overall usage of Gatsby has declined, while Next.js has experienced continuous growth.
Next.js Infrastructure Support on Vercel
Vercel is the creator and maintainer of Next.js and this gives Vercel a number of advantages:
The Vercel platform supports new Next.js functionality immediately as and when they are released, this also extends to bleeding edge canary releases. Next.js continues to lead innovation on the web, and using Vercel ensures your team can always make use of the latest innovations.
The Next.js and Vercel roadmaps are tightly aligned, and both products benefit from innovation and engineering talent in each.
This is not the case with Netlify, as was recently demonstrated through the release of Next.js v14. Netlify struggled to offer the support their customers were looking with the new version of Next.js (released October 2023), which is documented by the Netlify support forum entry (last post update was February 2024).
With future updates such as partial prerendering around the corner, these situation are only going to increase.
Next.js Code Support
Vercel is uniquely positioned in being able to offer consulting, professional services and support for Next.js. This mitigates risk.
Here are a couple of examples where Vercel customers raised Next.js issues and the Next.js team patched the bugs for the customer. As a Vercel customer you will have access to the Next.js team through you Customer Success Manager.
Customer introduced a new tracing header to aid observability of requests as they pass from your frontend to your backend. This caused an issue with how cache keys are calculated for the fetch cache included in Next.js
Impact:
Reduction in frontend performance potentially affecting conversion rate, increased load/cost on the backend infrastructure as the frontend offloads/caches less backend traffic
Timeline
4/15/2024 12:00 Issue raised in Next.js GitHub
4/15/2024 16:30 Fix merged to canary branch
4/18/2024 Released to Next v14.2.2
Resolution time: 61 hours / 2.5 days
Customer found a bug in Next.js App Router when changing the page architecture as part of the FR site launch. The bug broke navigation between search and product pages.
Impact:
French site launch was fully blocked, as navigation did not work correctly in some cases
Timeline
9/29/2023 21:00 Issue raised in Next.js GitHub
10/2/2023 22:00 Fix merged to canary branch
10/3/2023 03:00 Released to Next v13.5.4
Resolution time: 78 hours / 3.25 days
Vercel vs Netlify Company Ratings
Hosting Performance
Vercel outperforms Netlify across nearly all global regions in the Time to First Byte metric.
| Region | Netlify TTFB | Netlify Total Load | Vercel TTFB | Vercel Total Load |
|---|---|---|---|---|
| us-west-1 | 6ms | 15ms | 32ms | 39ms |
| us-east-1 | 300ms | 313ms | 24ms | 32ms |
| ca-central-1 | 208ms | 241ms | 58ms | 69ms |
| sa-east-1 | 8ms | 20ms | 25ms | 34ms |
| eu-central-1 | 211ms | 220ms | 24ms | 32ms |
| eu-west-2 | 33ms | 64ms | 25ms | 34ms |
| eu-west-3 | 132ms | 161ms | 29ms | 35ms |
| eu-north-1 | 49ms | 98ms | 34ms | 43ms |
| eu-south-1 | 147ms | 179ms | 56ms | 69ms |
| af-south-1 | 670ms | 1031ms | 23ms | 30ms |
| ap-southeast-1 | 9ms | 18ms | 23ms | 34ms |
| ap-northeast-1 | 235ms | 314ms | 24ms | 33ms |
| ap-east-1 | 145ms | 191ms | 28ms | 37ms |
| ap-southeast-2 | 7ms | 16ms | 29ms | 37ms |
| ap-northeast-2 | 148ms | 262ms | 67ms | 78ms |
Case Studies
10% SEO uplift in increased organic traffic after migrating to Vercel
Saves ~21 developer days by leveraging Vercel's build infrastructure
Saw a 2% revenue uplift, worth $100 million annually
Saw a 98% speedup in build times, going from hours to minutes
Cut time spent on infrastructure administration by 50%
Saw 6x faster deployments with Vercel