# Install vitess with Homebrew, Nix Database clustering system for horizontal scaling of MySQL. Version 24.0.2 via Homebrew; verified 2026-06-24. ## Install ```sh sudo av install brew:vitess ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install vitess ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#vitess ``` Evidence: nixpkgs package indexes: pkgs/by-name/vi/vitess/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:vitess - **Package manager:** Homebrew - **Package manager page:** - **Version:** 24.0.2 - **Source summary:** Database clustering system for horizontal scaling of MySQL - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Last updated:** 2026-06-24T19:30:05Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - mysqlctl (cli) - mysqlctld (cli) - vtadmin (cli) - vtbackup (cli) - vtctl (cli) - vtctlclient (cli) - vtctld (cli) - vtctldclient (cli) - vtgate (cli) - vtorc (cli) - vttablet (cli) - mysqlctl (alias) - mysqlctld (alias) - vtadmin (alias) - vtbackup (alias) - vtctl (alias) - vtctlclient (alias) - vtctld (alias) - vtctldclient (alias) - vtgate (alias) - vtorc (alias) - vttablet (alias) ## Dependencies - etcd ## Build dependencies - go ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 24.0.2 - Package-manager updated: 2026-06-24 - Local data: ok - Upstream repository: https://github.com/vitessio/vitess - Upstream latest detected: v24.0.2 (current) ## Project history and usage Vitess is an open-source database clustering system for horizontally scaling MySQL. It sits between applications and MySQL, routes queries through VTGate, manages tablets through VTTablet, and lets applications continue using MySQL-compatible clients while data is split across shards. Its historical importance comes from being a production-born database infrastructure project: it started inside YouTube, became a CNCF project, and is used as a way to move large MySQL estates toward cloud-native operations without rewriting every application around custom sharding logic. ### Project history Vitess was created at YouTube in 2010 after read replicas and application-level sharding were no longer enough to keep MySQL serving capacity ahead of traffic. The Vitess history page describes the progression from one primary database, to read replicas, to sharding, and then to the need for a reusable system around those shards. The project became public on GitHub in 2012 and later moved into a vendor-neutral governance setting. CNCF accepted Vitess as an incubation project in February 2018, and Vitess graduated in November 2019 as the eighth CNCF graduated project. Vitess 4.0 was announced at graduation time, with CNCF highlighting improved SQL query support, experimental VReplication support, and usability work aimed at making the system easier for new operators to adopt. ### Adoption history CNCF's graduation announcement states that Vitess had been a core component of YouTube's database infrastructure since 2011 and had grown there to encompass tens of thousands of MySQL nodes. Vitess documentation also says it served all YouTube database traffic for more than five years. Beyond YouTube, official Vitess documentation names Slack, Square, and JD.com as production users. CNCF's Vitess project journey report describes community growth after CNCF entry, including hundreds of contributors, thousands of commits, and dozens of contributing companies during the measured period. Vitess also became commercially significant through PlanetScale, whose founders included Vitess co-creators and operators. That connection helped make Vitess familiar to developers who might never run a multi-shard MySQL fleet directly but encountered the architecture through managed database services. ### How it is used Operators use Vitess when a single MySQL server or manually managed replication topology is no longer enough. VTGate exposes a MySQL-compatible query endpoint, VTTablet runs alongside MySQL instances, and a topology service such as etcd, ZooKeeper, or Consul stores cluster state. Vitess is used for sharding, resharding, failover, backups, connection pooling, query protection, and large-fleet operational control. A key appeal is that applications can often continue using MySQL drivers while Vitess handles routing and cluster management below the application layer. ### Why package nerds care Vitess is the kind of package whose command list tells a story: `vtgate`, `vttablet`, `vtctl`, `vtctld`, `mysqlctl`, and related tools expose the moving parts of a distributed database control plane. For package maintainers and infrastructure developers, it represents the category of serious cloud-native database software that still preserves the MySQL protocol as an adoption bridge. ### Timeline - 2010: Vitess was created inside YouTube to address MySQL scalability limits. - 2011: Vitess became a core component of YouTube database infrastructure. - 2012: The first public Vitess GitHub commit was made on February 24. - 2018: CNCF accepted Vitess as an incubation project in February. - 2019: CNCF announced Vitess graduation in November, alongside Vitess 4.0. - 2020: CNCF published a Vitess project journey report documenting post-CNCF community and adoption growth. ### Related projects - Vitess is related to MySQL and Percona Server because it scales and manages those databases rather than replacing their storage engine outright. - It is also related to Kubernetes, etcd, gRPC, Prometheus, ZooKeeper, and Consul through cloud-native deployment, topology, monitoring, and control-plane integrations. ### Sources - batch input current_curation.docs, current_curation.repo, and current_curation.tags - - - - ## Security Notes infrastructure mutation or orchestration signal. - **Geiger risk:** orange / medium - infrastructure mutation or orchestration signal ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** vitess - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Other Package-Manager Records - Nix - vitess: normalized package name match | nixpkgs package indexes: pkgs/by-name/vi/vitess/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Related links - [Cloud CLI packages](https://www.automicvault.com/pkg/cloud-clis/) - Belongs to a cloud or infrastructure command family. - [Secret-risk packages](https://www.automicvault.com/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [etcd](https://www.automicvault.com/pkg/brew/etcd/) - Runtime dependency declared by Homebrew. - [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew. - [automysqlbackup](https://www.automicvault.com/pkg/brew/automysqlbackup/) - Shares av.db curated category or tags: cli, data, database, mysql. - [dumpling](https://www.automicvault.com/pkg/brew/dumpling/) - Shares av.db curated category or tags: cli, data, database, mysql. - [kitchen-sync](https://www.automicvault.com/pkg/brew/kitchen-sync/) - Shares av.db curated category or tags: cli, data, database, mysql. - [lazysql](https://www.automicvault.com/pkg/brew/lazysql/) - Shares av.db curated category or tags: cli, data, database, mysql. - [mysql](https://www.automicvault.com/pkg/brew/mysql/) - Shares av.db curated category or tags: cli, data, database, mysql. - [percona-server](https://www.automicvault.com/pkg/brew/percona-server/) - Shares av.db curated category or tags: cli, data, database, mysql. - [percona-xtrabackup](https://www.automicvault.com/pkg/brew/percona-xtrabackup/) - Shares av.db curated category or tags: cli, data, database, mysql. - [sqlite3-to-mysql](https://www.automicvault.com/pkg/brew/sqlite3-to-mysql/) - Shares av.db curated category or tags: cli, data, database, mysql. ## Combined YAML source View the package source record on GitHub. [combined/vitess.yml](https://github.com/automic-vault/db/blob/main/combined/vitess.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph