Install benthos with Homebrew, Nix

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• benthos

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