Resource Limits
TagoIO implements multi-tenancy as a cost-effective resource-sharing approach. This architectural choice brings many benefits but requires mechanisms to avoid service disruptions when other users sharing resources have spikes in consumption. To prevent such scenarios, TagoIO limits the number of resources individuals can create in their accounts. When these limits are reached, creating additional resources will be blocked to maintain platform stability and prevent resource exhaustion.
Limits for each resource
The limits for each resource are determined by your specific plan. The table below shows the limits for each plan.
Most of the limits below are applied per Profile.
| Resource type / Plan | Free | Starter | Scale |
|---|---|---|---|
| Actions | 5 | 100 | 200 |
| Analysis | 5 | 100 | 200 |
| Dashboard | 5 | 100 | 1,000 |
| Entity | 5 | 50 | 80 |
| SQL Query | 3 | 15 | 50 |
| Device | 5 | 100 | 10,000 |
| Profile | 1 / account | 2 / account | 5 / account |
| Team Member | 0 | 1 | 5 |
| TagoCore | 10 | 10 | 10 |
| TagoCore Cluster | 3 | 3 | 3 |
| Custom Connector | 3 | 20 | 50 |
| Custom Network | 1 | 5 | 10 |
| Device service authorization | 10 | 50 | 200 |
| Secrets | 5 | 5 | 10 |
| Access Management Policies | 5 | 30 | 100 |
| Dictionary & Multi-language | 2 | 10 | 50 |
| Backup (daily creation limit) | N/A | 1 / day | 1 / day |
If you attempt to add additional resources after reaching your limit, a notification will be shown indicating that you have run out of available slots.
If your requirements exceed these limits, consider upgrading to the Scale plan or contacting us through support@tago.io. For more information about our plans and services, check our Pricing Page.
TagoSQL query limits
Beyond how many queries you can store, TagoSQL limits what a single query may do:
| Limit | Free | Starter | Scale |
|---|---|---|---|
| Versions kept per query | 1 | 5 | 25 |
| Parameters per query | 3 | 10 | 50 |
| Max joined tables | 1 (no JOINs) | 3 | 5 |
| Result row cap | 100 | 1,000 | 10,000 |
| Fleet devices per query | 10 | 50 | 100 |
| Fleet time window | 7 days | 30 days | 90 days |
| Query timeout | 5s | 15s | 30s |
The two fleet rows govern
multi-device queries (device_data_by_tag):
how many devices one request may target, and how far back its mandatory time bound may reach.
The result row cap never truncates a result silently. A query whose written LIMIT exceeds the cap is
rejected when you store it, and a query with no LIMIT whose result turns out larger fails when it runs.
OFFSET is not capped. See TagoSQL Errors for the exact messages.
Enterprise plans and TagoDeploy instances can have custom values. Your profile's effective numbers are
available on the profile limits endpoint (GET /profile/{id}/limits) under the sql group.
For how many requests per minute the /sql routes accept, see
Rate Limits.
Monitoring resources across your entire account
You can monitor the amount of resources you have used by accessing the profile menu in the top left corner of your Admin page and selecting the Hard Limits option.