Vercel adds CLI commands for DNS, domains and projects plus Deployment Storage for instant rollbacks

Vercel CLI expands into DNS, domain and project management

The Vercel command-line interface now ships dedicated commands for managing DNS records, domains and projects, according to an announcement on the Vercel blog. The update brings functionality that previously lived in the Vercel dashboard and API into the terminal, where it can be used interactively, in scripts, or by agents.

On the DNS side, vercel dns update lets you retrieve the complete configuration for a record and update it in place using its record ID. Editable fields include the record name, type, value, TTL, MX priority and comment. SRV records can be modified through their priority, weight, port and target fields.

Domain handling covers renewals. The renewal command can renew a domain on demand or control whether it renews automatically, and it displays the current renewal price and asks for confirmation before completing the purchase.

For projects, the CLI can now pause or resume a project and configure its observability features. Web Analytics and Speed Insights could already be enabled from the CLI; they can now also be disabled. Project membership is included as well, letting you add a member with a specific role or remove an existing one.

Two design details stand out. All of the new commands support structured JSON output, which makes them usable in scripts and by automated agents. In addition, any command that is billable or destructive requires explicit confirmation before it runs. Users need to update to the latest version of the Vercel CLI to get the new commands.

Deployment Storage keeps past deployments rollback-ready

In a second announcement on the Vercel blog, the company detailed Deployment Storage, the mechanism that keeps the files produced by every deployment — pages, functions and the assets Vercel serves — available so that older deployments can be inspected and used as rollback targets.

The headline capability is Instant Rollback. If a production deploy ships a bug or an unwanted change, you open the project, click Instant Rollback on the Production Deployment tile and choose an earlier production deployment. Vercel immediately repoints the project's domains to that deployment, restoring the previous version in seconds with no rebuild required.

Pricing and retention controls

Deployment Storage is billed at $0.10 per GB per month. Hobby plans include up to 10 GB. Existing teams continue with their current pricing, with no change to their bills at this time, according to the announcement.

Retention is configurable by deployment class. The Deployment Retention Policy sets how long Pre-Production, Production, Canceled and Errored deployments stay available. Shorter retention means less storage, but a deleted deployment can no longer be a rollback target — a direct trade-off between cost and the length of the rollback window. The Usage page breaks down Deployment Storage and Functions Storage per project. Vercel also suggests trimming the output directory, moving large files to Vercel Blob and reducing function bundle sizes to keep future deployments smaller.

Why it matters

Both changes target the same friction: operational work that had to happen in a web dashboard can now happen wherever the user already works. For teams that script their infrastructure or wire CLI output into CI, DNS edits, domain renewals, project lifecycle changes and membership updates can join the same repeatable workflow as deploys. The structured JSON output and the confirmation gates around billable and destructive actions suggest Vercel is designing these commands for automated agents as much as for humans typing at a prompt.

Deployment Storage addresses the other half of the deployment lifecycle: recovery. Being able to revert a bad production deploy in seconds, without waiting for a rebuild, can meaningfully shorten incident response — but only as far back as the retention policy allows. That makes the retention setting a genuine operational decision rather than a checkbox.

Taken together, the two features move more of the platform — configuration, membership, storage and recovery — into scriptable, automatable territory, which is a concrete quality-of-life improvement for teams already running their frontend infrastructure on Vercel.