Why they built it
At Lyft, streaming powered pricing, ETAs, safety and real-time ML but required specialists, and Micah Wylde estimated only two or three of roughly 100 supported engineers became self-sufficient with Flink. He described frustration trying to use Flink after seeing operational failures including a broadcast-state bug that grew into terabytes of state and required days of recovery. The founders thought a Rust engine built on DataFusion with SQL as the first-class language, plus checkpointing and recovery and managed scaling without operating Flink, was worth building.
How it ended
Arroyo did not fail; it ended as an independent company when Cloudflare completed its acquisition on April 10, 2025. Cloudflare gained a stateful SQL layer that fit its R2, Queues, Workers and Data Platform, launching Pipelines ingestion in beta with transformations to follow. Price, consideration, retention terms, revenue and multiple remain undisclosed, and Cloudflare shipped Pipelines SQL transformations in September 2025.
What went wrong
Most important first.
- 1
Entrenched streaming incumbents Competition
Arroyo competed with Flink, Spark Streaming, Kafka Streams, Materialize, RisingWave, Tinybird and ksqlDB with a disadvantage in maturity and small commercial footprint.
- 2
Unproven standalone commercial scale Monetization
No reliable revenue, contract value, retention or serviceable-market estimate was found, and Wylde's claim of dozens of companies running pipelines had no disclosed named customers or volumes.
- 3
Thin financing record Capital
Financing evidence is limited to an Employbl report of a $500,000 YC pre-seed with no primary announcement confirmed, and no ARR, margins, burn, runway or valuation was found.
What could be different today
- Cloudflare Pipelines now exists as a buyer platform, launching ingestion in beta in April 2025 and SQL filtering and transformation with exactly-once delivery to R2 as Iceberg tables or Parquet files in September 2025.
- Cloudflare's interface still exposes "Validate Arroyo SQL" without public evidence promising full engine parity, creating a concrete migration boundary from Arroyo to Pipelines.
- The Apache-licensed Rust and DataFusion Arroyo engine remains inspectable with roughly 5,000 stars and continued 2026 pull requests, plus version 0.5 exactly-once Parquet and JSON delivery to object storage.
