Kedasha is a Developer Advocate at GitHub who shares her software development experience with the broader developer community. She is passionate about helping others learn about the technology industry and can be found online at **@itsthatladydev**.
### Professional Role
- Works as a Developer Advocate at GitHub.
- Shares lessons and insights with developers.
### Interests and Community Work
- Enjoys helping people learn about the tech industry.
- Draws on her experience as a software developer when supporting the community.
Kedasha’s work centers on education, mentorship, and sharing practical knowledge with developers.
Kedasha is a GitHub Developer Advocate who shares her software development experience with the broader developer community. She is passionate about helping others learn about the technology industry and can be found online as **@itsthatladydev**.
### Professional Role
- Works as a Developer Advocate at GitHub.
- Shares lessons and experiences with developers.
### Community and Education
- Enjoys helping others learn about technology and the tech industry.
- Uses her experience as a software developer to support the wider community.
Kedasha’s work centers on developer education, community engagement, and sharing practical industry knowledge.
GitLab is expanding its integration with Anthropic Claude to provide enterprise teams with more capable AI inside a governed software development platform. Claude supports GitLab Duo Agent Platform features such as code generation, review, agentic chat, and vulnerability resolution. The central argument is that organizations should not have to trade advanced AI capabilities for security, compliance, and auditability.
## Governed AI across the SDLC
- Claude-generated changes follow GitLab’s existing merge request process, approval rules, security scans, and audit trails.
- AI agents do not bypass controls; their actions remain attributable, reviewable, and subject to policy enforcement.
- This governance becomes increasingly important as agents autonomously plan, code, test, secure, and deploy software.
- GitLab positions built-in governance as a core architectural differentiator rather than an added feature.
## Flexible enterprise deployment
- Claude is available in GitLab through:
- Google Cloud Vertex AI
- Amazon Bedrock
- Organizations can use existing cloud contracts, governance frameworks, and data-residency arrangements.
- GitLab’s availability in the Claude Marketplace lets customers purchase GitLab Credits and apply them toward Anthropic spending commitments.
- These options simplify procurement and consolidate AI spending.
## Supporting an agentic development model
- GitLab is selecting model partners based on reasoning ability, reliability, and safety.
- The platform is designed to maintain visibility into what AI agents do, when they act, and how their changes are tracked.
- As agents take on more complex engineering tasks, GitLab argues that strong models must be paired with equally strong governance.
## Implications for customers
- Existing GitLab Duo users gain deeper Claude-powered assistance without changing their established governance processes.
- Organizations evaluating AI development platforms can access advanced models while retaining enterprise control.
- GitLab presents the integration as a way to accelerate development without compromising compliance or oversight.
The practical recommendation is to evaluate AI platforms not only by model capability, but also by how well they integrate governance, auditability, cloud deployment options, and existing enterprise workflows.
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.
Kedasha is a GitHub Developer Advocate who shares her software development experience and industry knowledge with the broader developer community. She is passionate about helping others learn and can be found online as **@itsthatladydev**.
### Role and Focus
- Works as a Developer Advocate at GitHub.
- Shares lessons from her professional experience with developers.
- Helps others learn about the technology industry.
### Online Presence
- Identifies online as **@itsthatladydev**.
Kedasha is a Developer Advocate at GitHub who shares her software development experience with the broader developer community. She is passionate about helping others learn about technology and the tech industry.
### Professional Role
- Works as a Developer Advocate at GitHub.
- Shares lessons from her career with developers and learners.
### Community Engagement
- Enjoys helping others understand the technology industry.
- Maintains an online presence as **@itsthatladydev**.
