Skip to main content

Send2Bucket vs Cloudflare Pipelines

Cloudflare Basin Pipelines, formerly Cloudflare Pipelines, takes HTTP and Workers data, optionally transforms it with SQL, and writes JSON or Parquet files or Iceberg tables to R2 in your Cloudflare account. Send2Bucket writes events and OpenTelemetry data to buckets and catalogs on any cloud.

Short answer: if your data can live in R2, Pipelines is much cheaper per GB and adds SQL transforms. Choose Send2Bucket when you need native OTLP, or when data has to land in S3, Google Cloud Storage, S3 Tables, another Iceberg catalog or DuckLake.

At a glance​

Send2BucketCloudflare Basin Pipelines
How you sendPOST /v1/events (JSON) and OTLP over HTTP and gRPCHTTP endpoint, Workers binding, Logpush
OpenTelemetryNative OTLP endpointNo OTLP; an open-source Worker adapter, otlp2pipeline, exists
TransformsNone; records are delivered as sentSQL transforms
StorageS3, Google Cloud Storage, S3-compatible (including R2)R2
TablesIceberg REST catalogs, S3 Tables, Supabase Analytics Buckets, DuckLakeIceberg in Basin Catalog
Limits16 MiB per request after decompression5 MB per request, 20 pipelines per account
PricePlans and billingIngress free. JSON sink $0.03/GB, Parquet or Iceberg sink $0.06/GB, transforms $0.04/GB, 50 GB of each included. Needs the Workers Paid plan

When Pipelines fits better​

  • Your producers already run on Cloudflare Workers.
  • You want to filter or reshape records with SQL before they are stored.
  • Storing data in R2 and querying it with Cloudflare's tools is fine.

When Send2Bucket fits better​

Sources​