Arroyo

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

  • Databases
  • Tools & Utilities
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

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

74/100 Good

Maintained
100last commit 15 days ago
Popular
745,077 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
70no serious findings, 14 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
5,077
Open issues
129
Last commit
2026-11-06
Latest release
v0.15.0
License
Apache-2.0
Activity
steady

Checked 14 days ago - source: GitHub (ArroyoSystems/arroyo)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the Arroyo CLI Run the install script on Mac or Linux to get the arroyo command. Without it, you can't launch or stop the cluster with arroyo start/stop. source
  • Start the cluster with Docker After installing, run arroyo start to launch a local Arroyo cluster in Docker. This starts the stream processor, so you need Docker installed and running or the command will fail. source
  • Use a TOML file for settings Put any needed settings in a TOML configuration file, such as checkpoint-url, controller scheduler, and database type. This tells Arroyo where to keep saved progress and which database it uses, so wrong values can break recovery or database connections. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

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.

Answers sourced from doc.arroyo.dev, www.arroyo.dev, www.reddit.com

Community

Collected 48 days ago - public community threads