warpstreamlabs/bento

Health v2 · maintenance only

Flags: no_license

Adoption not part of the score

2155 stars · 232 forks observed · 2026-10-03

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Bento is a high-performance, resilient stream processor written in Go that connects a wide range of sources and sinks (Kafka, Pub/Sub, Redis, SQL, cloud services, and more) while performing transformations, enrichments, and filtering via a declarative YAML config and the Bloblang mapping language. It is a community fork of Benthos maintained by WarpStream Labs, deployable as a static binary, Docker image, or serverless function with at-least-once delivery guarantees.

Use cases

• pipe kafka topics to redis streams with transformations
• enrich and filter messages between pub/sub systems
• build declarative etl pipelines from a single yaml config
• route messages to different sinks based on payload content
• transform payloads in a streaming pipeline
• connect aws sqs to gcp pub/sub
• run windowed aggregations over event streams
• replace custom glue scripts between message brokers

When to choose

• you need complex stateful stream processing like exactly-once semantics or SQL-style streaming joins at scale
• you want a visual drag-and-drop pipeline builder
• your use case is batch analytics rather than streaming message brokering

When to avoid

• you need exactly-once processing guarantees
• you require heavy stateful stream computations like large windowed joins or SQL streaming analytics
• you want a GUI-based pipeline builder rather than config files

Facets

application · maturity active

streaming etl message-queue serialization middleware big-data developer-tools windows go cross-platform self-hosted cloud stream-processing benthos-fork kafka data-pipelines bloblang connectors declarative-config event-driven data-engineering messaging automation linux macos docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="warpstreamlabs/bento")