Limits

Tinybird has limits on certain operations and processes to ensure the highest performance.

Free plan limits

Organizations on the Free plan have the following limits:

  • 1k queries per day in total for all Workspaces in the Organization. Applies to API Endpoints and Query API calls.
  • 10 queries per second (QPS) limit. Applies to API Endpoints and Query API calls. Your operations can take x2 QPS per second allowed in you plan for API endpoint requests or SQL queries. See Burst mode.
  • 10 GB storage, including all Data Sources from all Workspaces.
  • 0.5 vCPU limit, limiting the concurrency but not the total active minutes. See Active minutes.
  • Sinks are not available on the Free plan.

If you reach the limits, you will receive an email notification. See Email notifications.

See Free plan for more information.

Developer plan limits

Depending on the size of your Developer plan, the following limits apply:

  • You can't exceed the vCPU time limit. The limit relates to vCPU time used during a minute. Tinybird allows usage bursts of 2x the vCPU time per minute. If you reach the vCPU limit you're allowed 75% of the QPS limit of your plan size during the next 5 minutes. See Burst mode.
  • You can't exceed the queries per second limit (QPS). This limit relates to API Endpoints and queries. Your operations can take x2 QPS per second allowed in you plan for API endpoint requests or SQL queries. See Burst mode.
  • If you exceed the active minutes in your plan, additional minutes are billed at a fixed rate per minute. See the Pricing page for more information.

Limits are applied at the organization level, so all Workspaces in an Organization share the same limits. If you reach the limits, you will receive an email notification. See Email notifications.

See Developer plan for more information.

Enterprise plan limits

Enterprise plans limits depend on the infrastructure type: shared or dedicated.

Shared infrastructure

Enterprise plans starting at 4 vCPUs on shared infrastructure have the same limits as the Developer plans.

  • You can't exceed the vCPU time limit. The limit relates to vCPU time used during a minute. Tinybird allows usage bursts of 2x the vCPU time per minute. If you reach the vCPU limit you're allowed 75% of the QPS limit of your plan size during the next 5 minutes. See Burst mode.
  • You can't exceed the queries per second limit (QPS). This limit relates to API Endpoints and queries. Your operations can take x2 QPS per second allowed in you plan for API endpoint requests or SQL queries. See Burst mode.
  • If you exceed the active minutes in your plan, additional minutes are billed at a fixed rate per minute. See the Pricing page for more information.

Limits are applied at the organization level, so all Workspaces in an Organization share the same limits. If you reach the limits, you will receive an email notification. See Email notifications.

Dedicated infrastructure

Enterprise plans with dedicated infrastructure have no predefined limits. The only limits are the ones related to the underlying infrastructure and available capacity.

See Rate limiter for more information on rate limiting in dedicated infrastructure plans.

Email notifications

When reaching or temporarily exceeding your plan's limits, you will receive one of the following emails.

Free plans

The following table shows the limits' notifications you might receive for the Free plan.

LimitWarning emailAlert email
vCPU usage (1/2 vCPU)Triggered after 3 minutes at 150-200% usage in last 30 minutes.Triggered after 1 minute at >200% usage in last 30 minutes.
Queries Per Second (10 QPS)Triggered after 30 seconds at >75% of limit in last 30 minutes.Triggered after 30 seconds at >100% of limit in last 30 minutes.
Active minutesUsed more than 75% of allocated minutes.Used more than 100% of allocated minutes.
Storage UsageUsed more than 75% of allocated storage.Used more than 100% of allocated storage.
Requests per day (1,000 queries)Used more than 75% of daily query limit.Used more than 100% of daily query limit.

Developer and shared plans

The following table shows the limits' notifications you might receive for plans on shared infrastructure.

LimitWarning emailAlert email
vCPU usageTriggered after 3 minutes at 150-200% usage in last 30 minutes.Triggered after 1 minute at >200% usage in last 30 minutes.
Queries Per SecondTriggered after 30 seconds at >75% of limit in last 30 minutes.Triggered after 30 seconds at >100% of limit in last 30 minutes.
Active minutesUsed more than 75% of allocated minutes.Used more than 100% of allocated minutes.
Storage UsageUsed more than 75% of allocated storage.Used more than 100% of allocated storage.

Workspace limits

The following limits apply to all workspaces in an organization, regardless of the plan.

Description Limit
Number of Workspaces90 Workspaces. Soft limit, contact support to increase it.
Number of seats90 seats. Soft limit, contact support to increase it.
Number of branches, including mainDefault 4. Soft limit, contact support to increase it.
Number of Data Sources100 Data Sources. Soft limit, contact support to increase it.
Number of Copy Pipes10 Pipes. Soft limit, contact support to increase it.
10 Pipes. Soft limit, contact support to increase it.
Number of Tokens100,000 tokens. If you need more you should take a look at JWT tokens)
Number of secrets100 secrets.

See Rate limits for JWTs for more detail specifically on JWT limits.

Ingestion limits

The following ingestion limits apply to all workspaces in an organization, regardless of the plan.

