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.

Harness Rate Limits is the machine-readable rate-limit profile for Harness on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, across the free, essentials, and enterprise tiers, measuring requests_per_minute, concurrent_executions, and gb_total.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.

Tagged areas include DevOps, GitOps, Internal Developer Portal, Lifecycle, and Software Delivery.

4 Limits Throttle: 429
DevOpsGitOpsInternal Developer PortalLifecycleSoftware DeliveryRate LimitingQuotasThrottling

Limits

Free Tier (Harness Open Source / Litmus Chaos) account
requests_per_minute
see Harness support / API reference
Essentials Concurrent Pipelines account
concurrent_executions · usage
60
Enterprise Concurrent Pipelines account
concurrent_executions · usage
500
Enterprise Code Repository Storage account
gb_total · usage
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.

Sources