# Install benthos with Homebrew, Nix

Stream processor for mundane tasks written in Go. Version 4.76.0 via Homebrew; verified 2026-06-25.

## Install

```sh
sudo av install brew:benthos
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install benthos
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#benthos
```

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

## Package facts

- **Package key:** brew:benthos
- **Package manager:** Homebrew
- **Package manager page:** <https://formulae.brew.sh/formula/benthos>
- **Version:** 4.76.0
- **Source summary:** Stream processor for mundane tasks written in Go
- **Homepage:** <https://github.com/redpanda-data/benthos>
- **Repository:** <https://github.com/redpanda-data/benthos>
- **Upstream docs:** <https://docs.redpanda.com/connect/configuration/about>
- **License:** MIT
- **Source archive:** <https://github.com/redpanda-data/benthos/archive/refs/tags/v4.76.0.tar.gz>
- **Last updated:** 2026-06-25T15:15:24Z
- **Generated:** 2026-07-08T07:18:31+00:00

## Executables

- benthos (cli)
- benthos (alias)

## Build dependencies

- go

## Install behavior

- Post-install hook: not defined
- Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux

## Freshness

- Page generated: 2026-07-08
- Package-manager version: 4.76.0
- Package-manager updated: 2026-06-25
- Local data: ok
- Upstream repository: https://github.com/redpanda-data/benthos
- Upstream latest detected: v4.76.0 (current)
## Project history and usage

Benthos is the long-running Go stream-processing package identity behind declarative source-to-pipeline-to-sink data flows. In current upstream naming it sits beside Redpanda Connect: the Benthos repository notes that the original connector-heavy project moved to redpanda-data/connect, while the Homebrew package preserves the older benthos command-line name.

### Project history

The public Benthos release line goes back at least to v0.0.1 in September 2016. Its core idea was operationally small: a single Go binary configured with YAML, a pipeline of processors, and connectors for mundane data plumbing tasks.

Redpanda's current Connect repository carries the same model forward, documenting declarative pipelines, Bloblang mappings, stateless operation, and at-least-once delivery using in-process transactions rather than local disk state.

### Adoption history

Benthos found a niche with operators who wanted stream processing without committing to a broker-specific framework or a large runtime. Package-manager adoption matters because the tool is useful as a local binary for testing configs, running one-off transforms, and shipping small container images.

The name also survived a branding and repository transition. Existing scripts, formulas, and muscle memory still point at benthos even as the broader upstream project is presented as Redpanda Connect.

### How it is used

Typical usage is to run a YAML config that declares an input, processors, and an output. Common tasks include message transformation, enrichment, filtering, bridging queues and object stores, and testing pipeline fragments locally.

For package users, the interesting command-line surface is not just running a daemon; it is linting, discovering components, and iterating on Bloblang mappings in the same binary that can later run in a container.

### Why package nerds care

Benthos is package-nerd significant because the package name captures a lineage split: old Benthos, Redpanda Connect, and the later Bento fork all occupy related but distinct points in the same ecosystem.

It is also a good example of why CLI package names can outlive product names. The executable, config examples, and dependency graph around plugins can remain stable enough that distributions keep the historical name even while upstream documentation changes.

### Timeline

- 2016: Benthos v0.0.1 was published publicly.
- 2021: The v3 release line was active, showing Benthos had become a mature Go stream-processing project.
- 2024: Redpanda's Benthos repository stated that the original connector repository moved to redpanda-data/connect.
- 2025: Redpanda Connect continued the v4 release line under the Connect name.

### Related projects

- Redpanda Connect is the direct successor/continuation for the connector-rich project history.
- Bento is a WarpStream-maintained fork of the pre-license-change project line.
- Bloblang is the mapping language associated with Benthos-style pipelines.

### Sources

- <https://docs.redpanda.com/redpanda-connect/about>
- <https://github.com/redpanda-data/benthos>
- <https://github.com/redpanda-data/connect>
- <https://github.com/redpanda-data/connect/releases/tag/v0.0.1>


## Security Notes

No matching local secret-handling manifest was found for benthos. Nucleus package metadata is still published here so future coverage has a stable package URL.


## Source Database Details

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** benthos
- **Version Scheme:** 0
- **Revision:** 0
- **Head Version:** HEAD
- **Bottle Stable Root URL:** <https://ghcr.io/v2/homebrew/core>
- **Deprecated:** no
- **Disabled:** no
- **Keg Only:** no
- **URL Keys:** head, stable

## Other Package-Manager Records

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


## Related links

- [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family.
- [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata.
- [Language runtime packages](https://www.automicvault.com/pkg/language-runtime-packages/) - Matched language runtime, compiler, or interpreter metadata.
- [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew.
- [nifi](https://www.automicvault.com/pkg/brew/nifi/) - Shares av.db curated category or tags: cli, data, data-pipelines, stream-processing.
- [apache-flink](https://www.automicvault.com/pkg/brew/apache-flink/) - Shares av.db curated category or tags: cli, data, stream-processing.
- [storm](https://www.automicvault.com/pkg/brew/storm/) - Shares av.db curated category or tags: cli, data, stream-processing.
- [topfew](https://www.automicvault.com/pkg/brew/topfew/) - Shares av.db curated category or tags: cli, data, stream-processing.
- [adios2](https://www.automicvault.com/pkg/brew/adios2/) - Shares av.db curated category or tags: cli, data.
- [alluxio](https://www.automicvault.com/pkg/brew/alluxio/) - Shares av.db curated category or tags: cli, data.
- [anyquery](https://www.automicvault.com/pkg/brew/anyquery/) - Shares av.db curated category or tags: cli, data.
- [apache-arrow](https://www.automicvault.com/pkg/brew/apache-arrow/) - Shares av.db curated category or tags: cli, data.
- [kapacitor](https://www.automicvault.com/pkg/brew/kapacitor/) - Local package facts share a topical domain. Shared terms: cli, data, processing, processor.
- [miller](https://www.automicvault.com/pkg/brew/miller/) - Both packages touch the same language runtime or ecosystem. Shared terms: cli, data, go, processing.

## Combined YAML source

View the package source record on GitHub. [combined/benthos.yml](https://github.com/automic-vault/db/blob/main/combined/benthos.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- package-page enrichment
- curated package history
- package version freshness
- av.db category and tag curation
- package relationship graph
- external package-manager database matches
- cross-ecosystem install command graph
