

Vercel Edge Functions can now be regional or global
Vercel Edge Functions can now be deployed to a specific region.
By default, Edge Functions run in every Vercel region globally. You can now deploy Edge Functions to a specific region, which allows you to place compute closer to your database. This keeps latency low due to the close geographical distance between your Function and your data layer.
Check out the documentation to learn more.


Explore bot traffic data, now in Monitoring Beta
Monitoring now lets you explore traffic data that comes from known and unknown bots. You can group the traffic data by public_ip, user_agent, asn, and bot_name to efficiently debug issues related to traffic coming from real users or bots.
Three new example queries have been added to help you get started:
- Requests by IP Address
- Requests by Bot/Crawler
- Requests by User Agent
Check out the documentation to learn more.


Improved logs available as public beta for Enterprise Teams
Improved logs are now in public beta for all Enterprise accounts. This improvement allows you to search, inspect, and share your organization's runtime logs, either at a project or team level.
The new UI consolidates and streamlines error handling and debugging. Enterprise users can now search runtime logs from all your deployments directly from the Vercel dashboard. Vercel will retain log data for 10 days and continue increasing our retention policy throughout the beta period. For longer log storage, you can use Log Drains.
Read the documentation to learn more.

Improvements and Fixes
With your feedback, we've shipped bug fixes and small feature requests to improve your product experience.
- Vercel CLI: v28.4.5 was released with bug fixes and improved JSON parsing.
- A new system environment variable:
VERCEL_GIT_PREVIOUS_SHAis now available in the Ignored Build Step, allowing scripts to compare changes against theSHAof the last successful deployment for the current project, and branch. - Vercel dashboard navigation: We’ve made it easier to navigate around the dashboard with the Command Menu. You can now search for a specific setting and get linked right to it on the page.
- More granular deployment durations: The total duration time shown in the deployment tab on the Vercel dashboard now includes all 3 steps (building, checking, and assigning domains) and the time stamp next to each step is no longer rounded up.
- Transferring projects: When transferring a project, the current team is always shown in the dropdown, disabled, with a "Current" label at the end. This is to prevent users from trying to transfer a project to the same Hobby team it already is in and also to keep the current team context.
- Improved deployment logs: Logs that start with
npm ERR!are now highlighted in red in deployment logs. - CLI docs revamp: The Vercel CLI docs have moved and now include release phases and plan call-outs.
- Build environment updates:
Node.jsupdated to v16.16.0,npmupdated to v8.11.0,pnpmupdated to v7.12.2.


Easily access Vercel Brand Assets and Guidelines
You can now copy the SVGs for the Vercel logo and wordmark or open the brand guidelines by right clicking on the Vercel logo no matter where you are in the platform. The SVGs are ready for you to use in code or in your favorite design app.


Improved monorepo support with increased Projects per repository
To help your monorepo grow, we have updated the number of projects that you are able to add from a single git repository for both Pro and Enterprise plans.
Pro users can attach up to 60 (increased from 10) projects per single git repository, and the Enterprise limit has more than doubled.
Check out the documentation to learn more.


Commenting on Previews is now in Public Beta
With comments, teams can give collaborative feedback directly on copy, components, interactions, and more right in your Preview Deployments.
PR owners, comment creators, and participants in comment threads can review and collaborate on real UI with comments, screenshots, notifications, all synchronized with Slack.
Check out the documentation to learn more or opt-in to start using comments now.


Add elastic scalability to your backend with Cockroach Labs
Combine CockroachDB Serverless with Vercel Serverless functions in under a minute to build apps faster and scale your entire backend elastically with the new Cockroach Labs integration, now in beta.
Try out the integration.


Vercel Remote Cache SDK is now available
Remote Caching is an advanced feature that build tools like Turborepo use to speed up execution by caching build artifacts and outputs in the cloud. With Remote Caching, artifacts can be shared between team members in both local, and CI environments—ensuring you never need to recompute work that has already been done.
With the release of the Vercel Remote Cache SDK, we're making the Vercel Remote Cache available to everyone. Through Vercel's Remote Caching API, teams can leverage this advanced primitive without worrying about hosting, infrastructure, or maintenance.
In addition to Turborepo, which ships with the Vercel Remote Cache support by default, we're releasing plugins for Nx and Rush.
Check out our examples to get started.


