# Install depot with Homebrew

Build your Docker images in the cloud. Version 2.101.77 via Homebrew; verified 2026-07-31.

## Install

```sh
sudo av install brew:depot
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install depot
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:depot
- **Package manager:** Homebrew
- **Version:** 2.101.77
- **Source summary:** Build your Docker images in the cloud
- **Homepage:** <https://depot.dev/>
- **Repository:** <https://github.com/depot/cli>
- **Last updated:** 2026-07-31T15:18:17Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- depot (alias)

## Install behavior

- Bottle: not available

## Freshness

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

Depot CLI is the official command-line interface for Depot, a build infrastructure platform for faster container builds and CI workflows. Its original center of gravity is remote Docker builds with managed cache and native x86 and Arm builders.

### Project history

The depot/cli repository was created in 2021. The README describes the CLI as the official way to build Docker images through Depot's remote builder infrastructure, while the current documentation positions Depot more broadly around container builds, Depot CI, GitHub Actions runners, and an OCI-compatible registry.

### Adoption history

Adoption follows teams that already have Docker or GitHub Actions workflows and want faster hosted build machines without changing their Dockerfiles. The README presents Homebrew, an install script, Proto, and GitHub release binaries, making the CLI accessible in local development and CI images.

### How it is used

A normal first run is `depot login`, `depot init`, and then `depot build -t repo/image:tag .`. `depot init` links the local directory to a Depot project by writing `depot.json`; build and bake commands can also take a project flag or environment variable for CI use.

### Why package nerds care

Package nerds care about Depot CLI because it acts as a drop-in package around buildx-style workflows: the command line looks familiar, but the cache, CPU architecture, and builder lifecycle move to a managed remote service.

### Timeline

- 2021: Official depot/cli repository created.
- 2022: Depot documentation metadata identifies Depot's founding year.
- 2026: Depot docs describe container builds, Depot CI, GitHub Actions runners, and Depot Registry.

### Related projects

- Related official surfaces include Depot container builds, Depot CI, Depot GitHub Actions runners, Depot Registry, and the Depot documentation site.

### Sources

- <https://github.com/depot/cli#readme>
- <https://depot.dev/docs>
- <https://depot.dev/docs.md>
- <https://api.github.com/repos/depot/cli>


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


## Configuration files

- Unix: depot.json, .depot/workflows/

## Combined YAML source

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