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
| Send2Bucket | EdgeMQ | |
|---|---|---|
| How you send | POST /v1/events (JSON) and OTLP over HTTP and gRPC | POST /v1/ingest (NDJSON or RecordIO) and MQTT over WSS/TLS |
| OpenTelemetry | Native OTLP endpoint | No OTLP |
| Buckets | S3, Google Cloud Storage, S3-compatible | Amazon S3 |
| Tables | Iceberg REST catalogs, S3 Tables, Supabase Analytics Buckets, DuckLake | None |
| Object format | gzip NDJSON with a per-record envelope | zstd WAL segments, raw Parquet, typed Parquet on Pro |
| Acknowledgement | After the batch is stored durably | After a durable write-ahead log fsync |
| Price | Plans and billing | Starter: 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
- OpenTelemetry. Logs, traces and metrics go to the same endpoint as events. See the API reference.
- Tables. Append to an Apache Iceberg catalog, S3 Tables or DuckLake instead of managing files.
- Other clouds. Deliver to Google Cloud Storage or an S3-compatible bucket such as R2 or MinIO.