See who spent your AI credits and set fair caps per team
Blog post from GitLab
GitLab 19.4 introduces per-user GitLab Credits management to help organizations control, attribute, and report AI spending as agentic AI adoption expands. Premium and Ultimate customers can set subscription-wide and individual spending caps, create exceptions for specific users, receive usage alerts at key thresholds, and use GitLab Flex controls to restrict or limit spending by capability. Detailed exports provide up to 31 days of billable event data, including user, project, namespace, session, model, token, and credit-consumption information, enabling departmental showback, potential chargeback, and more accurate forecasting. Developers can also view their own daily credit consumption, while promotional credits are applied per user before shared evaluation credits. GitLab notes that usage data syncs periodically rather than in real time, meaning in-flight activity may temporarily exceed caps, and states that existing subscription caps, APIs, and automations remain unchanged. The company also promotes its October 6 GitLab Transcend event, focused on managing the effects of coding agents across the software development lifecycle.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| AI Agents | 1 | 931 | 231 | 103 | -84% |
| LLM | 1 | 747 | 162 | 79 | -85% |
| Platform Engineering | 1 | 358 | 65 | 25 | -70% |
| Real-time | 1 | 649 | 155 | 80 | -85% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.