Industry News

Speakeasy specializes in building developer-focused SDKs—to help developers build their products. They adopted v0 to bridge the workflow from design to code, using it to accelerate rapid prototyping and reduce implementation time. Read more Continue reading...

The Vercel Toolbar has a new compact design, making it easier to access the tools you use most. Compact design: The toolbar is now smaller and only runs when you click or tap to activate it or when visiting from a link that contains a comment thread, draft link, or flag override Shortcuts: Your most recently used tools will pin to the top of your menu for easy access Visit with Toolbar: When visiting projects and deployments from the dashboard, you'll see a "Visit" button that gives you the option to load the toolbar upon opening Browser extension controls: Users with the browser extension enabled can control when the toolbar is active or hidden under "Preferences" in the toolbar menu Learn more about the Vercel Toolbar...

You can now see the bounce rate of your visitors in Web Analytics. With bounce rate, you're able to see the percentage of users visiting a single page without navigating any further. When filtering for a route or path, the bounce rate adapts and shows how many users bounced on a specific page. Learn more about filtering in Web Analytics. Read more Continue reading...

We have completed our Self-Assessment Questionnaire Attestation of Compliance (SAQ-D AOC) for Service Providers under PCI DSS v4.0. A copy of our PCI DSS compliance documentation can be obtained through our Trust Center. For additional information about our SAQ-D AOC report or Responsibility Matrix, please contact us. Learn how we support ecommerce customers who require PCI compliance for payment processing. Read more Continue reading...

Audit logs are now generally available for Enterprise customers, and can be integrated with SIEMs for real-time export. Audit logs provide an auditable trail of key events and changes within your Vercel team. With an immutable record, you can track who performed an action, what was done, and when—with access to up to 90 days of historical data. Enterprise customers can also configure a real-time audit log stream to their existing Security Information and Event Management (SIEM) tools, such as Datadog or Splunk. Additionally, logs can be sent to durable object storage solutions like Amazon S3, Google Cloud Storage, or a custom HTTP POST endpoint. For more details, check out the Audit Log documentation or contact your account manager...

Following the Node.js 18 end of life on April 30, 2025, we are deprecating Node.js 18 for Builds and Functions on August 1, 2025. Will my existing deployments be affected? No, existing deployments with Serverless Functions will not be affected. When will I no longer be able to use Node.js 18? On August 1, 2025, Node.js 18 will be disabled in project settings. Existing projects using 18 as the version for Functions will display an error when a new deployment is created. How can I upgrade my Node.js version? You can configure your Node.js version in project settings or through the engines field in package.json. How can I see which of my projects are affected? You can see which of your projects are affected by this deprecation...

Projects using Bun's new text bun.lock lockfile can now be deployed to Vercel with zero configuration. While Vercel already supports Bun's binary bun.lockb lockfile, Bun v1.1.39 introduces a new text-based lock file with bun install --save-text-lockfile. Bun plans to make this the default in v1.2. Learn more about package managers supported by Vercel. Read more Continue reading...

The Flags SDK is a library that gives developers tools to use feature flags in Next.js and SvelteKit applications. The Flags SDK version 3.0 adds: Pages Router support so feature flags can be used in App Router and Pages Router New adapters architecture that allows the SDK to integrate with various data sources and feature flag providers A new identify concept that allows you to establish an evaluation context for your feature flags. With this addition, you can tailor flags and experiments for individual users or groups With this release, the repository is now open source and under the MIT License, providing more transparency and allowing for community contributions and integrations. Check out the new Flags SDK...

The archive option was introduced for CLI deployments hitting rate limits like the limit on the maximum amount of files. Prebuilt deployments commonly use archive uploads as they generate thousands of files at build time. Previously, archive deployments were always compressed into one large file with the only existing --archive option, tgz. Deployments using tgz may hit the file size upload limit. Additionally, uploading one large archive file is slower than uploading multiple file parts. The beta split-tgz format resolves these issues by splitting large archives into smaller parts. split-tgz avoids the static file upload limit and uploads large prebuilt projects up to 30% faster. Example usage: vercel deploy --archive=split-tgz...

