doc/subscriptions/gitlab_credits.md
{{< details >}}
{{< /details >}}
{{< history >}}
{{< /history >}}
GitLab Credits are the standardized consumption currency for usage-based billing. Credits are used for GitLab Duo Agent Platform, where each usage action consumes a number of credits.
GitLab Duo Pro and Enterprise and their associated GitLab Duo features are not billed based on usage and do not consume GitLab Credits.
Credits are calculated based on the features and models you use, as listed in the credit multiplier tables. You are billed for features that are generally available.
Billing occurs at the root namespace or top-level group level, not at the project level. Credit usage is attributed to the user who performs the action, regardless of which project they are using the features in. All usage in a root namespace or top-level group is consolidated for billing purposes.
GitLab provides three ways to obtain credits:
For a click-through demo, see GitLab Credits.
<!-- Demo published on 2026-01-28 -->For information about credit pricing, see GitLab pricing.
Included credits are allocated to all users on a Premium or Ultimate tier. These credits are individual and cannot be shared between users. Included credits reset at the beginning of each month. Unused credits do not roll over to the next month.
Community program subscriptions do not receive included credits.
For more information about included credits, see GitLab Promotions Terms & Conditions.
Monthly Commitment Pool is a shared pool of credits available to all users in the subscription. All users in your subscription can draw from this shared pool after they have consumed their included credits.
You can purchase the Monthly Commitment Pool as a recurring annual or multi-year term. The number of credits purchased for the year is divided in 12.
For example, when you purchase a monthly commitment pool of 1,000 credits, you will have 1,000 credits available each month for the contract term.
You can increase your commitment at any time through your GitLab account team. The additional commitment applies for the remainder of your contract term. You can decrease your commitment only at the time of renewal.
You can purchase a commitment of credits with built-in tiered discounting. The commitment is billed up front at the start of the contract term.
Credits become available immediately after purchase, and reset on the first of every month. Unused credits do not roll over to the next month.
[!note] When purchasing a monthly commitment pool, you accept the usage billing terms, including On-Demand credit usage. After you accept the terms, On-Demand billing stays active for the rest of your subscription and subsequent self-serve renewals, and you cannot opt out.
On-Demand credits cover usage incurred after you have used all included credits and the credits in the Monthly Committed Pool. On-Demand credits are billed monthly.
On-Demand credits are consumed at the list price of $1 per credit used.
On-Demand credits can be used after you have accepted usage billing terms. You can accept these terms when you purchase your monthly commitment, or directly in the GitLab Credits dashboard. By accepting usage billing terms, you agree to pay for all On-Demand charges already accrued in the current monthly billing period, and any On-Demand charges incurred going forward.
If you haven't accepted usage billing terms, you can't use GitLab Duo Agent Platform and consume On-Demand credits. You can regain access to GitLab Duo Agent Platform by either purchasing a monthly commitment or accepting the usage billing terms.
For example, a subscription has a monthly commitment of 50 credits per month. If 75 credits are used in that month, the first 50 credits are part of the monthly commitment pool, and the additional 25 are billed as on-demand usage.
GitLab Credits are consumed in the following order:
If you have not purchased the Monthly Commitment Pool or accepted the usage billing terms for On-Demand credits, you can request a free temporary pool of credits to evaluate GitLab Duo Agent Platform features.
Credits are allocated based on the number of users you request for the evaluation, and added to a shared pool for those users. Credits are valid for 30 days, and cannot be used after they expire.
To request credits, contact the Sales team.
If you're on the Free tier and want to try credits, you can start an Ultimate trial.
{{< details >}}
{{< /details >}}
{{< history >}}
{{< /history >}}
Users on the Free tier on GitLab.com can purchase a Monthly Commitment Pool of GitLab Credits for their group namespace. This provides access to a set of GitLab Duo Agent Platform features, without needing a Premium or Ultimate subscription.
On-demand usage for Free namespaces is capped at $25,000 for each calendar month. Upon reaching this limit, on-demand usage is automatically turned off and resets at the beginning of the following month.
You can buy GitLab Credits for your Monthly Commitment Pool in Customers Portal.
{{< tabs >}}
{{< tab title="Customers Portal" >}}
Prerequisites:
{{< /tab >}}
{{< tab title="GitLab.com" >}}
Prerequisites:
On the Premium and Ultimate tier:
On the Free tier:
{{< /tab >}}
{{< tab title="GitLab Self-Managed" >}}
Prerequisites:
{{< /tab >}}
{{< /tabs >}}
Your GitLab Credits are displayed in the subscription card in Customers Portal, and in the GitLab Credits dashboard.
Credit usage is calculated based on the features and models they use. Some features have multiple model options to choose from, while other features use only one model.
A request represents a single (billable) action initiated by a user (for example, sending a chat message or requesting code generation). This represents one interaction from the user's perspective.
A model call represents the underlying API calls made to LLMs to fulfill a user request. A single user request might trigger multiple model calls. For example, one call to understand context and another call to generate a response.
The following table lists the number of requests you can make with one GitLab Credit for different models. Newer, more complex models have a higher multiplier and require more credits. A request is made anytime a model is called.
For self-hosted models, you can make eight requests for one credit for any supported or compatible model.
For subsidized models with basic integration:
| Model | Requests with one credit |
|---|---|
claude-3-haiku | 8.0 |
codestral-2501 | 8.0 |
gemini-2.5-flash | 8.0 |
gpt-5-mini | 8.0 |
gpt-5-4-nano | 8.0 |
For premium models with optimized integration:
| Model | Requests with one credit |
|---|---|
claude-4.5-haiku | 6.7 |
gpt-5-4-mini | 6.7 |
gpt-5-codex | 3.3 |
gpt-5 | 3.3 |
gpt-5.2 | 2.5 |
gpt-5.2-codex | 2.5 |
gpt-5.3-codex | 2.5 |
claude-3.5-sonnet | 2.0 |
claude-3.7-sonnet | 2.0 |
claude-sonnet-4 <sup>1</sup> | 2.0 |
claude-sonnet-4.5 <sup>1</sup> | 2.0 |
claude-sonnet-4.6 | 2.0 |
claude-opus-4.5 | 1.2 |
claude-opus-4.6 | 1.2 |
claude-sonnet-4 <sup>2</sup> | 1.1 |
claude-sonnet-4.5 <sup>2</sup> | 1.1 |
Footnotes:
The following table lists the number of requests or model calls you can make with one GitLab Credit for different features. This pricing applies to all models (including self-hosted models) available for the feature.
| Feature | Requests or calls with one credit |
|---|---|
| GitLab Duo Code Suggestions | 50 requests |
| Code Review Flow | 4 calls |
| SAST False Positive Detection Flow | 1 call |
| SAST Vulnerability Resolution Flow | 0.25 calls |
Each message sent to GitLab Duo Agentic Chat counts as one billable request. One conversation window can include multiple messages, and so multiple billable requests.
{{< details >}}
{{< /details >}}
{{< history >}}
budget_caps_graphql_api. Enabled by default.{{< /history >}}
[!flag] The availability of this feature is controlled by a feature flag. For more information, see the history.
You can set a monthly GitLab Credits cap at the subscription and user level to prevent unexpected overage charges. When credit consumption reaches the configured cap, access to features that consume GitLab Credits (for example, GitLab Duo Agent Platform) is automatically suspended until the next billing period begins, or until an administrator adjusts or disables the cap.
The following cap types are available:
| Cap type | Applies to | Credit sources counted | Managed through |
|---|---|---|---|
| Subscription cap | All users on the subscription | On-Demand only | Customers Portal |
| Flat user cap | Individual users (default limit) | All | GraphQL API |
| Per-user override | Specific users (overrides the flat cap) | All | GraphQL API |
When on-demand usage in the current billing period reaches or exceeds the configured cap, all Agent Platform features (Duo Chat, Code Suggestions, Flows, and Agents) are suspended for all users on that subscription or instance. For user-level caps, only the individual user who reached their cap is suspended.
Users who have reached their cap are unable to access Agent Platform features until the cap is raised or the next billing period begins.
Usage counters reset automatically at the start of each billing period. Cap values persist across billing periods unless changed.
Caps are enforced using the most recent usage data available. Because data is not real time, limited additional GitLab Credits usage may occur before enforcement takes effect.
When subscription on-demand usage reaches the configured cap, GitLab sends an email notification to billing account managers.
Prerequisites:
If the cap is set below the currently reported total on-demand usage for the current billing period, the cap is considered reached immediately on the next enforcement check.
To disable the cap, turn off the Monthly On-demand Credits cap toggle. When disabled, no subscription-level on-demand GitLab Credits cap is enforced, and behavior falls back to existing billing behavior.
You can use the GraphQL API to view usage caps and set a flat user-level cap or a per-user override cap.
{{< details >}}
{{< /details >}}
{{< history >}}
{{< /history >}}
The GitLab Credits dashboard displays information about your usage of GitLab Credits. Use the dashboard to monitor credit consumption, track trends, and identify usage patterns.
On the dashboard, used credits represent deductions from available credits. For overages (On-Demand credits), used credits represent on-demand usage that will be paid later, if you have agreed to the usage billing terms.
To help you manage credit consumption, GitLab emails the following information to administrators and subscription owners:
You can access the dashboard in the Customers Portal and in GitLab.
[!note] Usage data is not displayed in real time. Data is synchronized to the dashboards periodically, so usage data should appear within a few hours of actual consumption. This means your dashboard shows recent usage, but might not reflect actions taken in the last few hours.
The GitLab Credits dashboard in the Customers Portal provides the most detailed view of your usage and costs.
The dashboard displays summary cards of key metrics:
The GitLab Credits dashboard in GitLab provides operational visibility into the usage of credits in your organization. Use the dashboard to understand which users, groups, or projects are driving usage, and make informed decisions about resource allocation.
The dashboard displays the following information:
{{< history >}}
{{< /history >}}
{{< tabs >}}
{{< tab title="Customers Portal" >}}
Prerequisites:
{{< /tab >}}
{{< tab title="GitLab.com" >}}
Prerequisites:
{{< /tab >}}
{{< tab title="GitLab Self-Managed" >}}
Prerequisites:
{{< /tab >}}
{{< /tabs >}}
By default, individual user data is not displayed in the GitLab Credits dashboard. To display it, you must enable this setting for your group or instance.
{{< history >}}
{{< /history >}}
When per-user credit caps are enabled, the Usage by user tab on the GitLab Credits dashboard displays a Usage control status column. This column shows whether each user can access GitLab Duo Agent Platform features or is blocked because they reached their credit cap.
The column displays one of the following statuses:
| Status | Description |
|---|---|
| Regular | The user has not reached their credit cap and can use GitLab Duo Agent Platform features. |
| Blocked - subscription cap reached | The user reached the flat per-user cap set at the subscription level. |
| Blocked - user cap reached | The user reached a per-user override cap set specifically for them. |
You can restore access for a blocked user by using the per-user override GraphQL API.
To unblock a user, either:
After you update the cap, the user's status changes to Regular and they can use GitLab Duo Agent Platform features again.
{{< history >}}
{{< /history >}}
To view a user's individual usage events in a drill-down view:
[!note] Session links are available only for GitLab Duo Agent Platform usage events that are triggered in a project and have an associated session ID. Usage events triggered in a group, legacy events, and actions outside Agent Platform don't have links.
{{< history >}}
{{< /history >}}
You can export the credit usage data for a subscription as a CSV file in Customers Portal. The CSV file lists the usage events and credits used on each day of the current month.
Prerequisites: