Skip to content

Changelog

Changelog

Follow us on X to hear about the changes first!

Azure AI Provider for the Vercel AI SDK now available

The Vercel AI SDK now supports Azure AI services through a new official provider. To use the provider, install the relevant package:

pnpm install ai @ai-sdk/azure

You can then use the provider with all AI SDK Core methods. For example, here's how you can use it with generateText:

import { azure } from '@ai-sdk/azure';
import { generateText } from 'ai';
const { text } = await generateText({
model: azure('your-deployment-name'),
prompt: 'Write a vegetarian lasagna recipe for 4 people.',
});
Using the Azure provider with the Vercel AI SDK

For more information, please see the documentation.

Cover for HTML element attribution in Speed InsightsCover for HTML element attribution in Speed Insights

HTML element attribution in Speed Insights

Speed Insights now shows which HTML elements are causing low scores, helping you identify performance issues on your site. Supported metrics include:

  • Interaction to Next Paint (INP)
  • Cumulative Layout Shift (CLS)
  • Largest Contentful Paint (LCP)
  • First Input Delay (FID)

This feature is available to all customers using Speed Insights.

Get started with Speed Insights

Cover for CSV Export in Web AnalyticsCover for CSV Export in Web Analytics

CSV Export in Web Analytics

You can now export Web Analytics data as CSV. The aggregated data includes information about unique visitors and page views for the selected data set.

This feature is available to all customers using Web Analytics.

Enable Web Analytics

Cover for Account-owned domains now visible in team-scope domains tabCover for Account-owned domains now visible in team-scope domains tab

Account-owned domains now visible in team-scope domains tab

To give users more clarity on the domains owned across both Teams and accounts, Team Owners can now see account-owned domains in the same tab as their Team domains. This change provides more visibility into the domains you own across your Teams and account.

Learn more about domains on Vercel in the documentation.

Vercel Functions now have faster and fewer cold starts

Vercel's infrastructure now keeps a minimum of one function instance warm for production environments on paid plans. This improves startup times for apps with relatively low traffic.

This builds on our recent improvements to make Vercel Functions start up even faster, by powering them with Rust and adding support for bytecode caching.

Get started with Vercel Functions.

Vercel is now certified under the EU-US Data Privacy Framework (DPF)

We've achieved certification under the DPF to further strengthen our commitment to privacy at Vercel.

  • Commitment to protecting personal data: The DPF provides a reliable mechanism for transferring personal data from the EU, UK, and Switzerland to the U.S. in compliance with applicable privacy laws.
  • Vercel’s privacy practices: You have additional validation to assess Vercel with this internationally recognized certification, along with our ISO 27001 certification.
  • Supporting customer workflows: You have an additional mechanism that may help support their legal and compliance obligations when sending customer personal data to Vercel.

To view our public listing, visit the Data Privacy Framework website.

Improved security with automation testing now available on all plans

You can now more easily run end-to-end tests against deployments protected by Vercel Authentication.

All plans can now create a secret value to bypass authentication, which can then be set as an HTTP header (or query parameter) named x-vercel-protection-bypass.

The automation bypass enables you to protect your project's deployments with Vercel Authentication while still providing access to external services like Checkly and Playwright for your CI/CD e2e testing.

See how to use Protection Bypass for Automation.

Cover for Observe your feature flags with the Vercel DX platformCover for Observe your feature flags with the Vercel DX platform

Observe your feature flags with the Vercel DX platform

The Vercel DX Platform now has a deep understanding of the feature flags you use and create in third-party providers. This beta integration provides better insights into your applications and streamlines your development workflow.

  • Web Analytics integration: Break down page views and custom events by feature flags in Web Analytics, gaining granular insights into user interactions.
  • Enhanced Log visibility: The platform now displays feature flags in logs, making it easier to understand the conditions under which errors occur.
  • reportValue: Reports an evaluated feature flag from the server for runtime logs and Custom Analytics Events (server-side).
  • <FlagValues />: Surfaces a feature flags value on the client for usage in Analytics.