Logs now indicate when Vercel Functions reach (or near) their maximum duration or memory allocation for each request. Logs also include quick links to configure function maximum duration, CPU & memory, region, and Node.js Version directly from requests. View your project's logs. Read more Continue reading...

Dates across the dashboard now provide more precision. For the first three days, dates are displayed as relative (e.g. "10m ago") After three days, they switch to absolute values (e.g. "Jan 3") This builds on a recent update where hovering over dates reveals more information, including the exact timestamp. Read more Continue reading...

Python is now supported in the ongoing in-function concurrency public beta. In-function concurrency optimizes functions to handle multiple invocations simultaneously, improving resource efficiency. By reusing active instances instead of creating new ones, it reduces idle compute time and associated costs. In-function concurrency is particularly beneficial for workloads with external API or database calls, such as AI models, where functions often sit idle while waiting for responses. The in-function concurrency public beta is available to Pro and Enterprise customers using Standard or Performance Function CPU, and can be enabled through your dashboard. Real-time tracking of resource savings is available in Observability. Learn more...

This year, we built a Black Friday-Cyber Monday (BFCM) dashboard to celebrate the success of our customers through the busy retail weekend. The dashboard gave a real-time look inside Vercel's infrastructure, showing live metrics for deployments, requests, blocked traffic, and more. Building a data-heavy, real-time dashboard with a good user experience comes with challenges. Let's walk through how we overcame them. Read more Continue reading...

Streaming is now enabled by default for all Vercel Functions using the Python runtime, completing the rollout plan announced last year. Python functions can now send data to the client as it’s generated, rather than waiting for the entire response—particularly beneficial for use cases like AI applications and real-time updates. The VERCEL_FORCE_PYTHON_STREAMING environment variable is no longer necessary, as streaming is now applied automatically in your new deployments. With streaming responses, the runtime log format and frequency have been updated. For more details, visit our documentation or get started with our template. Read more Continue reading...

You can now view your Speed Insights traffic broken down by project in the Usage tab. Learn more about Speed Insights. Read more Continue reading...

The "Contain Types" filter in runtime logs has been replaced by two new filters for better clarity: Resource: Filters which infrastructure resource within the Vercel Edge Network was used to serve the request. Examples include Serverless Functions, Edge Cache, and Edge Middleware Request Type: Filters which framework-defined mechanism or rendering strategy was used by the request. Examples include API routes, Incremental Static Regeneration (ISR), and cron jobs These updates provide more granular insights into how your requests are processed. Both filters are available on all plans starting today. Learn more about how Vercel processes requests. Read more Continue reading...

For ecommerce teams running Salesforce Commerce Cloud, the platform's monolithic design can feel like a double-edged sword. While its out-of-the-box capabilities promise rapid deployments, they often hinder frontend flexibility and innovation. But what if you could unlock a new level of performance—without risking your core business? That’s exactly what a global sportswear brand achieved. Their headless Salesforce migration strategy halved their load times, cut cart abandonment by 28%, and increased mobile conversion rates by 15%. All without a disruptive, big-bang migration. Here’s how they did it and how you can too. Read more Continue reading...

You can now get AI-assisted answers to your questions from the Next.js docs search: Use natural language to ask questions about the docs View recent search queries and continue conversations Easily copy code and markdown output Leave feedback to help us improve the quality of responses Start searching with ⌘K (or Ctrl+K on Windows) menu on nextjs.org/docs. Read more Continue reading...

The x-vercel-ip-postal-code header is now part of Vercel’s geolocation capabilities, providing the postal code associated with the requester’s public IP address. This complements existing headers like x-vercel-ip-country, x-vercel-ip-city, and x-vercel-ip-country-region. The x-vercel-ip-postal-code header is accessible in Vercel Functions, including Edge Middleware. Here's a TypeScript example: Postal codes are also available via the @vercel/functions package: For more information on headers and geolocation, see Vercel’s request header documentation. Read more Continue reading...

The runtime log limits for Vercel Functions have been increased, allowing for significantly larger log entries. These updates replace the previous 4KB-per-line restriction, and they are now live for all projects. The runtime log limits are now: Log line size: Up to 256KB per log line. Log line count: Up to 256 individual log lines per request. Total log size per request: Up to 1MB (sum of all log lines in a single request). Learn more about our logs in our documentation. Read more Continue reading...