# Install azion with Homebrew

CLI for the Azion service. Version 4.22.2 via Homebrew; verified 2026-07-26.

## Install

```sh
sudo av install brew:azion
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install azion
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:azion
- **Package manager:** Homebrew
- **Version:** 4.22.2
- **Source summary:** CLI for the Azion service
- **Homepage:** <https://github.com/aziontech/azion>
- **Repository:** <https://github.com/aziontech/azion>
- **Last updated:** 2026-07-26T13:19:55+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- azion (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 4.22.2
## Project history and usage

Azion CLI is the command-line interface for managing Azion Edge Platform resources and application deployments. It is a vendor CLI in the modern edge-platform style: part deployment tool, part account/product manager, and part infrastructure-as-code helper.

### Project history

The current aziontech/azion repository was created in November 2021. The README describes Azion CLI as a user-friendly way to create and manage applications on the Azion Edge Platform, including initialization, build, deployment, product management, CI/CD automation, and configuration-as-code workflows.

The README also preserves a naming transition: it warns users who downloaded `azioncli` before version 1.0.0 to uninstall it before installing the `azion` CLI. That marks the tool's consolidation around the shorter `azion` executable and packaging name.

### Adoption history

The official README says Azion CLI is available through package managers including Homebrew, WinGet, Chocolatey, rpm, deb, and apk packages, plus a curl-based installer and release downloads. The batch input only includes Homebrew, so the broader package-manager list comes from the official README rather than the package index snapshot.

### How it is used

Users authenticate with a personal token via `azion -t <token>` or `azion login`, then use the CLI to initialize, build, deploy, and manage applications and Azion services. The official docs page for globals mentions `azion.config.js` and the token settings file, while the config page documents manifest-style configuration through `azion.json` and `azion.config.js`.

### Why package nerds care

Azion CLI is package-nerd significant because it packages an edge provider's operational API into a repeatable workstation and CI binary. Its Homebrew formula is one slice of a broader release matrix that also targets native Linux and Windows package channels.

For maintainers, the interesting part is the fast-moving vendor CLI lifecycle: regular releases, embedded auth state, local metrics/config files, and packaging formats for several operating systems all need to line up with the same executable name.

### Timeline

- 2021: Current aziontech/azion repository created.
- 2024: Official release stream includes 1.x releases under the `azion` CLI package.
- 2025: 4.x release stream active.
- 2026: 4.22.x releases published.

### Related projects

- The README relates Azion CLI to the Azion Edge Platform and to application frameworks including Next.js, Vue, Angular, Astro, Hexo, React, and Vite.

### Sources

- GitHub releases API lists active 4.x releases in 2025 and 2026.
- GitHub repository metadata: created_at 2021-11-22.
- Official Azion config docs mention azion.json and azion.config.js.
- Official Azion globals docs mention azion.config.js and ~/.azion/settings.toml.
- Official README documents purpose, framework deployment scope, package-manager availability, and the pre-1.0 `azioncli` uninstall note.


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## 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: ./azion.json, ./azion.config

## Credential files

- Unix: ~/.azion/settings.toml

## Combined YAML source

View the package source record on GitHub. [combined/azion.yml](https://github.com/mxcl/pkgdb/blob/main/combined/azion.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