These features have universal compatibility with any feature flag provider you're already using, like LaunchDarkly, Statsig, or Split, or custom setups.

This update lets users on all plans leverage existing feature flag workflows within the Vercel platform and ship safely with more confidence.

Check out the documentation to learn more.

Cover for Protect against OWASP risks with the Vercel FirewallCover for Protect against OWASP risks with the Vercel Firewall

Protect against OWASP risks with the Vercel Firewall

Enterprise customers can now protect against the top OWASP risks.

The Vercel Firewall protects against the OWASP Core Ruleset for Enterprise, which enables Vercel to log, block, or challenge traffic against these rules.

In addition to new custom rules, customers can also ensure they remain protected against the biggest risks for web applications with new OWASP Top 10 protection. For example, this ruleset includes automatic protection against SQL injection attacks.

Contact sales to see a demo and learn more.

Declaring feature flags in code

We’re introducing a new approach for working with feature flags. This approach allows declaring feature flags in code and calling them as functions. Flags implemented using this pattern can automatically respect overrides set by the Vercel Toolbar, and integrate with our Developer Experience Platform features like Web Analytics and Runtime Logs.

import { unstable_flag as flag } from "@vercel/flags/next"
const showSummerSale = flag({
key: "summer-sale",
decide: async () => false
})
Declaring a feature flag

The pattern avoids common pitfalls of client-side feature flag and experimentation usage, such as flashing the wrong experiment, loading spinners, layout shift, and jank. It works with any feature flag provider and even custom setups.

export const showSummerSale = flag<boolean>({
key: 'summer-sale',
async decide() {
return getLaunchDarklyClient().variation(this.key, false);
},
});
Using a feature flag

The pattern further allows for optionally precomputing certain feature flags in Middleware. Middleware can then route visitors to statically generated pages tailored to their specific combination of feature flags and experiments.

This even works when multiple flags are present on the page, which typically suffers from combinatory explosion. Precomputing is great for experimentation on marketing pages as it allows keeping them completely static with ultra-low TTFB, no layout shift, and no flashing of the wrong experiment.

We have implemented this new feature flags design pattern for Next.js in @vercel/flags/next, and we are releasing an implementation for SvelteKit soon.

Check out our documentation to learn more.

The Vercel AI SDK now supports Azure AI services through a new official provider. To use the provider, install the relevant package:

pnpm install ai @ai-sdk/azure

You can then use the provider with all AI SDK Core methods. For example, here's how you can use it with generateText:

import { azure } from '@ai-sdk/azure';
import { generateText } from 'ai';
const { text } = await generateText({
model: azure('your-deployment-name'),
prompt: 'Write a vegetarian lasagna recipe for 4 people.',
});
Using the Azure provider with the Vercel AI SDK

For more information, please see the documentation.

Cover for HTML element attribution in Speed InsightsCover for HTML element attribution in Speed Insights

Speed Insights now shows which HTML elements are causing low scores, helping you identify performance issues on your site. Supported metrics include:

  • Interaction to Next Paint (INP)
  • Cumulative Layout Shift (CLS)
  • Largest Contentful Paint (LCP)
  • First Input Delay (FID)

This feature is available to all customers using Speed Insights.

Get started with Speed Insights

Cover for CSV Export in Web AnalyticsCover for CSV Export in Web Analytics

You can now export Web Analytics data as CSV. The aggregated data includes information about unique visitors and page views for the selected data set.

This feature is available to all customers using Web Analytics.

Enable Web Analytics

Cover for Account-owned domains now visible in team-scope domains tabCover for Account-owned domains now visible in team-scope domains tab

To give users more clarity on the domains owned across both Teams and accounts, Team Owners can now see account-owned domains in the same tab as their Team domains. This change provides more visibility into the domains you own across your Teams and account.

Learn more about domains on Vercel in the documentation.

Vercel's infrastructure now keeps a minimum of one function instance warm for production environments on paid plans. This improves startup times for apps with relatively low traffic.

