Install vespa-cli with Homebrew, Nix

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• vespa
• vespa-wrapper

Project history

Vespa itself was open-sourced by Yahoo/Oath on September 27, 2017 as a big-data processing and serving engine for real-time search, recommendation, and personalization workloads. The open-source announcement positioned Vespa as the serving complement to batch and stream processing stacks such as Hadoop and Storm.

Vespa CLI was introduced on September 23, 2021. The announcement says Vespa users had historically deployed and interacted with applications through APIs or a Maven plugin, both of which had friction: API use meant copying dense terminal commands and Maven assumed a Java toolchain. The CLI was built as an official zero-dependency command-line tool for both self-hosted Vespa and Vespa Cloud.

In October 2023, Vespa.ai spun out of Yahoo as a separate company. Vespa's own announcement tied the spinout to the platform's evolution from Yahoo search, recommendation, and ad-serving infrastructure into a serving-time AI platform used for large datasets, vector search, and production relevance systems.

Adoption history

The CLI's adoption follows Vespa's adoption path: it became the normal local and cloud workflow surface for developers working with Vespa applications. Official documentation presents it as the command-line client for Linux, macOS, and Windows, and the command tree covers the everyday lifecycle from clone and deploy through feed, query, inspect, status, logs, tests, and production deployment.

Vespa's 2023 spinout announcement gives broader adoption context: Yahoo remained a major customer, the platform was serving personalized content and search use cases, and Vespa Cloud was already supporting production workloads. In that setting, the CLI is not just a convenience wrapper; it is the developer-facing entry point for a large hosted and self-managed search platform.

How it is used

Vespa CLI is used to clone sample applications, deploy application packages locally or remotely, deploy to Vespa Cloud, feed documents, query documents, and send authenticated custom requests. The docs also show it managing mTLS-related local state under `.vespa` and switching between local and cloud targets.

In package terms, `vespa` is the handle that turns Vespa from a server platform into an iterative developer workflow. A user can create or fetch an application package, deploy it, stream documents into it, run queries, inspect status, follow logs, and automate deployment operations without manually stitching together HTTP requests and authentication material.

Why package nerds care

Vespa CLI is significant because it condenses a complex distributed search platform into a reproducible command-line workflow. For packagers and operators, it is the small binary that makes Vespa approachable on a laptop, in CI, and in cloud automation, while still mapping directly to production Vespa concepts such as tenants, applications, instances, zones, deployments, documents, and queries.

Timeline

• 2016-06-03: Vespa GitHub repository created.
• 2017-09-27: Yahoo/Oath announced Vespa as open source on GitHub.
• 2021-09-23: Vespa CLI introduced as the official zero-dependency command-line tool.
• 2023-10-03: Vespa.ai announced it was spinning out of Yahoo as a separate company.

Related projects

• Vespa: the search, recommendation, and AI serving platform controlled by the CLI.
• Vespa Cloud: the hosted service targeted by the CLI for cloud deployment and operations.
• Maven plugin and direct Vespa APIs: the older interaction methods the CLI was designed to simplify.

Sources

• https://api.github.com/repos/vespa-engine/vespa
• https://blog.vespa.ai/introducing-vespa-cli/
• https://blog.vespa.ai/open-sourcing-vespa-yahoos-big-data-processing/
• https://blog.vespa.ai/vespa-is-becoming-its-own-company/
• https://docs.vespa.ai/en/clients/vespa-cli.html
• https://github.com/vespa-engine/vespa