Announcing Cloudflare K2: serverless event streams

Cloudflare has launched K2 in public beta, a serverless durable event-streaming service designed to decouple data producers from consumers, retain events during downstream outages, and support both parallel work distribution and pub/sub fan-out patterns. Built initially as an edge buffering layer for Basin Pipelines, K2 stores ordered, partitioned logs on Cloudflare R2 object storage, using R2’s durability and consistency to simplify coordination while allowing compute and storage to scale independently. Events are accumulated into segments before being written to R2, resulting in approximately one second of 99th-percentile produce latency in the initial release. K2 differs from Cloudflare Queues by focusing on high-volume batch processing, long-term retention, and multiple consumers rather than per-message retries and work-item controls, while Pipelines is recommended for direct transformation and storage into R2 or Iceberg tables. Users can create streams through Cloudflare tools and APIs, produce byte-based events through HTTP or Workers bindings, and consume leased batches through subscriptions that can be acknowledged, rejected, or extended. During the beta, K2 is available to Workers Paid subscribers without charge under limits including 10 GB of storage and 30 MB/s production per stream, with planned future capabilities such as greater write throughput, key-based ordering, push consumers, lower-latency tiers, and Kafka client compatibility.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.