Quotas & limits
This page lists the quotas and limits that apply to a workspace. Limits scale with your plan; most can be raised on request.
Limits by plan
The figures below are the standard defaults for each plan. They are starting points, not hard caps, see Raising a limit.
| Limit | Starter | Growth | Enterprise |
|---|---|---|---|
| Concurrent runs | 3 | 20 | Custom |
| Workspace members | 10 | 100 | Unlimited |
| Connected repositories | 25 | 250 | Unlimited |
| Custom agents | 5 | 50 | Unlimited |
| Private MCPs | 5 | 50 | Unlimited |
| Audit retention | 90 days | 1 year | Up to 7 years |
API rate limits
The REST API is rate-limited per workspace. Every response carries X-RateLimit-Remaining and X-RateLimit-Reset headers; an exceeded limit returns HTTP 429. See the API reference for the per-plan request budgets and retry guidance.
Run limits
| Limit | Description |
|---|---|
concurrent_runs | Runs executing at once. Additional triggered runs queue until a slot frees. |
run_duration | Wall-clock ceiling for a single run. A run that exceeds it fails cleanly. Default 6 hours. |
gate_timeout | How long a run waits at an approval gate before timing out. Configurable; default 24 hours. |
run_cost | No default ceiling. Set a cap per run with --max-cost or workspace-wide via a policy. |
Retention windows
Audit events and cost data share a retention window, configurable per workspace within the bounds your plan allows. Run logs are retained for the same window. Time-travel snapshots are kept as long as the run's audit trail exists, so any retained run can still be replayed. See Audit log for details.
Raising a limit
Most limits are soft. If you are approaching one, request an increase from Workspace Settings > Plan & limits, or contact your account team. Enterprise workspaces are configured to the limits agreed during onboarding.