Vercel Edge Config is now generally available

Configuration data is used to control everything from A/B testing and feature flags to advanced rewrites and bespoke request-blocking rules. However, traditional solutions for managing configuration data can be slow, unreliable, and difficult to scale, which can negatively impact the user experience, latency, and overall effectiveness of your website.

Today we’re announcing the general availability of Edge Config, a new solution for managing configuration data in the cloud designed to be ultra-fast, reliable, and scalable, which can help improve your website's performance and efficiency.

import { NextResponse, NextRequest } from "next/server";
import { get } from "@vercel/edge-config";

export async function middleware(request: NextRequest) {
  if (await get("showNewDashboard")) {
    return NextResponse.rewrite(new URL("/new-dashboard", request.url));
  }
}

Edge Config is a globally distributed, ultra-low latency data store for configuration data. It's optimized for fast, inexpensive reads and infrequent writes, making it perfect for managing experimentation and configuration data in modern web applications. Unlike traditional solutions for managing configuration data, Edge Config enables dynamic data storage alongside your functions, which means that your data is actively replicated to all of Vercel's regions before it's requested. This ensures that your data will always be available instantly, no matter where your users are located.

• Make your experimentation near-zero latency: Most lookups return in 0ms, and 99% will return in under 10ms. You get nearly the performance of static configuration with the convenience of updating it from your experimentation tool, from our API, or from our UI.
• Make changes without a new deployment: Changes to Edge Config are pushed to every region within seconds, so that you can take advantage of them without needing to deploy your entire site.
• Integrate with your experimentation tool: Automatically populate the Edge Config connected to your project with the experiment’s evaluation rules. We can then fetch our experiments in our code easily by integrating directly with Statsig—meaning you make changes in the Statsig interface, and you can query the values lightning-fast from Edge Config within Edge Middleware.

We’re continuing to work with integration partners for dynamic personalization at the edge. Split is currently upgrading their integration to include support for Edge Config and we are happy to announce a LaunchDarkly integration will be available at the end of April.

Dynamic routing with Edge Middleware

Combining Vercel Edge Middleware with an ultra-low latency data store opens up numerous other options to control your routing dynamically. For example, you can add blocked IPs and user-agents in Edge Config and make changes without needing to deploy your site. In your middleware you can query the entire configuration list at once then reject those in middleware with minimal overhead.

import { getAll } from "@vercel/edge-config";

export async function middleware(request: Request) {
  const [userAgents, ipAddresses] = await getAll(["userAgents", "ipAddresses"]);

  if (
    userAgents.includes(request.headers.get("user-agent")) ||
    ipAddresses.includes(request.ip)
  ) {
    return new Response("Denied", { status: 403 });
  }
}

Get Started with Edge Config

Edge Config is available to every Vercel account. Hobby users can perform 50,000 reads per month. Pro and Enterprise users can perform 1,000,000 reads per month, with additional usage available for an additional charge.

You can see the number of reads and writes for your Edge Config in your account dashboard.

To get started with Vercel, deploy an example or check out our documentation.

Related reading

Replacing Google Optimize with the Vercel Edge Network

Anthony Shew