# Vercel Vercel is a software infrastructure and deployment platform offering features such as serverless functions, deployment environments, global delivery, and web application firewall services. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Mem0 joins the Vercel Marketplace DevFeed: [Mem0 joins the Vercel Marketplace]() Original publisher: [Read original article]() Author: Tony Pan Published: 2026-09-16T17:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Artificial Intelligence](), [App](), [context](), [API keys](), [Command-line interface](), [Environment Variables]() Tags: [ai](), [ai-agents](), [app](), [billing](), [cli](), [context](), [environment-variables](), [free](), [giving](), [install](), [integration](), [vercel](), [volume]() ### AI overview Mem0 is now a native integration on the Vercel Marketplace, providing long-term memory for AI agents and apps across sessions. The integration includes billing through Vercel, automatic provisioning of a scoped Mem0 project and API key, and environment-variable configuration. Mem0 offers a free plan with usage limits and a $20-per-month plan for higher volume. ### Source excerpt Mem0 is now available as a native integration on the Vercel Marketplace, giving your AI agents and apps long-term memory. Mem0 remembers user preferences, facts, and context across sessions, so your app stops starting from scratch. Install from the Marketplace with integrated billing on your Vercel invoice, no separate account or key management. A scoped Mem0 project and API key are provisioned automatically and added to your project as environment variables, including MEM0_API_KEY. Mem0 offers a free plan with usage limits and a $20 per month plan for higher volume. To see it end to end, deploy the eve Memory Agent template, an eve agent with long-term memory powered by Mem0. Get started with Mem0 on the Vercel Marketplace or through the Vercel CLI, available to customers on all plans. Read more ## Auth0 launches v0 integration for production application authentication DevFeed: [Auth0 launches v0 integration for production application authentication]() Original publisher: [Read original article]() Author: Juan Cruz Martinez Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [Auth0 Blog]() Topics: [Auth0](), [Authentication](), [app builder](), [Access Control](), [Artificial Intelligence](), [Vercel](), [MFA]() Tags: [access-control](), [ai](), [app-builder](), [auth0](), [authentication](), [mfa](), [sdk](), [vercel]() ### AI overview Auth0 is launching an integration with v0 that lets users configure authentication directly from prompts, including login, protected routes, B2B use cases, enterprise identity providers, and MFA. The integration can create Auth0 applications, configure connections, and wire the SDK into generated code. ### Source excerpt Stop relying on generic login forms. Use the new Auth0 v0 integration on the Vercel identity platform to build secure, production-ready AI app authentication. ## How Delphi ships 100 times a day with its Python backend on Vercel DevFeed: [How Delphi ships 100 times a day with its Python backend on Vercel]() Original publisher: [Read original article]() Author: Kevin Sundstrom Published: 2026-09-15T04:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [Python](), [Vercel](), [Back end](), [feature flags](), [Amazon Web Services](), [Docker](), [airflow]() Tags: [aws](), [backend](), [docker](), [feature-flags](), [python](), [vercel](), [workflow](), [workflows]() ### AI overview A Vercel case study describes how Delphi rebuilt its Python backend on Vercel after previously using AWS, ECS, Docker Desktop, and local databases. The move gave the team a shared deployment workflow, faster onboarding, and more than 100 production deploys per day, while Vercel Workflows and Queues support long-running work and background jobs. ### Source excerpt Delphi on Vercel 10 engineers with no dedicated infrastructure role Everyone ships code, including product and design 100+ production deploys a day behind feature flags Delphi builds digital minds. They capture what someone has written, recorded, and taught, so anyone can tap that expertise on demand. Delphi is "a destination where you can find and interact with interesting minds," says founding engineer Spencer Schoeben. Nobody has built a digital mind network before, so Delphi figures out what to build by shipping features and watching how people use them. That only works if the product is fast to change. "If we are going to win, we need to have an excellent developer and agentic experience," Spencer says. "Otherwise, we could not adapt to how fast our user's demands change." Delphi's frontend had run on Vercel since day one. "The frontend has always been easy," Spencer says, "but the backend was a nightmare." Six months ago, the team rebuilt its Python backend on Vercel as well. Today the whole team ships to production 100+ times a day. Building a Python backend that's easy to work onThe backend slowed every change Delphi's backend previously ran on AWS, with ECS, Docker Desktop, and local databases. In the earliest days, the setup worked because the team was small and much of the context lived in people's heads. As Delphi grew, that made onboarding slower than the team wanted: getting a new engineer to their first deploy took a full day of environment setup. Delphi could have fixed that without leaving AWS. But fixing it properly would have meant designing and owning the infrastructure themselves, and the team didn't want to own infrastructure at all. "That is not our current goal as a company," Spencer says. After moving the backend to Vercel, new engineers could get to production much faster, with the same deploy workflow the rest of the team used every day. Workflows and Queues made the move possible When Delphi was founded, Vercel Workflows and Vercel Queues ## Vercel Sandbox now provides 64 GB of storage DevFeed: [Vercel Sandbox now provides 64 GB of storage]() Original publisher: [Read original article]() Author: Luke Phillips-Sheard Published: 2026-09-11T06:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel]() Tags: [agent](), [dependencies](), [documentation](), [sandbox](), [sandboxes](), [storage](), [vercel]() ### AI overview Vercel Sandbox storage has increased from 32 GB to 64 GB for all sandboxes, including those created from managed or custom images and those using the deprecated runtime property. ### Source excerpt Every Vercel Sandbox now includes 64 GB of storage, up from 32 GB. This includes sandboxes created from a Vercel Managed Image or custom image, as well as those configured with the deprecated runtime property. The additional space provides more room for large repositories, dependencies, build artifacts, data workloads that spill to disk, and storage-intensive agent tasks. Learn more about Sandbox images in the documentation. Read more ## Control who can manage connectors in Vercel Connect DevFeed: [Control who can manage connectors in Vercel Connect]() Original publisher: [Read original article]() Author: Allen Zhou Published: 2026-09-11T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Authorization]() Tags: [agents](), [connectors](), [documentation](), [enterprise](), [vercel]() ### AI overview Vercel Connect now lets Pro and Enterprise teams restrict connector management to Owners and users with the Connector Manager extended permission. Connectors provide applications and agents with access to external services through team-managed credentials. ### Source excerpt Pro and Enterprise teams can now control who can create and manage Vercel Connect connectors. Connectors let applications and agents access external services using credentials managed by your team. Owners can enable this restriction under Connector Permissions in Team Settings. Once enabled, only people with the Owner role or Connector Manager extended permission can create or manage connectors. Browse all connectors, or learn more in the Vercel Connect documentation. Read more ## FastAPI frontends and static files served from the CDN DevFeed: [FastAPI frontends and static files served from the CDN]() Original publisher: [Read original article]() Author: Daniel Park Published: 2026-09-10T17:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [FastAPI](), [Vercel](), [Front end](), [mount]() Tags: [cdn](), [frontend](), [mount](), [tool](), [vercel]() ### AI overview Vercel now promotes FastAPI frontends and static files served through app.frontend() or StaticFiles to the Vercel CDN at build time, allowing matching requests to bypass Vercel Functions. Route precedence is preserved, while dependency-protected frontends and middleware-protected static files remain on the function unless configured otherwise. ### Source excerpt FastAPI frontends and static files, served with app.frontend() or StaticFiles, are now promoted to the Vercel CDN at build time. Requests for those paths are served directly from the CDN, without invoking your Vercel Function. FastAPI evaluates routes in declaration order. A route declared before a StaticFiles mount takes priority over any CDN file at that path. This precedence is preserved. Promoted source directories remain in the function bundle so the app can read from them at runtime. To exclude them and serve only from the CDN, set tool.vercel.fastapi.static.exclude = true in pyproject.toml. Frontends guarded by dependencies are kept on the function as the CDN cannot run dependency checks. Similarly, static files which sit behind middleware are also kept on the function. To override this and always promote to CDN, set tool.vercel.fastapi.static.cdn = true. To opt out of the CDN entirely, set it to false instead. For more information see the Vercel FastAPI documentation. Read more ## How we cut CDN metadata lookup latency by 91% DevFeed: [How we cut CDN metadata lookup latency by 91%]() Original publisher: [Read original article]() Author: Luba Kravchenko Published: 2026-09-10T00:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [Latency](), [Vercel](), [Caching](), [Routing (disambiguation)](), [API](), [React Native]() Tags: [api](), [cache](), [cdn](), [deployment](), [latency](), [routing](), [vercel]() ### AI overview Vercel describes how it reduced P99 CDN metadata lookup latency by 91%. The team replaced per-path metadata fetching with bounded shards that group metadata for many paths, improving cache reuse across routing lookups while controlling data-fetching costs. The article also explains how framework routing rules, Build Output API outputs, Bloom filters, and exact metadata lookups work together to select the correct response. ### Source excerpt Every request to Vercel passes through our CDN, which executes on average over 80 million routing instructions per second. Part of that work is looking up metadata to determine which paths exist and how to serve them. When that metadata isn't cached, the CDN has to fetch it before it can serve the response. We used to fetch and cache metadata one path at a time, retrieving only what each lookup needed. That seemed efficient at the time, but large deployments can contain hundreds of thousands of paths, each with its own cache entry. Every new deployment introduced fresh metadata, making cache misses a recurring cost for large sites that deployed frequently. Fetching more metadata at once made these lookups faster. By grouping paths together, each fetch could populate the cache for many subsequent lookups. But fetching too much introduced its own costs. Through production experiments, we found a balance that cut P99 metadata lookup latency by 91% and made deployments faster along the way. How the CDN finds the right route The path in a request doesn't always match the path of the content or function that serves it. Framework routing rules connect the two. A request for /blog/hello-world, for example, might resolve to the dynamic route /blog/[slug]. A request for that page's React Server Component payload might resolve to /blog/[slug].rsc. As the CDN applies these rules, it may need to check several target paths to find the right response. The framework describes those routes during a build. With framework-defined infrastructure, application code declares which outputs are static, which need Functions, and which responses can be cached or regenerated. Frameworks translate that intent into Build Output API outputs, and Vercel generates the routing metadata the CDN reads. At request time, the CDN needs to determine which target paths exist and retrieve their metadata. The Bloom filters we added to global routing rule out paths that definitely don't exist. Remaining paths ## Vercel Sandbox is now available in all regions DevFeed: [Vercel Sandbox is now available in all regions]() Original publisher: [Read original article]() Author: Rob Herley Published: 2026-09-10T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [cloud-infrastructure](), [Latency](), [Command-line interface](), [SDKs](), [configuration]() Tags: [cli](), [compute](), [configuration](), [cpu](), [enterprise](), [latency](), [memory](), [sdk](), [support](), [update](), [vercel]() ### AI overview Vercel Sandbox is now available across all 20 Vercel compute regions, expanding from four. Users can select primary and failover regions, helping reduce latency and meet data residency requirements. Region selection is available on every plan, while Pro and Enterprise teams can configure failover regions. ### Source excerpt Vercel Sandbox can now run in all 20 Vercel compute regions, up from four. Running sandboxes closer to the databases, storage, and other services they access reduces latency. Teams can also keep sandbox workloads in approved regions to support data residency and regional processing requirements. iad1 remains the default region. Region selection is available on every plan. Pro and Enterprise teams can also configure failover regions. If Vercel can't create a sandbox in the primary region, it tries each configured failover region in order. Teams with data residency requirements can limit primary and failover regions to approved geographies. Set a default region for new sandboxes from your project's Settings > Sandboxes. With the SDK: With the CLI: A region passed at creation overrides the project default. Existing sandboxes remain in the regions where they were created. Active CPU and Provisioned Memory rates vary by region. See Sandbox pricing. If you use the Sandbox SDK or CLI, update it to the latest version before selecting one of the newly supported regions. Learn about region selection, failover, and CLI configuration in the Sandbox regions documentation. Read more ## Protect production deployments for free on every plan DevFeed: [Protect production deployments for free on every plan]() Original publisher: [Read original article]() Author: Jas Garcha Published: 2026-09-09T06:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Deployment](), [Authentication](), [Security](), [dashboards](), [Low-Code / Internal Tools]() Tags: [authentication](), [dashboards](), [deployment](), [internal-tools](), [password](), [security](), [vercel]() ### AI overview Vercel now lets every plan protect all project deployments, including production, with Vercel Authentication at no extra cost. The update also makes deployment protection exceptions free and lets Pro teams enable password protection per project. ### Source excerpt Vercel Authentication can now protect all deployments in a project, including production, at no additional cost on every plan. Previously, protecting production domains required the $150-per-month Advanced Deployment Protection add-on. When enabled, visitors must sign in with a Vercel account that has access to the project. This makes it useful for internal tools, private dashboards, and sites that aren't yet ready to launch. From your project, open Security in the sidebar, select Deployment Protection, then choose All Deployments from the dropdown. You can also make this the team default, so every new project starts with Vercel Authentication enabled for all deployments. With this change: Deployment Protection Exceptions are now free on every plan. Use an exception to make a specific preview domain public while keeping the rest of the project protected. Pro teams can now enable Password Protection for individual projects instead of purchasing it for the entire team. Learn more in the Deployment Protection documentation. Read more ## Persistent memory for eve agents DevFeed: [Persistent memory for eve agents]() Original publisher: [Read original article]() Author: Andrew Barba Published: 2026-09-09T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [cloud-infrastructure]() Tags: [agents](), [memory](), [storage](), [tools](), [vercel]() ### AI overview eve agents can now retain context across sessions through persistent memory organized into named slots. Each slot defines a memory provider and sharing scope, with support for per-user memory, automatic or tool-driven updates, Vercel Blob storage, several external providers, and custom providers. ### Source excerpt eve agents can now retain context across sessions and use it in future conversations. Persistent memory is organized into slots. You can define named slots in files under agent/memory/. Each slot specifies a provider, which stores and retrieves the memory, and a scope, which determines who or what shares it. For example, you can keep separate memory for each authenticated user. Before each turn, eve retrieves relevant memory and adds it to the model's context. Depending on the provider, memory can be updated automatically after a turn, through tools the agent uses, or through both methods. To add eve's built-in file memory provider, run: The command creates a file memory slot scoped to each authenticated caller: For agents deployed on Vercel, file memory uses a private Vercel Blob store so saved memories persist across restarts and deployments. Other supported memory providers include Supermemory, Upstash AgentKit, and Kybernesis Arcana. You can also connect another storage system or memory service by building a custom provider. Read the memory documentation to choose a provider and get started. Read more ## You can now read and search changelogs from the CLI DevFeed: [You can now read and search changelogs from the CLI]() Original publisher: [Read original article]() Author: Melkey Moksyakov Published: 2026-09-09T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Command-line interface](), [changelog](), [Vercel](), [Terminal](), [AI-assisted coding](), [JSON](), [Markdown]() Tags: [agents](), [changelog](), [cli](), [coding-agents](), [content](), [features](), [json](), [markdown](), [products](), [search](), [terminal](), [update](), [vercel]() ### AI overview Vercel introduces the vercel changelog command for reading and searching Vercel changelog entries from a terminal. It supports result limits, keyword searches, full Markdown content, and JSON output for scripts and coding agents. The feature requires Vercel CLI 59.6.0 or later. ### Source excerpt You and your agents can now read and search the Vercel changelog feed from your terminal using vercel changelog. Coding agents can use this command to discover new Vercel products and features, find updates relevant to your project, and read full announcements to inform their recommendations. vercel changelog returns the latest five changelogs with full Markdown content. You can also set the number of results, search all changelogs using a keyword, and access JSON output for scripts and agents. Update the Vercel CLI to version 59.6.0 or later and run vercel changelog to get started. See vercel changelog --help for all available options. Read more ## Introducing Flat Rate CDN DevFeed: [Introducing Flat Rate CDN]() Original publisher: [Read original article]() Author: Eric Dodds Published: 2026-09-08T04:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [Vercel](), [networking](), [Internet]() Tags: [billing](), [network](), [performance](), [pricing](), [vercel]() ### AI overview Vercel introduces Flat Rate CDN for Pro teams, replacing usage-based CDN billing with predictable monthly pricing, built-in protection against traffic spikes, and service tiers for different traffic profiles. The plan covers CDN requests and data transfer without surprise overages while retaining access to Vercel's premium network and routing performance. ### Source excerpt Over the past year, we have improved Vercel's Pro pricing to better reflect how teams build, with expanded user roles, flexible credits, access to enterprise features, and more. But one area our customers continued to give us feedback on was CDN pricing. CDN costs should be predictable, but viral launches, traffic bursts, or misconfigured routes sometimes turned an otherwise normal month into an unexpected bill. For teams building on Vercel, that uncertainty made growth feel like a problem at exactly the moment it should feel exciting. Today, we are introducing Flat Rate CDN for Pro teams: a new way to pay for CDN usage with a predictable monthly bill, built-in spike protection, and service tiers designed for different traffic profiles. What is Flat Rate CDN? Flat Rate CDN is an alternative to usage-based CDN billing that provides you with a predictable monthly bill. The model is designed around a simple idea: teams should be able to choose the CDN capacity that corresponds to their typical usage profile, pay a known amount monthly, and avoid surprise overages from temporary spikes. Flat Rate CDN has several advantages over usage-based billing: Fixed monthly price: Pay a fixed amount for Vercel CDN each month. Covers traffic spikes: CDN Requests, Fast Data Transfer, and other resources are no longer billed directly, so spikes don't result in surprise bills. No overages: Your bill will never increase because of temporary usage spikes. Importantly, predictable pricing does not mean lower-quality bandwidth. Every request still runs on Vercel's premium network, including private fiber that routes around congestion on the public internet, which can improve performance by up to 60%. Comparable routing is often sold as a premium add-on, but Vercel includes it by default for Pro teams, and performance isn't degraded during traffic spikes. How it works All new Pro teams have Flat Rate CDN enabled by default, and existing Pro teams can opt in. Usage is tracked at the team lev ## GPT 6 Astra now available on Vercel AI Gateway DevFeed: [GPT 6 Astra now available on Vercel AI Gateway]() Original publisher: [Read original article]() Author: Jerilyn Zheng Published: 2026-09-04T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Artificial Intelligence](), [OpenAI](), [Vercel](), [AI-assisted coding](), [codex]() Tags: [agentic](), [ai](), [ai-gateway](), [coding](), [coding-agents](), [gpt](), [model](), [openai](), [playground](), [vercel]() ### AI overview Vercel AI Gateway now offers OpenAI's GPT 6 Astra, a model designed for long-running agentic work. It can navigate software, analyze data, run simulations, and build and test websites while adapting to changing requirements. ### Source excerpt GPT 6 Astra from OpenAI is now available on AI Gateway. GPT 6 Astra is designed for long-running agentic work. It can navigate software, analyze data, run simulations, and build and test websites while adapting to new requirements, filling in routine gaps, and continuing other work when it needs clarification. Use the model ID openai/gpt-6-astra: To use GPT 6 Astra with a coding agent, run vercel ai-gateway coding-agents setup, then select openai/gpt-6-astra. See the setup guides for Codex and Hermes for specific instructions. Try GPT 6 Astra in the model playground. Read more ## Cursor Cloud Agents can now run in Vercel Sandbox DevFeed: [Cursor Cloud Agents can now run in Vercel Sandbox]() Original publisher: [Read original article]() Author: Allen Zhou Published: 2026-09-03T15:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [cursor](), [Vercel](), [Agent Harness](), [Firecracker]() Tags: [agents](), [apis](), [architecture](), [cursor](), [enterprise](), [firecracker](), [guide](), [sandbox](), [scale](), [vercel](), [virtual-machines](), [workflows]() ### AI overview Cursor Cloud Agents can run in Vercel Sandbox, using isolated Firecracker microVMs as their execution environment. The architecture combines Cursor's agent harness and inference loop with Vercel Functions and Workflows for durable request handling, worker provisioning, monitoring, retries, cleanup, and short-lived user-scoped credentials. ### Source excerpt Cursor Cloud Agents can now run in Vercel Sandbox instead of Cursor's hosted machines. Cursor manages the agent harness and inference loop. Its Self-Hosted Machines APIs let you supply the execution environment where agents clone repositories, edit files, and run commands and tests. Self-Hosted Machines requires a Cursor Enterprise plan. Vercel Sandbox provides that execution environment as an isolated Firecracker microVM for each agent request. Vercel Functions and Vercel Workflows form a durable control plane that claims queued agent requests, provisions workers, monitors sessions, and cleans up automatically. With this architecture, you get: A scale-to-zero worker pool without long-lived virtual machines A dedicated, isolated Sandbox for every agent request Durable retries when a worker or session fails Short-lived, user-scoped credentials inside each Sandbox Follow the step-by-step guide to deploy the reference implementation to your own Vercel account, or learn more in the Vercel Sandbox documentation. Read more ## Free domain with Pro offer now includes .app and .dev DevFeed: [Free domain with Pro offer now includes .app and .dev]() Original publisher: [Read original article]() Author: z0oks Published: 2026-09-02T07:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel]() Tags: [free](), [vercel]() ### AI overview Vercel now includes .app and .dev domains in its free one-year domain offer for Pro teams, expanding the eligible TLDs to eight. The offer is limited to one domain per team, excludes premium domains, and renews automatically at the regular price after the first year. ### Source excerpt We recently announced that all Pro teams can claim a free domain for one year. That offer now includes .app and .dev, bringing the eligible TLDs to eight: .app .dev .online .site .space .store .tech .website The offer still covers one domain per team, and premium domains are not eligible. After the first year, your domain will renew automatically at the regular price shown at checkout when you claim it. Claim yours at vercel.com/domains, and see the free domain FAQ for full terms. Read more ## GLM-5.3 is 50% off through DigitalOcean on AI Gateway DevFeed: [GLM-5.3 is 50% off through DigitalOcean on AI Gateway]() Original publisher: [Read original article]() Author: Jerilyn Zheng Published: 2026-09-02T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Digital Ocean](), [Language models](), [long-context](), [AI-assisted coding](), [Claude Code](), [codex](), [cursor]() Tags: [ai-gateway](), [claude-code](), [codex](), [coding-agents](), [context-window](), [cursor](), [digitalocean](), [language-models](), [model](), [tokens](), [vercel]() ### AI overview Vercel announces a 50% discount on GLM-5.3 through DigitalOcean on AI Gateway until September 8. The article explains the temporary promo model name, standard provider routing, model limits, spend tracking, and setup for coding agents. ### Source excerpt GLM-5.3 is 50% off on AI Gateway through Tuesday, September 8, in partnership with DigitalOcean. How to use the model during the offer period Using the promo name (zai/glm-5.3-promo-50) gets the discounted rate. It routes only to DigitalOcean, with no fallback to another provider, and it stops serving when the offer ends. Using the standard name (i.e., zai/glm-5.3) with provider options to sort DigitalOcean as the preferred provider keeps working after September 8 and routes across every provider that serves the model, at their usual rates. Because the promo name goes away when the offer ends, treat it as something you switch on for the window rather than hardcode. To keep the standard name in your code instead, pin the provider with order: ['digitalocean'] under providerOptions.gateway, which prefers DigitalOcean and falls back to the others if it cannot serve the request. GLM-5.3 takes text input, with a 1M token context window and a maximum output of 128K tokens. Discounted requests appear in your spend dashboard and carry a trace like any other request. Try GLM-5.3 in the model playground. To use it in a coding agent, see the coding agents guide, then run vercel ai-gateway coding-agents setup to connect agents like Claude Code, Codex, OpenCode, Cursor, Pi, and more and select zai/glm-5.3-promo-50 inside the agent. You can view all language models available on AI Gateway. Read more ## Compute that takes any shape DevFeed: [Compute that takes any shape]() Original publisher: [Read original article]() Author: Luke Phillips-Sheard Published: 2026-09-01T07:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [Cloud](), [Provisioning](), [cloud-infrastructure](), [Vercel](), [cpu](), [IO](), [DRIVE]() Tags: [agent](), [cloud](), [code](), [compute](), [cpu](), [image](), [infrastructure](), [io](), [memory](), [pricing](), [real-time](), [sandbox](), [storage](), [vercel]() ### AI overview Vercel presents Fluid as a unified compute system that assembles machines for different workloads, changes configuration dynamically, and absorbs burst capacity in real time. It supports builds, sandboxes, and functions, using isolated virtual machines, custom images, and separate storage connections. ### Source excerpt Workloads differ in how long they run, how much memory they take, and how much of the environment they control. That previously meant a different compute primitive for each job, so product iterations required provisioning infrastructure, not just working on a feature. We built Vercel so that none of this has to be your problem. The compute layer is a single system with a simple job. Take any workload, assemble the machine it needs, swap configuration on the fly, and absorb burst capacity in real time. We call this Fluid. Builds ran on it first, then sandboxes, and now functions. If you've shipped on Vercel, you've been on Fluid without knowing it. Fluid compute now runs over 15 million builds a day, 25 million sandboxes a week, and a trillion requests a month. A history of compute Changing a machine used to mean changing it by hand. You went down to the computer store, bought a hard drive or a stick of RAM, and swapped it in yourself. Then you could rent bare metal when you needed it, and use it to serve a website, host a database, or send email. Then the cloud let you request a machine in any configuration you wanted, choose its operating system, use it, and throw it away when you were done. For agents, even the cloud is too slow. A standard VM can't provision fast enough to keep up with how they work, but this is where Fluid excels. How a workload runs on Fluid When a workload comes in, Fluid assembles a machine to fit its shape. If an agent needs to run code, Hive provides an isolated VM, usually one already warm, so it's ready instantly. Your own image boots on top as the environment. A Drive connects, and your files are right where you left them, because storage was never tied to the machine. Each workload needs something different. A build is compute-bound, so it wants a beefy machine, heavy on CPU and memory. A function is IO-bound, loading specific code to run the instant a request lands, usually on a small VM. A sandbox is flexibility-bound, taking whatever ## AWS PrivateLink is now available on Pro and Enterprise DevFeed: [AWS PrivateLink is now available on Pro and Enterprise]() Original publisher: [Read original article]() Author: Bryan Mishkin Published: 2026-09-01T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Network](), [Amazon Web Services](), [AWS IAM](), [Amazon S3](), [MongoDB]() Tags: [aws](), [enterprise](), [iam](), [mongodb](), [networking](), [pricing](), [s3](), [vercel]() ### AI overview Vercel has made AWS PrivateLink available to Pro and Enterprise teams through Advanced Networking. Vercel Functions and builds can privately access AWS-hosted databases, SaaS services, internal services behind an AWS Network Load Balancer, and S3 or DynamoDB without using the public internet. ### Source excerpt AWS PrivateLink is now available for Pro and Enterprise teams as part of Advanced Networking. It allows Vercel Functions and builds to connect to AWS-hosted services without sending traffic over the public internet. Use it to reach AWS-hosted databases such as RDS, Aurora, and Neon; SaaS services such as Snowflake and MongoDB Atlas; internal services behind an AWS Network Load Balancer; and S3 or DynamoDB through gateway endpoints. To configure PrivateLink, open your project's Networking settings and enable Advanced Networking. Select New Connection, then enter the service name and region. The service must accept connections from all AWS principals or allowlist the IAM role Vercel provides for your team. Vercel creates the connection and provides a stable hostname. Use this hostname from your Functions and builds to reach the service privately. Pricing: The first AWS PrivateLink connection is included with Advanced Networking. Each additional connection costs $30 per month. PrivateLink data transfer costs $0.04 per GB. Learn more in the AWS PrivateLink documentation. Read more ## Set per-user budgets on AI Gateway DevFeed: [Set per-user budgets on AI Gateway]() Original publisher: [Read original article]() Author: Jerilyn Zheng Published: 2026-08-31T06:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [API](), [Artificial Intelligence](), [AI-assisted coding]() Tags: [ai](), [ai-gateway](), [api](), [cli](), [coding-agents](), [update](), [vercel]() ### AI overview Vercel AI Gateway now supports per-user spending budgets. Default or custom monthly, weekly, daily, or non-resetting limits can cover API-key and app-token usage, with alerts at configured thresholds and request blocking when any applicable budget is exceeded. ### Source excerpt You can now use AI Gateway budgets to set a dollar spending limit for each user on your team. The limit covers spend from every API key attributed to the user, along with their app tokens. After it's reached, AI Gateway rejects new requests until the budget resets or is increased. This is useful for controlling spend from coding agents and other workloads that run without supervision, and prevents one user from consuming all of the team's shared budget. Set user budgets Open the Users view on the Budgets page to set two kinds of user budgets: Default budget: If set, applies separately to every person without a custom budget, including users added later. Each user gets their own allowance rather than sharing one limit across the team. Custom budget: Applies to one person and overrides the default. Removing it returns that user to the default budget. Both default and custom budgets reset monthly by default, but you can change them to reset daily, weekly, or not at all. Budgets also support usage alerting via email to notify when you are at 50%, 75%, and/or 100% of your allocation. User budgets don't replace API key, project, or team budgets. A request must remain within every budget that applies to it. Reaching any applicable limit blocks new requests. API keys are attributed to the user who created them by default. If a key belongs to a production application or another shared workload, attribute it to the team from the API Keys page to keep its spend out of the key creator's budget. Keys created prior to the user budget feature release were attributed to the team for backwards-compatibility, so rotate to new keys if you wish to have current usage fall under the user scope. Set budgets from the CLI Upgrade to the latest Vercel CLI with vercel upgrade. You need Vercel CLI 59.6.2 or newer for user budgets, then set a default or custom user budget: Identify a member by their email address, username, or user ID. Team owners can manage user budgets, and can also grant oth ## fx is now available in the AI SDK harness layer DevFeed: [fx is now available in the AI SDK harness layer]() Original publisher: [Read original article]() Author: Felix Arntz Published: 2026-08-31T06:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [vercel ai sdk](), [SDKs](), [Vercel](), [AI-assisted coding](), [API](), [Protocol (disambiguation)]() Tags: [agent](), [agents](), [ai](), [api](), [building](), [claude](), [claude-code](), [codex](), [coding-agents](), [cursor](), [integration](), [open-source](), [opencode](), [sdk](), [vercel]() ### AI overview Vercel's AI SDK harness layer now supports fx, a lightweight open-source coding agent. Developers can run fx in their applications through the HarnessAgent interface using the official @ai-sdk/harness-fx adapter, which connects through the Agent Client Protocol via @ai-sdk/harness-acp. ### Source excerpt The AI SDK harness layer now supports fx, Vercel's lightweight, open-source coding agent. The harness layer provides one API for running coding agents in your application, so you can add fx without building a separate integration. Configure HarnessAgent with the official @ai-sdk/harness-fx adapter: The @ai-sdk/harness-fx adapter connects to fx over the Agent Client Protocol (ACP) using @ai-sdk/harness-acp. fx joins Claude Code, Cline, Codex, Cursor, Deep Agents, Grok Build, OpenCode, and Pi in the list of supported harnesses. Read the fx harness documentation to get started. Read more ## Vercel Sandbox now calculates snapshot storage costs daily DevFeed: [Vercel Sandbox now calculates snapshot storage costs daily]() Original publisher: [Read original article]() Author: Tom Lienard Published: 2026-08-31T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel]() Tags: [billing](), [cost](), [documentation](), [enterprise](), [sandbox](), [storage](), [update]() ### AI overview Vercel now calculates Sandbox snapshot storage charges from each day's average usage instead of one monthly average. The $0.08 per GB-month rate is unchanged, and the daily charges are shown on the team's Usage page for Pro and Enterprise teams. ### Source excerpt Vercel now calculates charges for Sandbox snapshot storage from each day's average usage and adds them to your monthly invoice. Previously, billing used one average across the entire monthly billing period. You can track these daily charges on the team's Usage page and see how changes in storage affect your cost. The rate remains $0.08 per GB-month; only how usage is calculated has changed. The update takes effect automatically at the start of the next billing period for Pro and Enterprise teams. No action is required. Learn more about Sandbox snapshot storage in the documentation. Read more ## CoreBreak proves agent guardrails need to live outside the agent DevFeed: [CoreBreak proves agent guardrails need to live outside the agent]() Original publisher: [Read original article]() Author: Tyler Akidau Published: 2026-08-31T00:00:00Z Content type: opinion Language: en Sources: [Redpanda]() Topics: [Artificial Intelligence](), [AI Agent](), [Security](), [Securing AI](), [Amazon Web Services](), [vercel ai sdk](), [Amazon Bedrock](), [Google](), [Vercel]() Tags: [agent](), [agentic-ai](), [ai](), [ai-agent](), [architecture](), [aws](), [bedrock](), [cve](), [google](), [policy](), [security](), [thought-leadership](), [vercel]() ### AI overview The article argues that CoreBreak exposed a structural security flaw in major AI agent stacks and that agent guardrails should be enforced outside the agent's control. ### Source excerpt At Black Hat 2026, CoreBreak exposed the same structural flaw across AWS, Google, and Vercel. Here's why AI agent security enforcement should live beyond the agent's reach. ## Vercel CLI expands commands for DNS, domains, and projects DevFeed: [Vercel CLI expands commands for DNS, domains, and projects]() Original publisher: [Read original article]() Author: Melkey Moksyakov Published: 2026-08-28T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [Terminal](), [API](), [dashboards](), [observability](), [JSON]() Tags: [agents](), [api](), [cli](), [configuration](), [dns](), [json](), [observability](), [projects](), [terminal](), [update](), [vercel](), [web]() ### AI overview Vercel CLI adds commands for managing DNS records, Vercel domains, project state, observability settings, and project members. The commands support structured JSON output and require explicit confirmation for billable or destructive actions. ### Source excerpt The Vercel CLI now provides dedicated commands for managing DNS records, domains, and projects. This brings more of the functionality available through the Vercel dashboard and API to the terminal, where it can be used interactively, in scripts, or by agents. Inspect and update DNS records Retrieve the complete configuration for a DNS record or update it in place using its record ID. vercel dns update supports changes to the record name, type, value, TTL, MX priority, and comment. SRV records can also be updated using their priority, weight, port, and target fields. Renew domains bought on Vercel Renew a domain on demand or control whether it renews automatically. The renewal command displays the current renewal price and asks for confirmation before completing the purchase. Control project state and observability Pause or resume a project and configure its observability features directly from the CLI. Web Analytics and Speed Insights could already be enabled from the CLI; they can now be disabled as well. Add and remove project members Add a project member with a specific role or remove an existing member. All of the new commands support structured JSON output for scripts and agents. Billable or destructive actions require explicit confirmation. Update to version 59.6.2 (or later) of the Vercel CLI to use the new commands: Learn more in the Vercel CLI documentation. Read more ## Find deployments faster with redesigned filters DevFeed: [Find deployments faster with redesigned filters]() Original publisher: [Read original article]() Author: William Bout Published: 2026-08-27T13:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Deployment](), [Vercel]() Tags: [deployment](), [vercel]() ### AI overview Vercel has redesigned the filters on the Deployments page to help users find specific deployments faster. ### Source excerpt The Deployments page now has redesigned filters that make it faster to find a specific deployment. You can: Apply suggested filters for common searches. Type to find an option instead of scrolling through the list. Describe what you're looking for in natural language, and Vercel automatically applies the matching filters. Open any project's Deployments page to try the new filters. Read more [Next page]()