Limits & quotas
Your plan sets caps on runs and connected repos, and the cloud control plane applies rate limits to protect the service. This page explains each limit and the error you'll see when you reach it.
Run quotas
The Free plan is capped at 10 runs per calendar month; the counter resets at the start of each month. Paid plans run unlimited runs. Exceeding the run cap returns run_quota_exceeded — upgrade or wait for the next calendar month.
| Plan | Runs |
|---|---|
| Free | 10 / calendar month |
| Solo | Unlimited |
| Team | Unlimited |
| Enterprise | Unlimited |
Repo quotas
The number of connected repositories is capped per plan: Free allows 1 repo, Solo allows 5, and Team and Enterprise are unlimited. Connecting beyond your cap returns repo_quota_exceeded. Disconnect a repo or upgrade to raise the cap.
| Plan | Repos |
|---|---|
| Free | 1 |
| Solo | 5 |
| Team | Unlimited |
| Enterprise | Unlimited |
Rate limits
The cloud control plane rate-limits requests at roughly 60–120 requests per minute depending on the route. Crossing that threshold returns rate_limited. In normal use you should never hit this; if you do, it usually points to an integration problem. If you are deliberately load-testing, contact support@pipemason.com first.
Quota errors
| Error | Meaning |
|---|---|
run_quota_exceeded | You reached your plan's run cap (Free: 10 / calendar month). Upgrade or wait for the next month. |
repo_quota_exceeded | You reached your plan's connected-repo cap. Disconnect a repo or upgrade. |
rate_limited | Too many requests in a short window (~60–120 req/min). Back off and retry; contact support if it persists. |
Note
--max-cost and the model-tier ceiling) are configured locally — see CLI flags and .pipeline/config.yml.