GitLab.com rate limits tied to subscription tier from Oct 19
Original: Rate limits on GitLab.com are changing
Why This Matters
As AI agent workloads multiply, platform-level rate limits will increasingly shape what teams can build and automate at scale.
GitLab.com will enforce subscription-based rate limits starting October 19, 2026. Free and unauthenticated traffic is affected first; Premium and Ultimate accounts follow in January 2027. Unauthenticated requests are capped at 60 per hour per IP regardless of account tier.
GitLab says platform load is expected to grow 'several times over' this year, and the rate limit overhaul is its answer to keeping response times stable as agentic and automation workloads pile on. The new rules are straightforward: limits are set per user and per top-level group, tied directly to subscription tier. Free plan users and unauthenticated requests get the new caps first on October 19. Premium and Ultimate subscribers have until January 2027 before their limits shift. The sharp edge for teams to note: unauthenticated requests are throttled to 60 per hour per IP — even if the underlying account is on a paid plan. Any automation hitting the API without credentials falls into that bucket. GitLab is running two brownout windows — October 7 and October 14, 15:00–19:00 UTC — so teams can test real workload behavior under the new limits before they go permanent. The company says the Free tier and anonymous allowance 'match the industry norm,' while Premium and Ultimate are positioned as more generous than comparable platforms. Full per-plan numbers are in the rate limits documentation.