Alation · Rate Limits

Alation Rate Limits

Alation operates as a single-tenant SaaS or on-prem deployment; rate limits are tied to the capacity of the customer's tenant rather than a published per-tier policy. Alation's public developer documentation does not publish per-second/per-minute API throughput numbers. Behavior is governed by authentication tokens (refresh + access tokens) and tenant resource limits.

2 Limits Throttle: 429
Data CatalogData GovernanceData IntelligenceData LineageData QualityBusiness GlossaryMetadata ManagementRate Limiting

Limits

Tenant Capacity tenant
varies
dimensioned by tenant size and deployment topology - not publicly documented
Per-Token Concurrency token
concurrent_requests
tenant-specific - rotate access tokens via the refresh-token flow as documented in the developer portal

Policies

Token Lifecycle
Use refresh tokens to mint short-lived access tokens. SSO-backed tenants must create refresh tokens via the Alation UI rather than the API.
Backoff Strategy
Implement exponential backoff with jitter on 429 responses; honor Retry-After if returned.
Capacity Planning
For sustained high-volume metadata sync, work with Alation's customer success team to right-size the tenant.

Sources