Limits
Limits are tied to your plan and enforced on the backend. Numeric values are listed in the feature comparison and plans.
What limits exist
| Limit | What's counted | Period | When exceeded |
|---|---|---|---|
Ad accounts (max_ad_accounts) | Connected ad accounts across limited sources for your plan | Point-in-time | You can't add an account beyond the limit — an upgrade or disconnect is needed |
CRM workspaces (max_crm_workspaces) | Active CRM connections/workspaces | Point-in-time | New CRM connections are blocked |
Projects (max_projects) | Projects on the account | Point-in-time | Creating a project is blocked |
| Seats | Owner + invited members | Point-in-time | Invites are blocked; on Solo+ you can buy extra seats (+$15) |
Schedules (max_schedules) | Active schedule jobs | Point-in-time | New schedules can't be created (scheduling is disabled on Free) |
Runs (max_runs_month) | Manual and automatic report runs | Calendar month | New runs are rejected until the period resets |
Rows (max_rows_month) | Rows written by reports | Calendar month | Writing stops / the run fails with a plan-limit error |
AI asks (max_ai_asks_month) | Requests to the AI assistant | Calendar month | Asks are blocked (on Agency Pro — soft cap with unlimited summaries) |
| Lookback | How far back a request can query | Per request | Free is limited to 30 days |
What's not in the limits model
- There's no separate "number of reports" limit as a hard catalog quota (runs/rows/schedules are the quotas)
- There's no "Yandex.Direct" limit — that connector doesn't exist in the product
- AI is not limited "per day" — the counter is monthly
Schedule frequencies by plan
| Plan | Available frequencies |
|---|---|
| Free | — |
| Solo | daily, weekly |
| Agency / Agency Pro | hourly, daily, weekly |
How to increase your limits
- Move to a higher plan — changing plans
- Buy additional seats — adding seats
- For Agency Pro / custom terms — contact support