Install vercel-cli with Homebrew, apt, MacPorts, Nix, pacman, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• vc
• vercel

Project history

Vercel itself was founded by Guillermo Rauch in 2015 as ZEIT, and the company's early developer experience centered on Now: a command-line deployment product for serverless, static, and frontend projects. The old Now CLI's appeal was its minimal flow: enter a project directory, run a command, and receive a live deployment URL.

On April 21, 2020, ZEIT announced that it had become Vercel, aligning the company around frontend teams and the develop-preview-ship workflow. The platform rename also propagated into the CLI: GitHub maintainers answered that the Now name had become Vercel, and the npm `now` package later carried a deprecation notice directing users to `vercel` after December 31, 2020.

Since the rename, Vercel CLI has become the local and automation-oriented control plane for the platform. Release notes such as Vercel CLI v28 in 2022 show the CLI absorbing more project lifecycle features, including Git integration, linked-project behavior, environment-pull improvements, and changes to deployment ergonomics.

Adoption history

The CLI's adoption tracks Vercel's rise with Next.js and frontend platform workflows. It is used by individual developers for one-command preview deployments, by teams to link local directories to hosted projects, and by CI systems through token authentication.

Vercel's platform also emphasizes Git-connected preview deployments, but the CLI remains important because it works outside the Git push path. It can deploy prebuilt output, pull environment variables, inspect deployments, view logs, manage DNS-related resources, and reproduce parts of the hosted deployment environment locally.

How it is used

Typical package use starts with installing the CLI, logging in, running `vercel link` for an existing project or `vercel`/`vercel deploy` from a project root, and then promoting with `vercel deploy --prod`. Day-to-day workflows commonly include `vercel env pull`, `vercel dev`, `vercel inspect`, `vercel logs`, and token-based commands in CI.

For package users, the `vc` alias and `vercel` binary sit at the boundary between local source trees and Vercel's hosted platform. That makes the tool less like a generic cloud SDK and more like a deployment workflow command, especially for Next.js and other frontend frameworks.

Why package nerds care

Vercel CLI is significant because it preserves the original Now-style instant deployment workflow while also covering modern project linking, environment management, preview, production, and automation use cases. In package collections, it is the local handle for a cloud platform that many JavaScript and frontend teams touch daily.

Timeline

• 2015: Guillermo Rauch founds ZEIT, the company that later becomes Vercel.
• 2010s: The Now CLI popularizes a one-command deployment workflow.
• April 21, 2020: ZEIT rebrands as Vercel.
• December 31, 2020: The old npm `now` package stops receiving updates, with users directed to the `vercel` package.
• August 2022: Vercel CLI v28 release notes show expanded project, Git, and environment-management behavior.
• 2020s: The CLI remains a primary interface for local development, preview deployments, production deploys, and CI/CD automation on Vercel.

Related projects

• Vercel CLI is related to the Vercel REST API, Next.js, Turborepo, Netlify CLI, Cloudflare Wrangler, Firebase CLI, AWS Amplify CLI, and other developer-first deployment CLIs. Its distinctive lineage is the ZEIT Now command flow and its close coupling to preview deployments.

Sources

• https://github.com/vercel/vercel
• https://github.com/vercel/vercel/discussions/4468
• https://vercel.com/blog/zeit-is-now-vercel
• https://vercel.com/changelog/vercel-cli-v28
• https://vercel.com/docs/cli
• https://vercel.com/docs/cli/deploy
• https://vercel.com/docs/projects/deploy-from-cli
• https://www.npmjs.com/package/now