Back to Gitlabhq

Per-capability spend caps for GitLab Flex

doc/releases/19/gitlab-19-3-released/flex-per-capability-spend-caps.md

19.3.0515 B
Original Source

With GitLab Flex, overage from one capability draws down the same commitment every other capability depends on. You can now set a spend cap for each capability when you adjust your Flex reservation in the Customers Portal: Restricted (no overage past the reservation), Usage cap (a bounded amount of overage), or Unlimited (unlimited overage past the reservation). When a capped capability reaches its cap, its usage stops for the rest of the billing period, and capabilities without a cap keep running.