# Install aiven-client with Homebrew Official command-line client for Aiven. Version 4.16.0 via Homebrew; verified 2026-07-08. ## Install ```sh sudo av install brew:aiven-client ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install aiven-client ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:aiven-client - **Package manager:** Homebrew - **Version:** 4.16.0 - **Source summary:** Official command-line client for Aiven - **Homepage:** - **Repository:** - **Last updated:** 2026-07-08T15:12:54Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - avn (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 4.16.0 ## Project history and usage Aiven CLI is the official command-line client for Aiven's managed cloud services platform. It is distributed as the `aiven-client` Python package and installs the `avn` executable, giving users a scriptable interface to Aiven projects, services, users, events, clouds, and access tokens. ### Project history The public GitHub repository was created in December 2015, fitting Aiven's early period of exposing its managed-service platform through APIs and automation tooling. The README describes `aiven-client (avn)` as the official command-line client for Aiven and positions it beside the backend service rather than as a third-party wrapper. The project remained a Python CLI with a small Unix-friendly surface: install from PyPI or Homebrew, authenticate once, then drive Aiven resources through commands that can emit raw REST API JSON for use with tools such as `jq`. ### Adoption history Adoption is mainly tied to Aiven customers and operators rather than to a general-purpose developer audience. Official docs document pip and Homebrew installation, and the Homebrew formula appears in the input package-manager facts as `brew:aiven-client`. The tool's durable package-manager value is that it gives Homebrew users a first-party `avn` binary without needing to remember Python packaging details, while still staying aligned with the PyPI package and the upstream Aiven API. ### How it is used Typical use starts with `avn user login`, either with a username/password flow or an access token generated in the Aiven Console. The client can also read an auth token from `~/.config/aiven/aiven-credentials.json` and a default project from `~/.config/aiven/aiven-client.json`. The CLI is used for project selection, cloud-region listing, service management, event inspection, access-token management, and automation scripts. Its `--json` output is explicitly documented for piping REST API responses into other command-line tools. ### Why package nerds care For package-manager users, `aiven-client` is a classic vendor CLI formula: the package is not interesting because it is a new language runtime, but because it pins a first-party cloud API surface into reproducible local tooling. The split between PyPI, uvx, and Homebrew also makes it a useful example of a Python command-line package that needs to feel native in several installer cultures while preserving one executable name, `avn`. ### Timeline - 2015: Public GitHub repository created for `aiven/aiven-client`. - Later: Official docs document PyPI, uvx, and Homebrew installation paths. - 2026: Official docs still present the Aiven CLI as the scriptable command-line interface for the Aiven platform. ### Related projects - Aiven API: the REST API surface that the CLI exposes for shell usage. - Aiven MCP: a newer official Aiven tool documented alongside the CLI for natural-language management of Aiven services. ### Sources - - - - input source_facts.package-manager.brew ## Security Notes No matching local secret-handling manifest was found for aiven-client. Nucleus package metadata is still published here so future coverage has a stable package URL. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ~/.config/aiven/aiven-client.json ## Credential files - Unix: ~/.config/aiven/aiven-credentials.json ## Combined YAML source View the package source record on GitHub. [combined/aiven-client.yml](https://github.com/mxcl/pkgdb/blob/main/combined/aiven-client.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph