GitLab.com rate limits will align with subscription tiers starting October 19

GitLab.com is adjusting its rate limits to provide a more predictable experience aligned with user subscription tiers. Starting October 19, users with free accounts will have their requests capped at 60 per hour unless they authenticate, which may impact those relying on automated tasks that exceed this limit.

Users on Premium and Ultimate plans will see their new limits applied in January 2027, which suggests that as teams scale their usage, they will need to consider upgrading their plans to avoid hitting rate limits. This change is designed to ensure that the platform remains responsive and equitable for all users.

Since the new limits are specific to each subscription, teams should prepare by reviewing their API usage patterns and optimizing their request strategies, such as batching or caching requests. This is particularly important for those on the Free plan who may be more likely to encounter limitations due to unauthenticated requests.

GitLab has indicated that most users are currently operating within the new limits and will not notice significant changes. However, those who do exceed the limits will receive HTTP 429 responses, prompting them to adjust their approach or authenticate their requests to access higher limits.

The upcoming changes not only aim to manage load effectively as demand increases but also reflect industry standards for rate limiting, helping users understand what to expect in terms of performance and capacity based on their chosen subscription.