techlist.io
KREN
gitlab

GitLab 18.11: Budget guardrails for GitLab Credits (opens in new tab)

gitlabsoftware-developmentai-mlsaasgraphql-apibudget-guardrailsspending-capsusage-governance

GitLab 18.11 introduces spending controls for GitLab Credits used by the Duo Agent Platform. Organizations can set subscription-wide monthly caps, limit individual users, and monitor enforcement, making AI costs more predictable as adoption grows. The goal is to combine usage-based pricing with the budget certainty traditionally associated with seat-based licensing.

Subscription-Level Spending Caps

  • Billing account managers can set a hard monthly ceiling in the Customers Portal.
  • When usage reaches the cap, Duo Agent Platform access pauses for all users until the next billing period.
  • Managers can raise or disable the cap mid-month to restore access.
  • Caps reset monthly and remain in effect until changed.
  • Because usage data is synchronized periodically, limited usage may occur after the cap is technically reached.

Per-User Credit Limits

  • A flat per-user limit can be applied uniformly through the GitLab GraphQL API.
  • Custom overrides allow organizations to give higher allocations to selected users, such as staff engineers.
  • Limits apply to a user’s total consumption across all credit sources.
  • Reaching an individual limit pauses only that user’s Duo Agent Platform usage; their GitLab access remains intact.
  • Other users continue working until they reach their own limits or the subscription cap.

Visibility and Notifications

  • Billing account managers receive email notifications when the subscription cap is reached.
  • Group owners on GitLab.com and instance administrators on Self-Managed installations can see users blocked by per-user caps.
  • Administrators can restore access by changing limits through the GraphQL API.
  • Per-user usage data supports monitoring, chargeback, and future budget planning.

Benefits for Scaling AI Adoption

  • Hard caps make AI spending easier to forecast, approve, and include in quarterly budgets.
  • Per-user limits help distribute credits fairly across teams and cost centers.
  • Organizations can expand from small pilots to hundreds or thousands of developers without risking uncontrolled invoices.
  • Usage data helps platform teams understand consumption patterns and adjust allocations.

Usage-Based Pricing with Guardrails

GitLab contrasts its approach with seat-based AI tools, where organizations pay a fixed amount per user regardless of usage. GitLab Credits instead charge based on actual consumption while adding enforced spending limits, combining flexibility with predictable budgeting.

Example Deployments

  • A 200-person engineering organization can set a subscription cap matching its approved monthly budget.
  • If usage approaches the limit, finance or billing managers can either increase the cap or wait for the next period.
  • A 2,000-person enterprise can apply standard limits to most developers while allocating higher caps to engineers handling complex work.

Availability and Setup

  • The controls are available for GitLab.com and Self-Managed customers running GitLab 18.11.
  • Subscription-level caps are configured by billing account managers in the Customers Portal.
  • Flat and custom per-user caps are configured through the GitLab GraphQL API by namespace owners or instance administrators.

Organizations adopting GitLab Duo Agent Platform should establish a subscription cap, define fair per-user allocations, and monitor usage regularly. These controls provide a safer foundation for expanding AI usage without sacrificing financial oversight.