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.
| Limit | Warning email | Alert 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 minutes | Used more than 75% of allocated minutes. | Used more than 100% of allocated minutes. |
| Storage Usage | Used 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.
| Limit | Warning email | Alert email |
|---|---|---|
| vCPU usage | 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 | 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 minutes | Used more than 75% of allocated minutes. | Used more than 100% of allocated minutes. |
| Storage Usage | Used 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 Workspaces | 90 Workspaces. Soft limit, contact support to increase it. |
| Number of seats | 90 seats. Soft limit, contact support to increase it. |
Number of branches, including main | Default 4. Soft limit, contact support to increase it. |
| Number of Data Sources | 100 Data Sources. Soft limit, contact support to increase it. |
| Number of Copy Pipes | 10 Pipes. Soft limit, contact support to increase it. |
| 10 Pipes. Soft limit, contact support to increase it. | |
| Number of Tokens | 100,000 tokens. If you need more you should take a look at JWT tokens) |
| Number of secrets | 100 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 columns | 500 |
| Full body upload | 8 MB |
| Multipart upload - CSV and NDJSON | 500 MB |
| Multipart upload - Parquet | 50 MB |
| Max file size - Parquet - Free plan | 1 GB |
| Max file size - Parquet - Developer and Enterprise plan | 5 GB |
| Max file size (uncompressed) - Free plan | 10 GB |
| Max file size (uncompressed) - Developer and Enterprise plan | 32 GB |
| Kafka topics | Default is 5. Soft limit, contact support to increase it. |
| Max parts created at once - NDJSON/Parquet jobs and Events API | 12 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.
| Description | Limit and time window |
|---|---|
| Request size - Events API | 10 MB |
| Response size | 100 MB |
| Create Data Source from schema | 25 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/events | 1,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 Name | Description |
|---|---|
X-RateLimit-Limit | The maximum number of requests you're permitted to make in the current limit window. |
X-RateLimit-Remaining | The number of requests remaining in the current rate limit window. |
X-RateLimit-Reset | The time in seconds after the current rate limit window resets. |
Retry-After | The 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.
| Description | Limit and time window |
|---|---|
| Maximum frequency for the scheduled jobs | 5 minutes |
| Maximum rows per append or replace | 50 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¶
| Description | Limit and time window |
|---|---|
| Storage | 500 GB |
| Throughput | 250 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 length | 8KB |
| Result length | 100 MB |
| Query execution time | 10 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 Name | Description |
|---|---|
X-RateLimit-Limit | The maximum number of requests you're permitted to make in the current limit window. |
X-RateLimit-Remaining | The number of requests remaining in the current rate limit window. |
X-RateLimit-Reset | The time in seconds after the current rate limit window resets. |
Retry-After | The 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:
| Description | Limit |
|---|---|
| Execution time | 300s |
| Frequency | Up to every minute |
| Memory usage per query | 10 GB |
| Active jobs (running or queued) | 6 |
Copy Pipe limits¶
Copy Pipes have the following limits:
| Description | Limit |
|---|---|
| Execution time | 50% of the scheduling period, max |
| Frequency | Up to every minute |
| Active jobs (running or queued) | 6 |
Delete limits¶
Delete jobs have the following limits:
| Description | Limit |
|---|---|
| Active delete jobs per Workspace | 6 |
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:
| Plan | Sink Pipes per Workspace | Execution time | Frequency | Memory usage per query | Active jobs (running or queued) |
|---|---|---|---|---|---|
| Pro | 3 | 30s | Up to every 10 min | 10 GB | 3 |
| Enterprise | 10 | 300s | Up to every minute | 10 GB | 6 |
Copy Pipe limits (Legacy)¶
Copy Pipes have the following limits, depending on your billing plan:
| Plan | Copy Pipes per Workspace | Execution time | Frequency | Active jobs (running or queued) |
|---|---|---|---|---|
| Build | 1 | 20s | Once an hour | 1 |
| Pro | 3 | 30s | Up to every 10 minutes | 3 |
| Enterprise | 10 | 50% of the scheduling period, 30 minutes max | Up to every minute | 6 |
Delete limits (Legacy)¶
Delete jobs have the following limits, depending on your billing plan:
| Plan | Active delete jobs per Workspace |
|---|---|
| Build | 1 |
| Pro | 3 |
| Enterprise | 6 |
Next steps¶
- Understand how Tinybird plans and billing work.
- Explore popular use cases for user-facing analytics (like dashboards) in Tinybird's Use Case Hub.