# Install dtm with Homebrew

Cross-language distributed transaction manager. Version 1.19.0 via Homebrew; verified 2026-07-29.

## Install

```sh
sudo av install brew:dtm
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install dtm
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:dtm
- **Package manager:** Homebrew
- **Version:** 1.19.0
- **Source summary:** Cross-language distributed transaction manager
- **Homepage:** <https://en.dtm.pub/>
- **Repository:** <https://github.com/dtm-labs/dtm>
- **Last updated:** 2026-07-29T17:00:36+09:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- dtm (alias)
- dtm-qs (alias)

## Install behavior

- Bottle: not available

## Freshness

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

DTM is a Go-origin distributed transaction manager for microservice systems. Its niche is cross-service data consistency: the project presents saga, TCC, XA, two-phase message, outbox, and workflow patterns behind one transaction service with SDKs for several languages.

### Project history

The public GitHub repository was created in 2021 and the official documentation describes DTM as a distributed transaction framework in Go. The README and documentation emphasize that the server can coordinate transaction branches over HTTP or gRPC and can use storage backends such as MySQL, Redis, BoltDB, PostgreSQL, and others.

The project grew around the operational problem of making distributed transactions usable in polyglot microservice deployments. Its examples and quick-start material center on common business flows such as inter-bank transfers, orders, flash sales, cache consistency, and event publishing.

### Adoption history

DTM's README and documentation include a 'Who's using DTM' page listing organizations such as Tencent and ByteDance as users. Homebrew packaging gives it a small but useful macOS/Linux CLI distribution channel, with the formula tracking the upstream GitHub tags.

### How it is used

Users typically run the `dtm` service, point application SDKs at it, and model business operations as saga, TCC, XA, workflow, or message transactions. The project also ships `dtm-qs` for quick-start workflows. Configuration is optional for simple runs, with `conf.sample.yml` documenting storage, ports, timeouts, logging, and microservice discovery settings.

### Why package nerds care

For package people, DTM is notable because it packages a distributed-systems coordination service as a normal installable CLI/server rather than just a Go library. It also sits at the intersection of Go services, language SDKs, database drivers, and package-manager distribution, which makes it a compact example of modern infrastructure tooling leaving the language ecosystem and entering system package indexes.

### Timeline

- 2021: Public dtm-labs/dtm GitHub repository created.
- 2021 onward: Project documentation describes saga, TCC, XA, two-phase message, outbox, and workflow support.
- 2020s: Homebrew formula distributes the `dtm` and `dtm-qs` executables from upstream GitHub releases.

### Related projects

- DTM documentation and repository topics place it near Seata, workflow engines, outbox/message-transaction implementations, and Go microservice frameworks such as go-zero and Kratos. The project also maintains quick-start and example repositories under the dtm-labs organization.

### Sources

- <https://github.com/dtm-labs/dtm>
- <https://en.dtm.pub/>
- <https://en.dtm.pub/other/using.html>
- <https://github.com/dtm-labs/dtm/blob/main/conf.sample.yml>
- <https://formulae.brew.sh/api/formula/dtm.json>


## 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: ./conf.yml

## Combined YAML source

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