This builds on our recent improvements to make Vercel Functions start up even faster, by powering them with Rust and adding support for bytecode caching.

Get started with Vercel Functions.

We've achieved certification under the DPF to further strengthen our commitment to privacy at Vercel.

  • Commitment to protecting personal data: The DPF provides a reliable mechanism for transferring personal data from the EU, UK, and Switzerland to the U.S. in compliance with applicable privacy laws.
  • Vercel’s privacy practices: You have additional validation to assess Vercel with this internationally recognized certification, along with our ISO 27001 certification.
  • Supporting customer workflows: You have an additional mechanism that may help support their legal and compliance obligations when sending customer personal data to Vercel.

To view our public listing, visit the Data Privacy Framework website.

You can now more easily run end-to-end tests against deployments protected by Vercel Authentication.

All plans can now create a secret value to bypass authentication, which can then be set as an HTTP header (or query parameter) named x-vercel-protection-bypass.

The automation bypass enables you to protect your project's deployments with Vercel Authentication while still providing access to external services like Checkly and Playwright for your CI/CD e2e testing.

See how to use Protection Bypass for Automation.

Cover for Observe your feature flags with the Vercel DX platformCover for Observe your feature flags with the Vercel DX platform

The Vercel DX Platform now has a deep understanding of the feature flags you use and create in third-party providers. This beta integration provides better insights into your applications and streamlines your development workflow.

  • Web Analytics integration: Break down page views and custom events by feature flags in Web Analytics, gaining granular insights into user interactions.
  • Enhanced Log visibility: The platform now displays feature flags in logs, making it easier to understand the conditions under which errors occur.
  • reportValue: Reports an evaluated feature flag from the server for runtime logs and Custom Analytics Events (server-side).
  • <FlagValues />: Surfaces a feature flags value on the client for usage in Analytics.

These features have universal compatibility with any feature flag provider you're already using, like LaunchDarkly, Statsig, or Split, or custom setups.

This update lets users on all plans leverage existing feature flag workflows within the Vercel platform and ship safely with more confidence.

Check out the documentation to learn more.

Cover for Protect against OWASP risks with the Vercel FirewallCover for Protect against OWASP risks with the Vercel Firewall

Enterprise customers can now protect against the top OWASP risks.

The Vercel Firewall protects against the OWASP Core Ruleset for Enterprise, which enables Vercel to log, block, or challenge traffic against these rules.

In addition to new custom rules, customers can also ensure they remain protected against the biggest risks for web applications with new OWASP Top 10 protection. For example, this ruleset includes automatic protection against SQL injection attacks.

Contact sales to see a demo and learn more.

We’re introducing a new approach for working with feature flags. This approach allows declaring feature flags in code and calling them as functions. Flags implemented using this pattern can automatically respect overrides set by the Vercel Toolbar, and integrate with our Developer Experience Platform features like Web Analytics and Runtime Logs.

import { unstable_flag as flag } from "@vercel/flags/next"
const showSummerSale = flag({
key: "summer-sale",
decide: async () => false
})
Declaring a feature flag

The pattern avoids common pitfalls of client-side feature flag and experimentation usage, such as flashing the wrong experiment, loading spinners, layout shift, and jank. It works with any feature flag provider and even custom setups.

export const showSummerSale = flag<boolean>({
key: 'summer-sale',
async decide() {
return getLaunchDarklyClient().variation(this.key, false);
},
});
Using a feature flag

The pattern further allows for optionally precomputing certain feature flags in Middleware. Middleware can then route visitors to statically generated pages tailored to their specific combination of feature flags and experiments.

This even works when multiple flags are present on the page, which typically suffers from combinatory explosion. Precomputing is great for experimentation on marketing pages as it allows keeping them completely static with ultra-low TTFB, no layout shift, and no flashing of the wrong experiment.

We have implemented this new feature flags design pattern for Next.js in @vercel/flags/next, and we are releasing an implementation for SvelteKit soon.

Check out our documentation to learn more.