Language
TypeScriptjob-boards.greenhouse.io
Main language for the dashboard and product front end.
UI library
Builds the dashboard interface.
Full-stack framework
Next.jsvercel.com
Framework for vercel.com and the dashboard, split into Multi-Zones.
Why: They split into zones to cut build times and simplify dependencies as the app grew.
Hosting
AWSvercel.com
Cloud where Vercel Functions run, on AWS Lambda.
Database
ClickHousejob-boards.greenhouse.io
Analytical store in the data platform, alongside Tinybird.
Payments
Stripevercel.com
Payments in the dashboard, with its script lazy-loaded only when needed.
Styling and UI kit
Geistvercel.com
In-house design system with colors, typography, React components and the Geist Sans and Mono fonts.
Build and runtime
Turborepovercel.com
Runs the vercel.com monorepo, with remote cache and affected-only tasks.
Turbopackvercel.com
Bundler used for local development of vercel.com.
Data fetching
Streams platform data into the warehouses.
Snowflakejob-boards.greenhouse.io
Data warehouse for the company's data platform.
Backend framework
Rustvercel.com
Powers the Fluid compute core and Turborepo.
Why: Turborepo moved to Rust once Go began to underserve it after merging with Turbopack.
Language of the CDN services, alongside Lua.
Node.jsjob-boards.greenhouse.io
Runtime for back-end services, and one of the languages Fluid compute runs for customers.
Error monitoring
Sentryvercel.com
Error tracking in the dashboard through @sentry/nextjs.
vercel.com started as one large Next.js app serving both marketing pages and the logged-in dashboard. As it grew, build times climbed and small changes triggered full builds.
The team split it into vertical microfrontends with Next.js Multi-Zones inside a Turborepo monorepo, using feature flags to move traffic over gradually. The result was over 40% faster preview builds and local compilation.
Sources:vercel.com
In 2022 the team took the dashboard's Lighthouse score from 51 to 94. Most of the wins were about shipping less JavaScript: importing only the needed parts of Sentry, lazy-loading Stripe and Google Tag Manager scripts, and caching functions that ran hundreds of times per render.
They also leaned on Next.js features such as next/image and inlined font CSS.
Sources:vercel.com
Turborepo was first written in Go, which fit the project early on. As the codebase grew and merged with Turbopack, which is written in Rust, Go started to underserve it.
The team ported it incrementally, running Rust and Go side by side for a while, and finished the migration with Turborepo 1.11.
Sources:vercel.com vercel.com
Vercel Functions run on AWS Lambda, which at first could not stream responses. To add streaming, Vercel built a secure TCP-based protocol from Lambda back to its own infrastructure, with a Rust core as the glue.
That work became Fluid compute, which reuses running instances across requests to cut cold starts and costs for I/O-heavy workloads such as AI apps.
Sources:vercel.com
Found on the homepage with the open Wappalyzer rules (HTML, scripts and headers). It shows what runs in the browser, not the whole backend.
Checked on 2026-10-29. Every tool links to the public source that shows it.
