# Install bento with Homebrew, Nix

Fancy stream processing made operationally mundane. Version 1.20.0 via Homebrew; verified 2026-07-27. Also installable with nix: nix profile install nixpkgs#bento.

## Install

```sh
sudo av install brew:bento
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install bento
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#bento
```

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

## Package facts

- **Package key:** brew:bento
- **Package manager:** Homebrew
- **Version:** 1.20.0
- **Source summary:** Fancy stream processing made operationally mundane
- **Homepage:** <https://warpstreamlabs.github.io/bento/>
- **Repository:** <https://github.com/warpstreamlabs/bento>
- **Last updated:** 2026-07-27T15:08:19Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- bento (alias)

## Install behavior

- Bottle: not available

## Freshness

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

Bento is WarpStream Labs' fork of the original Benthos project line. Its repository description explicitly frames it as a fork of the original project before the license was changed, preserving the familiar declarative stream-processing workflow under a new package and executable name.

### Project history

The Bento GitHub repository was created in May 2024, with an early v0.0.3 release candidate published in June 2024. The README keeps the Benthos-style design: high-performance resilient stream processing, a single config file, connectors, processors, Bloblang mappings, metrics, tracing, and plugin APIs.

Bento's short history is therefore mostly a continuity story rather than an invention story: it keeps the pre-existing architecture and developer ergonomics while establishing a separate namespace, documentation site, container image, and Homebrew formula.

### Adoption history

Bento adoption is tied to users who wanted the Benthos workflow after the upstream licensing and branding split. Its package-manager presence lets existing teams choose the fork without learning a different pipeline model.

WarpStream's stewardship also matters for data-infrastructure users because WarpStream itself operates in the Kafka-compatible streaming space, making Bento a natural local connector and transformation tool around streaming deployments.

### How it is used

Bento is run with a config file, commonly as `bento -c ./config.yaml`, or as a container with a mounted YAML file. It can connect cloud services, Kafka, NATS, HTTP, databases, queues, and object stores while applying mappings, filters, enrichment, and batching.

For package users, Bento is attractive when they want a static local binary, a docker image, and a Go plugin surface without depending on the Redpanda Connect distribution.

### Why package nerds care

Bento is package-nerd significant because it is the fork name that makes the Benthos licensing and governance split visible in package indexes. The package tells you which side of the lineage you are installing.

Its relationship to brew:benthos is also useful metadata: both tools share concepts and much command-line culture, but Bento intentionally uses a separate executable and docs namespace.

### Timeline

- 2024-05: The warpstreamlabs/bento repository was created.
- 2024-06: Bento v0.0.3-rc1 was published.
- 2024: The README described Bento as a fork of the original project before the license change.
- 2026: The repository remained active with the Bento package identity.

### Related projects

- Benthos is the original project lineage.
- Redpanda Connect is the Redpanda-maintained successor/renaming around the same stream-processing family.
- Bloblang remains the mapping-language heritage shared by Bento-style pipelines.

### Sources

- <https://github.com/warpstreamlabs/bento>
- <https://github.com/warpstreamlabs/bento/releases/tag/v0.0.3-rc1>
- <https://warpstreamlabs.github.io/bento/docs/about>


## Security Notes

broad file, network, media, or database tool signal.

- **Geiger risk:** blue / medium
- broad file, network, media, or database tool signal

## Other Package-Manager Records

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


## Combined YAML source

View the package source record on GitHub. [combined/bento.yml](https://github.com/mxcl/pkgdb/blob/main/combined/bento.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph