# Arroyo

Arroyo is a distributed stream processing engine for building real-time, stateful SQL pipelines over high-volume data streams. It is open source and self-hosted, installable on Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/4863/arroyo

## Description

Arroyo is a distributed stream processing engine for building real-time, stateful SQL pipelines over high-volume data streams.

## Platform availability

Available on 1 of 10 platforms: Helm.

## Health score

74/100 (Good), based on 4 of 5 factors.
- Maintained: 100 (last commit 15 days ago)
- Popular: 74 (5,077 GitHub stars)
- Easy to install: 25 (1 install platform, install notes)
- Security check: 70 (no serious findings, 14 minor, CI, tests)

## Links

- GitHub: https://github.com/ArroyoSystems/arroyo
- Documentation: https://github.com/arroyosystems/arroyo-docs
- Official website: https://arroyo.dev
- Kubernetes (Helm): https://artifacthub.io/packages/helm/arroyo/arroyo

## Common questions

### Is a single-node Arroyo cluster suitable for production?

No. The documentation says a single-node cluster is useful for testing and development, but it is not suitable for production. It describes running a production-ready distributed cluster using Arroyo's built-in scheduler or Kubernetes.

### Does Arroyo require a stateful deployment model?

Arroyo is described as a stateful stream processing engine that behaves like a stateless one.

### Can Arroyo scale from simple container runtimes to large Kubernetes deployments?

Yes. It is built for elastic cloud environments, from simple container runtimes such as Fargate to large, distributed Kubernetes deployments.

### What proprietary-system concern is mentioned in the community discussion?

The discussion says that reliance on a proprietary system was a serious concern. It notes that open-sourcing with Apache/MIT licensing will help advocate for it internally.

---
Source: Our Local Host (https://ourlocalhost.com/app/4863/arroyo), the self-hosted and open-source app directory.
