Vercel Products
All Vercel Release Notes
- Nov 6, 2025
- Parsed from source:Nov 6, 2025
- Detected by Releasebot:Nov 7, 2025
Skew Protection max age now supports the full deployment lifetime
You can now configure your project's Skew Protection max age to persist for the entire lifetime of your deployments.
Set the value to any duration less than or equal to your project's Deployment Retention policy.
This removes the previous limits of 12 hours on Pro and 7 days on Enterprise.
Learn more about Skew Protection and enable it in your project.
Original source Report a problem - Nov 6, 2025
- Parsed from source:Nov 6, 2025
- Detected by Releasebot:Nov 7, 2025
Moonshot AI's Kimi K2 Thinking models are now available in Vercel AI Gateway
Moonshot AI launches Kimi K2 Thinking and Kimi K2 Thinking Turbo via Vercel AI Gateway with a unified API and no extra accounts. K2 Thinking shines in deep reasoning; Turbo adds low latency. Includes observability, BYOK, retries, and automatic provider routing for reliability.
Moonshot AI Kimi K2 Thinking and AI Gateway
You can now access Moonshot AI's latest and most powerful thinking models, Kimi K2 Thinking and Kimi K2 Thinking Turbo, using Vercel's AI Gateway with no other provider accounts required.
Kimi K2 Thinking is oss and excels at deep reasoning, handling up to 200–300 sequential tool calls, and achieves top results on benchmarks for reasoning and coding. Kimi K2 Thinking Turbo is a high speed version of Kimi K2 Thinking and is best suited for scenarios requiring both deep reasoning and low latency.
AI Gateway lets you call the model with a consistent unified API and just a single string update, track usage and cost, and configure performance optimizations, retries, and failover for higher-than-provider-average uptime.
To use it with the AI SDK, set the model to moonshotai/kimi-k2-thinking or moonshotai/kimi-k2-thinking-turbo :
Using AI Gateway with the AI SDK
Includes built-in observability, Bring Your Own Key support, and intelligent provider routing with automatic retries.
Learn more about AI Gateway, view the AI Gateway model leaderboard or try it in our model playground.
Original source Report a problem - Nov 6, 2025
- Parsed from source:Nov 6, 2025
- Detected by Releasebot:Nov 7, 2025
Edge Config reads and writes now billed per unit
Edge Config pricing shifts to per‑unit billing on the Pro plan, aligning costs with usage. Reads now $0.000003 per read and writes $0.01 per write, replacing the old tiered rates. Per‑unit billing smooths scaling for teams while preserving included credits.
Edge Config Pricing Update
Edge Config Reads and Writes are moving from package-based to per-unit pricing on the Pro plan. You’ll continue paying the same effective rates, but now you’ll be billed per unit to align costs directly with your usage.
The new rates are:
- Edge Config Reads: $0.000003 per read (prev. $3 per 1M reads)
- Edge Config Writes: $0.01 per write (prev. $5 per 500 writes)
Per‑unit billing scales more smoothly across team sizes and usage patterns. It also helps teams on Pro use Edge Config without immediately consuming a large portion of the included monthly usage credit.
Get started or learn more about Edge Config.
Original source Report a problem - Nov 5, 2025
- Parsed from source:Nov 5, 2025
- Detected by Releasebot:Nov 6, 2025
Free Vercel BotID Deep Analysis through January 15
BotID Deep Analysis, Vercel’s advanced bot protection system, will be free for all Pro and Enterprise customers from November 5 to January 15, 2026.
BotID is an invisible CAPTCHA to stop advanced, human-like bots from attacking high-value endpoints like registrations, AI invocations, and checkouts. Deep Analysis, our most advanced solution, uses thousands of telemetry points for real-time client-side checks.
To participate, visit the Bot Management section in the Firewall dashboard and opt in. BotID usage will not be billed during this period. Regular billing resumes on January 16.
Original source Report a problem - Nov 4, 2025
- Parsed from source:Nov 4, 2025
- Detected by Releasebot:Nov 5, 2025
Route build traffic through Static IPs
Use static IPs for builds
You can now choose whether build traffic, such as calls to external APIs or CMS data sources during the build process, routes through your Static IPs.
To enable this, go to your Project Settings Connectivity toggle "Use static IPs for builds."
By default, this setting is disabled. When enabled, both build and function traffic will route through Static IPs and count toward Private Data Transfer usage.
This is available to all teams using Static IPs.
Try it out or learn more here.
Original source Report a problem - Nov 3, 2025
- Parsed from source:Nov 3, 2025
- Detected by Releasebot:Nov 4, 2025
Redirects and Rewrites now available in Observability
Vercel launches enhanced observability for redirects and external rewrites with new metrics views for all plans, including total rewrites and rewrites by hostname. Pro and Enterprise users can upgrade to Observability Plus for latency and path analytics, and drains now support redirects and external rewrites.
Improved observability into redirects and external rewrites
Improved observability into redirects and external rewrites is now available to all Vercel customers.
External rewrites forward requests to APIs or websites outside your Vercel project, effectively allowing Vercel to function as a reverse proxy or standalone CDN.
See external rewrites, connection latency, and errors by hostname or path
Customers on all plans get new views that offer visibility into key rewrite metrics:
- Total external rewrites
- External rewrites by hostnames
Customers on Pro and Enterprise plans can upgrade to Observability Plus to get:
- Connection latency to external host
- Rewrites by source/destination paths
- Routes and paths for redirect location
Drains have also been updated to support the following:
- Redirects
- External Rewrites
- Cached External Rewrites
View external rewrites or learn more about Observability.
Original source Report a problem - Oct 31, 2025
- Parsed from source:Oct 31, 2025
- Detected by Releasebot:Oct 31, 2025
Zero-configuration support for Fastify
Vercel now supports Fastify
Vercel now supports Fastify applications, a web framework highly focused on providing the best developer experience with the least overhead and a powerful plugin architecture, with zero-configuration.
A "Hello World" Fastify app on Vercel
Backends on Vercel use Fluid compute with Active CPU pricing by default. This means your Fastify app will automatically scale up and down based on traffic, and you only pay for what you use.
Deploy Fastify on Vercel or visit the Fastify on Vercel documentation
Original source Report a problem - Oct 31, 2025
- Parsed from source:Oct 31, 2025
- Detected by Releasebot:Oct 31, 2025
Caching details now available in Runtime Logs
New: Runtime Logs details
You can now view more details on how Vercel's CDN globally serves cached content to users as quickly as possible.
In the right-hand panel of the Runtime Logs page, we now list:
- Cache key: A unique identifier for a specific version of a cached page
- Cache tags: Tags associated with the cached data
- Revalidation reason: If a revalidation took place, the reason why the content was being revalidated (time-based, tag-based, or deployment-based)
This is available to all Vercel users at no additional cost. Try it out or learn more about Runtime Logs.
Original source Report a problem - Oct 31, 2025
- Parsed from source:Oct 31, 2025
- Detected by Releasebot:Oct 31, 2025
Microfrontends now generally available
Vercel's microfrontends are generally available, letting teams deploy independent frontends that render as one app while Vercel handles edge routing. Since beta, domains routing, Observability, and onboarding have improved, with nearly 1B routing requests daily and 250+ teams deploying. Pricing starts today with included projects and per-project fees.
Microfrontends support on Vercel is now generally available, enabling you to split large applications into smaller, independently deployable units that render as one cohesive experience for users.
Each team can use their own framework and release cadence, while Vercel handles edge composition and routing for a seamless user experience.
Since the public beta, we've improved domains routing support, added microfrontends to Observability, and simplified onboarding. Vercel is serving nearly 1 billion microfrontends routing requests per day, and over 250 teams, including Cursor, The Weather Company, and A+E Global Media are already deploying microfrontends.
Pricing
- Included: 2 microfrontend projects
- Additional projects: $250 per project per month (available on Pro and Enterprise plans)
- Routing: $2 per million routing requests
Pricing starts today for new projects and on November 30, 2025 for existing ones. If already used, the 3rd project for existing microfrontends users during the beta will continue to be free.
Get started with microfrontends, clone one of our examples, or learn more in our documentation.
Original source Report a problem - Oct 29, 2025
- Parsed from source:Oct 29, 2025
- Detected by Releasebot:Oct 29, 2025
- Modified by Releasebot:Nov 5, 2025
v16.0.1
New release brings broad stability fixes across routing, server rendering, and Windows environments, plus updated docs and dev tool tweaks. Expect smoother prefetch, better image handling, and more reliable cache and middleware behavior.
Core Changes
- fix(static-paths): add depth tracking to parallel route param resolution: #85319
- Fix types of @next/mdx: #82238
- Ensure getServerInsertedHTML skips rendering correctly: #85394
- Fix duplicate .next/types include on Windows: #85400
- Exclude next-js condition from middleware, proxy, and instrumentation: #85321
- remove unstable_forceStale prefetch option & restore prefetch={true} functionality: #85411
- Upgrade React from 2bcbf254-20251020 to 6160773f-20251023 : #85277
- fix(next/image): swap dependencies: #85419
- Handle Origin: null headers: #85402
- Generalize Segment Cache fallback implementation: #84652
- fix: ensure req.query is writable: #81573
- fix: Proxy not picked up on Windows: #85443
- [test] Ensure we can toggle the DevTools menu while status indicators are active: #85456
- Fix crash when suspending in Components using useActionQueue: #85459
Misc Changes
- docs: create-next-app react-compiler and new prompts: #85213
- docs: cache components - introduction: #85196
- docs: use cache feedback: #85169
- docs: stabilize apis in docs: #85219
- docs: revalidateTag immediate expiration in Route Handlers: #85223
- Docs/use cache feedback 2: #85222
- docs: added use cache: remote docs: #85145
- docs: proxy runtime defaults to nodejs: #85204
- chore: cache components feedback: #85241
- docs: add a note that cache components is opt-in near the top: #85245
- Docs/v16 feedback: #85259
- Update command to install babel-plugin-react-compiler as a devDependen...
Credits
Huge thanks to @icyJoseph, @wyattjoh, @devjiwonchoi, @arnabsen, @remcohaszing, @denesbeck, @gaojude, @mhart, @eps1lon, @jesuistuan, @codr, @InfiniteCodeMonkeys, @gnoff, @ztanner, @wbinnssmith, @styfle, @acdlite, @ale-grosselle, and @mischnic for helping!
Original source Report a problem