# Install juju with Homebrew, chocolatey, Nix, winget DevOps management tool. Version 4.0.13 via Homebrew; verified 2026-07-26. Also installable with nix: nix profile install nixpkgs#juju. ## Install ```sh sudo av install brew:juju ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install juju ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#juju ``` Evidence: nixpkgs package indexes: pkgs/by-name/ju/juju/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ### Windows - Chocolatey (92%): ```sh choco install juju ``` Evidence: Chocolatey community package catalog: juju from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','java7u13x86' - winget (92%): ```sh winget install --id Canonical.Juju -e ``` Evidence: Windows Package Manager source index: Canonical.Juju from https://cdn.winget.microsoft.com/cache/source.msix ## Package facts - **Package key:** brew:juju - **Package manager:** Homebrew - **Version:** 4.0.13 - **Source summary:** DevOps management tool - **Homepage:** - **Repository:** - **Last updated:** 2026-07-26T04:08:08+02:00 - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - juju (alias) - juju-metadata (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 4.0.13 ## Project history and usage Juju is Canonical's model-driven operations and application orchestration tool. It uses charms, controllers, models, and relations to deploy, integrate, scale, and operate software across Kubernetes, virtual machines, bare metal, and public or private clouds. ### Project history Juju grew out of Canonical's effort to make operations code reusable. Official documentation describes charms as operators that package the instructions needed to deploy, configure, scale, integrate, and manage applications on supported clouds. The model/controller split became central: users bootstrap a controller, create models, deploy charms, and let agents reconcile desired state. ### Adoption history By July 2015, Canonical was publishing Kubernetes 1.0 deployment workflows through Juju charms. In June 2016, Canonical announced additional storage and networking vendors in the Juju Charm Partner Program, showing an attempt to build an ecosystem around reviewed, reusable operations code. ### How it is used The Homebrew package exposes the `juju` CLI and related metadata tooling for bootstrapping controllers, adding models, deploying charms, managing credentials, and integrating applications. The CLI is both a local client and the main entry point into Juju's controller-backed orchestration model. ### Why package nerds care Juju is notable in package-manager culture because the CLI is only the tip of a larger distributed control plane. Installing the package gives access to an ecosystem of charms, Charmhub, cloud credentials, controller state, and model data rather than a self-contained utility. ### Timeline - 2014: GitHub tags show the 1.20.0 release line. - 2015: Canonical documented Kubernetes 1.0 deployment through Juju charms. - 2016: Canonical announced added vendors in the Juju Charm Partner Program. - 2020: GitHub tags show the 2.8.0 release line. - 2023: GitHub tags show a 3.0 end-of-life marker, reflecting the 3.x generation. ### Related projects - Charmhub is the charm and bundle discovery surface for Juju users. - The Operator Framework-style Ops library is the standard framework for modern charm authors. - MAAS, LXD, Kubernetes, and OpenStack are common infrastructure contexts for Juju deployments. ### Sources - - - - - - - - ## Security Notes No matching local secret-handling manifest was found for juju. 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: $JUJU_DATA/clouds.yaml, $JUJU_DATA/controllers.yaml, $JUJU_DATA/models.yaml, ~/.local/share/juju/clouds.yaml, ~/.local/share/juju/controllers.yaml, ~/.local/share/juju/models.yaml ## Credential files - Unix: $JUJU_DATA/credentials.yaml, ~/.local/share/juju/credentials.yaml ## Other Package-Manager Records - Nix - juju: normalized package name match | nixpkgs package indexes: pkgs/by-name/ju/juju/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Chocolatey - juju: normalized package name match | Chocolatey community package catalog: juju from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','java7u13x86' - winget - Canonical.Juju: normalized package name match | Windows Package Manager source index: Canonical.Juju from https://cdn.winget.microsoft.com/cache/source.msix ## Combined YAML source View the package source record on GitHub. [combined/juju.yml](https://github.com/mxcl/pkgdb/blob/main/combined/juju.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph