Billing¶

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:

Active minutes¶

Developer plans bill vCPU usage using active minutes. An active minute is when any operation used a vCPU for a minute. When using fractioned vCPUs, an active minute is proportional to the fraction, for example 30 seconds of ½ vCPU.

Plan sizes come with a number of active hours, which is the number of active minutes you can use divided by 60. If you consume all your active minutes, the overage is billed at a fixed rate per minute. See the Pricing page for more information.

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:

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 receive an email indicating the affected Pipe endpoints and the concurrency limit.

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.

Data ingestion (Legacy)¶

Data manipulation (Legacy)¶

Data transfer (Legacy)¶

See also¶

• Explore different Tinybird plans.
• Sign up for a free Tinybird account and follow the quick start.
• Learn more about using the Playground and Time Series.