# Install cadence-workflow with Homebrew

Distributed, scalable, durable, and highly available orchestration engine. Version 1.4.1 via Homebrew; verified 2026-07-04.

## Install

```sh
sudo av install brew:cadence-workflow
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install cadence-workflow
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:cadence-workflow
- **Package manager:** Homebrew
- **Version:** 1.4.1
- **Source summary:** Distributed, scalable, durable, and highly available orchestration engine
- **Homepage:** <https://cadenceworkflow.io/>
- **Repository:** <https://github.com/cadence-workflow/cadence>
- **Last updated:** 2026-07-04T16:53:42+09:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- cadence-canary (alias)
- cadence-cassandra-tool (alias)
- cadence-server (alias)
- cadence-sql-tool (alias)

## Install behavior

- Bottle: not available

## Freshness

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

Cadence Workflow is Uber-originated durable execution infrastructure for long-running business logic. It provides a distributed orchestration engine, CLI, SDKs, persistence integrations, visibility services, and operational tools for workflows that need retries, timers, signals, history, and resilience across process crashes.

### Project history

The Cadence repository describes the platform as open source since 2017 and containing the core orchestration engine plus CLI, schema management, benchmark, and canary tools. Its backend runs multiple services with a database such as Cassandra, MySQL, or PostgreSQL, optionally paired with Kafka and Elasticsearch/OpenSearch-style visibility components.

Cadence grew out of the durable workflow lineage associated with systems such as Amazon SWF and later inspired the 2019 Temporal fork. Official Cadence documentation now frames Cadence and Temporal as sharing the same durable execution model while diverging in governance, ecosystem, cost model, and operational emphasis.

### Adoption history

Cadence's adoption is anchored by large-scale Uber production use. The official comparison page says Cadence grew at Uber from fewer than 100 domains at the Temporal fork point to over 4,000 domains, facilitating billions of workflows and hundreds of billions of updates monthly.

The project also moved into broader open-source governance: the official FAQ identifies Cadence as a CNCF Sandbox project under the Linux Foundation, with an ecosystem of about 150 companies and open governance. The Homebrew formula packages the server-side tools and CLI-oriented binaries for local development and operations.

### How it is used

A typical Cadence deployment runs backend services, persistence, optional visibility infrastructure, and workers containing application workflow code. Operators use the Cadence CLI to inspect and operate workflows, task lists, domains, and clusters; the Homebrew package includes server, SQL schema, Cassandra schema, and canary tools.

### Why package nerds care

Cadence is significant in package-manager culture because it packages a distributed system, not just a command. The formula exposes multiple operational binaries, schema tools, config trees, and version-coupled server/client expectations, which makes it a useful case study for packaging infrastructure software that straddles local development, production operations, and service orchestration.

### Timeline

- 2017: Cadence is open sourced according to the official repository README.
- 2019: Temporal is created as a fork of Cadence.
- 2020s: Cadence continues as Uber-scale durable execution infrastructure with Go and Java SDKs, CLI, Web UI, and schema tools.
- 2023: Cadence joins the CNCF Sandbox, per official Cadence documentation.
- 2026: Official docs describe 4,000+ Uber domains and billions of workflows monthly.

### Related projects

- Related projects include the official Cadence Go and Java SDKs, Cadence Web UI, Cadence IDLs, Helm charts, iWF, and Temporal. The durable execution lineage is commonly discussed alongside Amazon SWF and Azure Durable Functions.

### Sources

- <https://cadenceworkflow.io/docs/operation-guide/maintain>
- <https://cadenceworkflow.io/faq/cadence-vs-temporal>
- <https://github.com/cadence-workflow/cadence#readme>
- source_facts.package-manager


## Security Notes

broad file, network, media, or database tool signal. infrastructure mutation or orchestration signal.

- **Geiger risk:** orange / medium
- broad file, network, media, or database tool signal
- 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: config/, config/base.yaml, config/development.yaml, config/<CADENCE_ENVIRONMENT>.yaml, config/<CADENCE_AVAILABILITY_ZONE>.yaml, cadence/config/dynamicconfig/development.yaml, /etc/custom-dynamicconfig/development.yaml, config/config_template.yaml

## Combined YAML source

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