Search domains on the Vercel dashboard
You can now search your list of domains in the Domains tab on the Vercel dashboard to instantly find what you're looking for.
The search bar improves discoverability for teams working with multiple domains that often have long lists of domains to parse through.
Check out the documentation to learn more.


Vercel Edge Functions can now be deployed to a specific region.
By default, Edge Functions run in every Vercel region globally. You can now deploy Edge Functions to a specific region, which allows you to place compute closer to your database. This keeps latency low due to the close geographical distance between your Function and your data layer.
Check out the documentation to learn more.


Monitoring now lets you explore traffic data that comes from known and unknown bots. You can group the traffic data by public_ip, user_agent, asn, and bot_name to efficiently debug issues related to traffic coming from real users or bots.
Three new example queries have been added to help you get started:
- Requests by IP Address
- Requests by Bot/Crawler
- Requests by User Agent
Check out the documentation to learn more.


Improved logs are now in public beta for all Enterprise accounts. This improvement allows you to search, inspect, and share your organization's runtime logs, either at a project or team level.
The new UI consolidates and streamlines error handling and debugging. Enterprise users can now search runtime logs from all your deployments directly from the Vercel dashboard. Vercel will retain log data for 10 days and continue increasing our retention policy throughout the beta period. For longer log storage, you can use Log Drains.
Read the documentation to learn more.

With your feedback, we've shipped bug fixes and small feature requests to improve your product experience.
- Vercel CLI: v28.4.5 was released with bug fixes and improved JSON parsing.
- A new system environment variable:
VERCEL_GIT_PREVIOUS_SHAis now available in the Ignored Build Step, allowing scripts to compare changes against theSHAof the last successful deployment for the current project, and branch. - Vercel dashboard navigation: We’ve made it easier to navigate around the dashboard with the Command Menu. You can now search for a specific setting and get linked right to it on the page.
- More granular deployment durations: The total duration time shown in the deployment tab on the Vercel dashboard now includes all 3 steps (building, checking, and assigning domains) and the time stamp next to each step is no longer rounded up.
- Transferring projects: When transferring a project, the current team is always shown in the dropdown, disabled, with a "Current" label at the end. This is to prevent users from trying to transfer a project to the same Hobby team it already is in and also to keep the current team context.
- Improved deployment logs: Logs that start with
npm ERR!are now highlighted in red in deployment logs. - CLI docs revamp: The Vercel CLI docs have moved and now include release phases and plan call-outs.
- Build environment updates:
Node.jsupdated to v16.16.0,npmupdated to v8.11.0,pnpmupdated to v7.12.2.


To help your monorepo grow, we have updated the number of projects that you are able to add from a single git repository for both Pro and Enterprise plans.
Pro users can attach up to 60 (increased from 10) projects per single git repository, and the Enterprise limit has more than doubled.
Check out the documentation to learn more.


With comments, teams can give collaborative feedback directly on copy, components, interactions, and more right in your Preview Deployments.
PR owners, comment creators, and participants in comment threads can review and collaborate on real UI with comments, screenshots, notifications, all synchronized with Slack.
Check out the documentation to learn more or opt-in to start using comments now.


Combine CockroachDB Serverless with Vercel Serverless functions in under a minute to build apps faster and scale your entire backend elastically with the new Cockroach Labs integration, now in beta.
Try out the integration.


Remote Caching is an advanced feature that build tools like Turborepo use to speed up execution by caching build artifacts and outputs in the cloud. With Remote Caching, artifacts can be shared between team members in both local, and CI environments—ensuring you never need to recompute work that has already been done.
With the release of the Vercel Remote Cache SDK, we're making the Vercel Remote Cache available to everyone. Through Vercel's Remote Caching API, teams can leverage this advanced primitive without worrying about hosting, infrastructure, or maintenance.
In addition to Turborepo, which ships with the Vercel Remote Cache support by default, we're releasing plugins for Nx and Rush.
Check out our examples to get started.


You can now search your list of domains in the Domains tab on the Vercel dashboard to instantly find what you're looking for.
The search bar improves discoverability for teams working with multiple domains that often have long lists of domains to parse through.
Check out the documentation to learn more.