The Vercel Marketplace now has an Experimentation category to allow developers to work with feature flagging and experimentation providers in Vercel projects.

Statsig—a modern feature management, experimentation, and analytics platform—is now available as a first-party integration in this new category, so users can:

• Connect Statsig with your Vercel projects directly from the Vercel Marketplace

• Leverage integrated billing through Vercel

• Sync your Statsig experiments into Edge Config for ultra-low latency

• Manage and roll out features progressively, run A/B tests, and track real-time results

Additionally, you can use the Flags SDK to load experiments and flags from Statsig using the newly released @flags-sdk/statsig provider.

Explore the template or get started with Statsig on the Vercel Marketplace, available to users on all plans.

The Vercel Firewall dashboard now displays enriched IP address data, including the autonomous system (AS) name, AS number (ASN), and geolocation on hover.

This information helps identify the origin of an attack, determine the owner of an IP address, and create targeted custom rules to block malicious traffic.

Learn more about the Vercel Firewall.

Middleware support for the Node.js runtime is now available, providing full Node.js support for authentication, personalization, and more—using familiar APIs.

Middleware continues to be deployed globally on Vercel, regardless of the runtime used. We are first releasing support for Node.js Middleware in Next.js 15.2.

This experimental feature requires the Next.js canary channel. Upgrade to next@canary and enable the nodejs experimental flag in your config to use it:

import type { NextConfig } from "next";

const nextConfig: NextConfig = {
  experimental: {
    nodeMiddleware: true, // Enable Node.js middleware
  },
};

export default nextConfig;

You must also specify the Node.js runtime in your middleware file:

import type { NextRequest } from "next/server";

export function middleware(request: NextRequest) {
  // Your middleware logic here
}

export const config = {
  runtime: "nodejs", // Specify the runtime environment as Node.js
};

Deploy now with Next.js 15.2.