---
title: "Introduction"
description: "Arroyo Stream Processing Engine"
---

> Documentation Index
> Fetch the complete documentation index at: https://www.arroyo.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

[Arroyo](https://arroyo.dev) is a distributed stream processing engine, designed to efficiently
perform stateful computations on streams of data. Unlike traditional batch processors, streaming engines can operate
on both bounded and unbounded sources, emitting results as soon as they are available.

In short: Arroyo lets you ask complex questions of high-volume real-time data with sub-second results.

![Arroyo](https://www.arroyo.dev/docs/images/header_image.png)

Arroyo is fully open-source under the Apache 2.0 license and designed for
self-hosting. It can be deployed in a [variety of ways](https://www.arroyo.dev/docs/docs/deployment), including
to Kubernetes, serverless runtimes, and VMs.

Arroyo development is sponsored by [Cloudflare](https://www.cloudflare.com). If
you are looking for a managed Arroyo experience, see [Basin
Pipelines](https://developers.cloudflare.com/basin-pipelines/).

## Features

- Pipelines defined in SQL, with support for complex analytical queries
- Scales up to tens of millions of events per second
- Stateful operations like windows and joins
- State checkpointing for fault-tolerance and pipeline recovery
- Event time processing with watermark support
- Low-latency streaming ingestion into Iceberg and other table formats

## Use cases

Some example use cases include:

- Detecting fraud and security incidents
- Real-time product and business analytics
- Real-time ingestion into your data warehouse or data lake
- Real-time ML feature generation

## Why Arroyo

There are already a number of existing streaming engines out there, including [Apache Flink](https://flink.apache.org),
[Spark Streaming](https://spark.apache.org/docs/latest/streaming-programming-guide.html), and
[Kafka Streams](https://kafka.apache.org/documentation/streams/). Why create a new one?

- **Serverless operations**: Arroyo pipelines are designed to run in modern cloud environments, supporting seamless scaling,
  recovery, and rescheduling
- **High performance SQL**: SQL is a first-class concern, with consistently excellent performance
- **Designed for everyone**: Arroyo cleanly separates the pipeline APIs from its internal implementation. You don't
  need to be a streaming expert to build real-time data pipelines.

## Getting Started

Arroyo ships as a single binary, which can be easily installed locally or run in a container.

### MacOS

```shellsession
brew install arroyosystems/tap/arroyo
```

### Linux

```shellsession
curl -LsSf https://arroyo.dev/install.sh | sh
```

### Docker

```shellsession
docker run -p 5115:5115 \
      ghcr.io/arroyosystems/arroyo:latest
```

### Kubernetes

```shellsession
helm repo add arroyo https://helm.arroyo.dev
helm install arroyo arroyo/arroyo
```

See the [getting started guide](https://www.arroyo.dev/docs/getting-started) to get up and running with a local Arroyo deployment.


### In production

Arroyo supports several deployment targets for production use, including native support for Kubernetes. See the
[deployment docs](https://www.arroyo.dev/docs/deployment) for more information.

## License

Arroyo is fully open-source under the [Apache 2.0 license](https://github.com/ArroyoSystems/arroyo/tree/master/LICENSE-apache).

## Community support

Community support is offered via the [Arroyo Discord](https://discord.gg/cjCr5rVmyR) where the Arroyo development
team and community are actively engaged in helping users get started and solve their problems with Arroyo.

## Telemetry

By default, Arroyo collects limited and anonymous usage data to help us
understand how the system is being used and to help prioritize future
development.

You can opt out of telemetry by setting `DISABLE_TELEMETRY=true` when running
Arroyo services.

Source: https://www.arroyo.dev/docs/index.mdx
