The development loop gets faster

The gap between local development and production behavior has long been one of the pain points of serverless and edge-based frontends. Features like CDN caching and serverless functions—now table stakes for dynamic sites—historically could not be exercised on a developer's own machine. That limitation shaped the two halves of Vercel's latest release: an overhauled local workflow and a redesigned edge network that together promise page loads up to 6x faster.

Real-time edits with Next.js

At the center of the new developer experience is Fast Refresh support in Next.js. The technology, originally developed by Facebook, lets changes to complex UI components reflect almost instantly—Vercel puts the improvement at 10x to 20x versus other React frameworks. Next.js is the first open-source framework to ship Fast Refresh.

The local environment now mirrors the capabilities of the production edge network. Developers using incremental static regeneration or API routes work with the same behavior they will see after deployment, without needing extra tooling to bridge the gap.

Vercel CLI 19 for other frameworks

Not every framework has the integrated support that Next.js enjoys. For those cases, the Vercel CLI (via vercel dev) replicates the platform locally. With the new version 19, developers using tools like Gatsby or Vue.js can create an api/my-function.js file and test it at http://localhost:3000/api/endpoint without any additional setup.

  • Faster startup. vc dev launches the underlying framework dev command sooner.
  • Better stacktraces. Errors in serverless functions point to the exact location of the problem.
  • Improved memory usage. Extended sessions stay lean and stable.
  • Seamless env sync. Cloud-based development environment variables are pulled automatically.
  • Speedy invocations. Node.js functions execute noticeably faster in local runs.

The edge network underneath

Vercel handles a reported 4.5+ billion requests per week—and all of it moved onto the rebuilt infrastructure mid-traffic. Two structural changes define the new architecture.

Owned Anycast IP ranges

A typical IP address anchors a device to one location. Anycast addresses like 8.8.8.8 (Google Public DNS) instead resolve to the nearest healthy node. Vercel now owns its own pool of such IPs. Deployments get A or CNAME records selected from plan- and project-specific pools of optimized Anycast addresses.

  • Faster page loads. Gains of up to 6x depending on location, ISP, and DNS resolver.
  • Optimal routing. Traffic is directed at the most fundamental layer of internet infrastructure.
  • Apex support. Bare domains work with plain A records, sidestepping ALIAS or ANAME requirements.
  • Global redundancy. Downtime in any region triggers automatic re-routing.
  • Better interoperability. No efficiency loss when using Route 53, Cloudflare, CrowdStrike, or other DNS providers in front.

Resilience under load and attack

With an increasing number of sites on the platform, Vercel upgraded its network to auto-scale through high traffic and unpredictable spikes. The same growth raised the profile of malicious traffic, so DDoS mitigation also received substantial improvements—all delivered, the company notes, with zero disruption to visitor or developer traffic. The result is that platform-level concerns such as scaling, routing and attack absorption are handled without any configuration from customers.