Description Limit
Data Source max columns500
Full body upload8 MB
Multipart upload - CSV and NDJSON500 MB
Multipart upload - Parquet50 MB
Max file size - Parquet - Free plan1 GB
Max file size - Parquet - Developer and Enterprise plan5 GB
Max file size (uncompressed) - Free plan10 GB
Max file size (uncompressed) - Developer and Enterprise plan32 GB
Kafka topicsDefault is 5. Soft limit, contact support to increase it.
Max parts created at once - NDJSON/Parquet jobs and Events API12 parts

Ingestion limits (API)

Tinybird throttles requests based on the capacity. So if your queries are using 100% resources you might not be able to run more queries until the running ones finish.

DescriptionLimit and time window
Request size - Events API10 MB
Response size100 MB
Create Data Source from schema25 times per minute
Create Data Source from file or URL*5 times per minute
Append data to Data Source*5 times per minute
Append data to Data Source using v0/events1,000 times per second
Replace data in a Data Source*5 times per minute
  • The quota is shared at Workspaces level when creating, appending data, or replacing data. For example, you can't do 5 requests of each type per minute, for a total of 15 requests. You can do at most a grand total of 5 requests of those types combined.

The number of rows in append requests doesn't impact the ingestion limit; each request counts as a single ingestion.

If you exceed your rate limit, your request is throttled and you receive HTTP 429 Too Many Requests response codes from the API. Each response contains a set of HTTP headers with your current rate limit status.

Header NameDescription
X-RateLimit-LimitThe maximum number of requests you're permitted to make in the current limit window.
X-RateLimit-RemainingThe number of requests remaining in the current rate limit window.
X-RateLimit-ResetThe time in seconds after the current rate limit window resets.
Retry-AfterThe time to wait before making a another request. Only present on 429 responses.

BigQuery Connector limits

The import jobs run in a pool, with capacity for up to 2 concurrent jobs. If more scheduled jobs overlap, they're queued.

DescriptionLimit and time window
Maximum frequency for the scheduled jobs5 minutes
Maximum rows per append or replace50 million rows. Exports that exceed this number of rows are truncated to this amount

You can't pause a Data Source with an ongoing import. You must wait for the import to finish before pausing the Data Source.

DynamoDB Connector limits

DescriptionLimit and time window
Storage500 GB
Throughput250 Write Capacity Units (WCU), equivalent to 250 writes of at most 1 KB per second

Query limits

The following query limits apply to all workspaces in an organization, regardless of the plan.

Description Limit
SQL length8KB
Result length100 MB
Query execution time10 seconds

If you exceed your rate limit, your request will be throttled and you will receive HTTP 429 Too Many Requests response codes from the API. Each response contains a set of HTTP headers with your current rate limit status.

Header NameDescription
X-RateLimit-LimitThe maximum number of requests you're permitted to make in the current limit window.
X-RateLimit-RemainingThe number of requests remaining in the current rate limit window.
X-RateLimit-ResetThe time in seconds after the current rate limit window resets.
Retry-AfterThe time to wait before making a another request. Only present on 429 responses.

Query timeouts

If query execution time exceeds the default limit of 10 seconds, an error message appears. Long execution times hint at issues that need to be fixed in the query or the Data Source schema.

To avoid query timeouts, optimize your queries to remove inefficiencies and common mistakes. See Optimizations for advice on how to detect and solve issues in your queries that might cause timeouts.

If you still need to increase the timeout limit, contact support. See Get help.

Only paid accounts can raise the timeout limit.

Publishing limits

The following publishing limits apply to all workspaces in an organization, regardless of the plan.

Materialized Views limits

No numerical limits, certain operations are inadvisable when using Materialized Views.

Sink limits

Sink Pipes have the following limits:

DescriptionLimit
Execution time300s
FrequencyUp to every minute
Memory usage per query10 GB
Active jobs (running or queued)6

Copy Pipe limits

Copy Pipes have the following limits:

DescriptionLimit
Execution time50% of the scheduling period, max
FrequencyUp to every minute
Active jobs (running or queued)6

Delete limits

Delete jobs have the following limits:

DescriptionLimit
Active delete jobs per Workspace6

Legacy billing

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

Sink limits (Legacy)

Sink Pipes have the following limits, depending on your billing plan:

PlanSink Pipes per WorkspaceExecution timeFrequencyMemory usage per queryActive jobs (running or queued)
Pro330sUp to every 10 min10 GB3
Enterprise10300sUp to every minute10 GB6

Copy Pipe limits (Legacy)

Copy Pipes have the following limits, depending on your billing plan:

PlanCopy Pipes per WorkspaceExecution timeFrequencyActive jobs (running or queued)
Build120sOnce an hour1
Pro330sUp to every 10 minutes3
Enterprise1050% of the scheduling period, 30 minutes maxUp to every minute6

Delete limits (Legacy)

Delete jobs have the following limits, depending on your billing plan:

PlanActive delete jobs per Workspace
Build1
Pro3
Enterprise6

Next steps

Updated