# Install berglas with Homebrew, Nix

Tool for managing secrets on Google Cloud. Version 2.0.15 via Homebrew; verified 2026-07-26. Also installable with nix: nix profile install nixpkgs#berglas.

## Install

```sh
sudo av install brew:berglas
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install berglas
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#berglas
```

  Evidence: nixpkgs package indexes: pkgs/by-name/be/berglas/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:berglas
- **Package manager:** Homebrew
- **Version:** 2.0.15
- **Source summary:** Tool for managing secrets on Google Cloud
- **Homepage:** <https://github.com/GoogleCloudPlatform/berglas>
- **Repository:** <https://github.com/GoogleCloudPlatform/berglas>
- **Last updated:** 2026-07-26T10:56:33+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- berglas (alias)

## Install behavior

- Bottle: not available

## Freshness

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

Berglas is a GoogleCloudPlatform command-line tool and Go library for storing and retrieving secrets on Google Cloud. It predates some common Secret Manager workflows and bridges Cloud KMS, Cloud Storage, and Secret Manager access patterns.

### Project history

The Berglas repository was created in April 2019, with a v0.1.3 release published in June 2019. Its README describes it as both a CLI for encrypting, decrypting, and storing data on Google Cloud and a library for injecting secrets into Google Cloud runtimes.

The project is explicit about its support status: it lives under GoogleCloudPlatform but is not an officially supported Google product.

### Adoption history

Berglas adoption came from teams that needed secret handling around Cloud KMS and Cloud Storage, then later interoperability with Secret Manager. It fit CI/CD and serverless workflows where environment injection and CLI automation were convenient.

Homebrew packaging made it easy for macOS operators to bootstrap and inspect Google Cloud secret workflows locally while using Application Default Credentials from the Cloud SDK.

### How it is used

Common commands create secrets, grant access, read secret data, bootstrap buckets and KMS keys, and run child processes with secrets populated in the environment.

Authentication usually follows Google Cloud Application Default Credentials, which is why the package curation points at the gcloud ADC credentials file rather than a Berglas-specific credentials file.

### Why package nerds care

Berglas is package-nerd significant as a small Go security CLI with cloud-side state. Installing the package gives a local executable, but most real behavior depends on enabled Google Cloud services, IAM, KMS keys, buckets, or Secret Manager resources.

It is also a snapshot of a transitional Google Cloud secrets era: the tool supports the older Cloud Storage plus KMS pattern while documenting interoperability with Secret Manager.

### Timeline

- 2019-04: The GoogleCloudPlatform/berglas repository was created.
- 2019-06: Berglas v0.1.3 was published.
- 2020s: Berglas documentation continued to emphasize Cloud KMS, Cloud Storage, Secret Manager interoperability, and ADC-based setup.

### Related projects

- Google Cloud KMS supplies encryption keys for the original storage model.
- Google Cloud Storage stores encrypted secret blobs in the original model.
- Google Secret Manager is the related managed service with Berglas interoperability.

### Sources

- <https://github.com/GoogleCloudPlatform/berglas>
- <https://github.com/GoogleCloudPlatform/berglas/releases/tag/v0.1.3>


## Security Notes

infrastructure mutation or orchestration signal.

- **Geiger risk:** orange / medium
- infrastructure mutation or orchestration signal


## 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.


## Credential files

- Unix: ~/.config/gcloud/application_default_credentials.json
- Windows: %APPDATA%\gcloud\application_default_credentials.json
## Other Package-Manager Records

- Nix - berglas: normalized package name match | nixpkgs package indexes: pkgs/by-name/be/berglas/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

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