Harness · Rate Limits
Harness Rate Limits
Harness does not publish a single consolidated API rate-limit table at a public URL. Limits are governed at the platform level per account, with documented capacity ceilings on concurrent pipeline executions per plan (60 on Essentials, 500 on Enterprise). Specific per-second request-rate numbers are not publicly disclosed; raise via support.
4 Limits
Throttle: 429
DevOpsGitOpsInternal Developer PortalLifecycleSoftware DeliveryRate LimitingQuotasThrottling
Limits
Free Tier (Harness Open Source / Litmus Chaos) account
see Harness support / API reference
Essentials Concurrent Pipelines account
60
Enterprise Concurrent Pipelines account
500
Enterprise Code Repository Storage account
250
Policies
Backoff Strategy
Clients should implement exponential backoff with jitter and honor the Retry-After header on 429 responses.
Account Scoping
Limits are enforced per Harness account, not per individual API key.
Plan-based Capacity
Concurrent pipeline ceilings are tied to the account's plan tier (Essentials or Enterprise); raises require plan upgrade or sales engagement.
Fair Use
Even on Enterprise, sustained traffic that materially impacts shared infrastructure may be subject to fair-use throttling.