Vercel announced a billing change titled “Function invocations now billed per unit.” Without the full changelog text, the confirmed takeaway is limited to the billing basis for function invocations. Teams using Vercel Functions should review invocation-heavy APIs, background jobs, webhooks, polling, and AI workflows, but should not assume exact pricing or plan impact without checking the official billing details.
Vercel’s changelog title indicates that Opus 4.8 is now on AI Gateway. The provided source text does not include details such as pricing, model ID, context window, capabilities, or provider-specific options. For developers already using Vercel AI Gateway, the practical next step is to check the official changelog or model list before integrating it into production workflows.
Vercel’s changelog says Sandbox persistence is now GA. Based on the provided material, the confirmed fact is limited to the feature reaching general availability. No model, pricing, API, or implementation details were included, so this should be treated as a product availability update rather than a technical deep dive.
Vercel has extended its microfrontends routing capabilities to support custom alias domains (via vc alias) and Git branch-specific preview domains. Previously, complex multi-project routing rules were often limited to production domains. This update ensures that developers can seamlessly test federated frontend architectures in preview environments before merging.
Vercel announced that Firecrawl has joined the Vercel Marketplace. Based only on the provided title, this appears to be a marketplace listing or ecosystem availability update. The title does not specify features, pricing, setup flow, usage limits, or integration depth, so teams should check the official listing before making adoption decisions.
Based on the title, this Vercel post appears to be a practical Next.js case study. It focuses on building a real-time or near-real-time power outage map and deploying it on Vercel. The source content was not provided, so data sources, map providers, architecture, and performance claims cannot be assumed.