Understand your bill

If you are on a paid plan, read on to learn how billing works for each plan. See Tinybird plans for information on each plan's features.

To learn about the prices of each plan, see Pricing.

Developer plans

Developer plans come in many sizes, depending on the compute resources you need. Each size includes a base capacity for your organization, which is a fixed amount you pay for. Other items are billed according to usage beyond a threshold.

Developer plans billing is calculated from the following resources:

ResourceBillingType
vCPUsNumber of vCPUs available. More than 3 vCPUs require an Enterprise plan. Each vCPU size includes a number of active minutes.Fixed.
Active minutesAn active minute is when any operation used a vCPU for a minute. See Active minutes.Usage based.
Queries per second (QPS)Number of queries per second (QPS). Each vCPU size includes a QPS allowance. See Queries per second.Usage based when usage exceeds the QPS included in the plan.
StorageAverage of daily maximum usage of the compressed disk storage of all your data, in gigabytes.Usage based when usage exceeds the 25 GB included in the plan.
Data transferWhen using Sinks, usage is billed depending on the destination, which can be the same cloud provider and region as your Tinybird cluster, or a different one.Usage based.

Self service

After you enter your credit card details, you can pick whatever size you want for your Developer plan, with up to 3 vCPUs supported. You can resize your plan every 24 hours. See Resize and upgrade.

To use more than 3 vCPUs, you need to sign up to an Enterprise plan. See Enterprise plans.

Periodicity

Developer plans are billed monthly. Each monthly invoice contain fixed costs and usage-based costs calculated from the previous period.

The billing period starts on the subscription date.

Enterprise plans

Enterprise plans provide plans greater than 3 vCPUs. The size of each plan determines the fixed amount you pay for. Other items are billed according to usage beyond a threshold.

Enterprise plans start at 4 vCPUs of capacity and have a minimum storage of 1 terabyte. Resizing requires contacting sales.

Plans with dedicated compute resources are also available. Contact Tinybird support at support@tinybird.co to learn more.

What are credits?

Enterprise billing is based on credits. A credit is a unit of resource usage. You can acquire and spend credits across the entire Tinybird offering, regardless of the region or feature.

Credits provide a predictable, consistent, and easy to track way of paying for Tinybird services. Instead of committing to specific features or an amount of resources, you commit to spending a number of credits over at least a 12 months period. You can spend credits on storage, compute, support, and so on.

Credits usage

The following table shows how Tinybird calculates credits usage for each resource:

ResourceBillingType
vCPUsNumber of vCPUs available. Each vCPU size includes a number of active minutes.Fixed.
Active minutesAn active minute is when any operation used a vCPU for a minute. See Active minutes.Usage based.
Queries per second (QPS)Number of queries per second (QPS). Each vCPU size includes a QPS allowance. See Queries per second.Usage based when usage exceeds the QPS included in the plan.
StorageAverage of daily maximum usage of the compressed disk storage of all your data, in gigabytes.Usage based when usage exceeds the storage included in the plan.
Data transferWhen using Sinks, usage is billed depending on the destination, which can be the same cloud provider and region as your Tinybird cluster, or a different one.Usage based.
SupportPremier or Enterprise monthly support fee.Fixed.
Private LinkPrivate connection. Optional. Billed monthly.Usage based.

Periodicity

Enterprise plans are billed every month according to the amount of credits you've used. The billing cycle starts on the first day of the month and ends on the last day of the month.

Track invoices

In Enterprise plans, invoices are issued upon credits purchase, which can happen when signing the contract or when purchasing additional credits. You can check your invoices from the customer portal.

Monitor usage

You can monitor credits usage, including remaining credits, cluster usage, and current commitment through your organization's dashboard. See Enterprise infrastructure monitoring. You can also check usage using the monthly usage receipts.

Rate limiter

The rate limiter monitors the status of the cluster and limits the number of concurrent requests to prevent the cluster from crashing due to insufficient memory. This allows the cluster to continue working, albeit with a rate limit.

The rate limiter activates when the following situation occurs:

  • When total memory usage in a host in the cluster is over 70% in clusters with less than 64GB of memory per host and 80% in the rest.
  • Percentage of 408 Timeout Exceeded and 500 Internal Server Error due to memory limits for a Pipe endpoint exceeds 10% of the total requests.

If both conditions are met, the maximum number of concurrent requests to the Pipe endpoint is limited proportionally to the percentage of errors. Workspace administrators in dedicated infrastructure receive an email indicating the affected Pipe endpoints and the concurrency limit.

The rate limiter rolls back after 5 minutes and it's activated again if the previously described conditions repeat.

For example, if a Pipe endpoint is receiving 10 requests per second and 5 failed during a high memory usage scenario due to a timeout or memory error, the number of concurrent queries is limited to a half, that is, 5 concurrent requests for that specific Pipe endpoint.

While the Rate limiter is active, endpoints return a 429 HTTP status code. You can retry those requests using a backoff mechanism. For example, you can space requests 1 second between each other.

Legacy billing

The following tables provide details on how each operation is billed in Legacy plans.

See also