Skip to main content

Send2Bucket vs EdgeMQ

EdgeMQ, in beta, and Send2Bucket are built the same way: a hosted HTTP endpoint with an API key, an acknowledgement after a durable write, and delivery into a bucket in your account through an IAM role with an external ID. They differ in protocols, destinations and output format.

Short answer: for JSON or MQTT into Amazon S3 as Parquet, EdgeMQ costs less per GB. Choose Send2Bucket for OpenTelemetry, for buckets outside AWS, or for Iceberg, S3 Tables and DuckLake tables.

At a glance​

Send2BucketEdgeMQ
How you sendPOST /v1/events (JSON) and OTLP over HTTP and gRPCPOST /v1/ingest (NDJSON or RecordIO) and MQTT over WSS/TLS
OpenTelemetryNative OTLP endpointNo OTLP
BucketsS3, Google Cloud Storage, S3-compatibleAmazon S3
TablesIceberg REST catalogs, S3 Tables, Supabase Analytics Buckets, DuckLakeNone
Object formatgzip NDJSON with a per-record envelopezstd WAL segments, raw Parquet, typed Parquet on Pro
AcknowledgementAfter the batch is stored durablyAfter a durable write-ahead log fsync
PricePlans and billingStarter: 10 GiB a month free, then $0.10/GiB. Pro: $49 a month plus $0.06/GiB

When EdgeMQ fits better​

  • Your devices speak MQTT.
  • You want Parquet objects, including typed Parquet, written for you.
  • Everything lands in Amazon S3 and price per GB decides it.

When Send2Bucket fits better​

Sources​