Skip to main content

Plans and billing

Send2Bucket bills an organization for the bytes it accepts. Storage, requests and queries at your destination are billed to you by its provider.

Plans​

PlanPriceAllowance
Free$0100,000,000 bytes (100 MB) per organization per UTC calendar month. Hard cap.
Trial$07 days from activation, 10 GB in total. Once per organization, no card.
Paid$20 per organization per month50 GB included per billing period, then the per-GB rates below.
  • Free. A request that would take the month past 100 MB is rejected with 429 and a body showing remaining_bytes and resets_at. The counter resets at 00:00 UTC on the first of the month.
  • Trial. Reaching 10 GB pauses intake until you upgrade or the trial ends. At the end of the 7 days the organization returns to Free unless the owner upgrades. The Free monthly counter keeps running during the trial.
  • Paid. Upgrading starts a new billing period at once. Only bytes accepted after the upgrade count toward Paid usage.

Batches accepted before a cap or a plan change are still delivered. Streams, keys and delivery state carry over on upgrade.

Usage above the included 50 GB is charged at graduated rates. Each slice of the month's volume is charged at its own rate, and the included 50 GB counts toward the thresholds.

Ingested bytes in a billing periodPrice per GB
First 50 GBIncluded in $20
Above 50 GB through 1 TB$0.500
Next 9 TB$0.450
Next 90 TB$0.400
Above 100 TB$0.350
Monthly volumeInvoice
50 GB$20
1 TB$495
10 TB$4,545
200 TB$75,545

A request that crosses the 50 GB allowance is accepted in full; only the bytes above 50 GB are charged. Fractional gigabytes are charged exactly, with no rounding per request or per record. The invoice total is rounded to the cent when it is settled.

How bytes are counted​

Units are decimal: 1 GB is 1,000,000,000 bytes and 1 TB is 1,000 GB.

RequestCounted bytes
POST /v1/eventsThe decompressed UTF-8 request body. The bytes field of the response.
OTLP over HTTP or gRPC, all items acceptedThe decompressed protobuf request message. HTTP headers, TLS and gRPC framing are not counted.
OTLP with rejected itemsThe accepted subset, re-encoded as a protobuf message with its resource, scope and metric descriptors once.
A rejected request (4xx, 429, 503)0

These never change the count:

  • Gzip on the request. The same message with and without compression counts the same.
  • Compression of delivered objects and metadata written by table writers.
  • Send2Bucket's retries to your destination.

Usage is added up across all of an organization's streams, signals and destinations. A client that resends records is billed for each copy. The dashboard shows ingested bytes and record counts per signal for the current period.