Gitlab Flex

The agentic era made software purchasing harder to predict. Six months out, you don't know how many seats your teams will need, how much AI your developers will consume, or which new capabilities you'll want to turn on mid-year. GitLab Flex is built for that reality: one annual commitment you can reshape month to month without reopening procurement.

How GitLab Flex works Commit to an annual spend based on your projected GitLab usage. That commitment creates a balance you draw down monthly as you provision seats, GitLab Credits, and usage-based capabilities. When your needs shift, such as reducing seats while scaling AI agent usage, or adopting a new capability mid-year, you reallocate next month's reservations within your existing agreement. No amendment required.

What's different Most software models keep seat licenses and usage credits in separate buckets that can't be rebalanced without going back to the table. GitLab Flex puts both under the same commitment, so you can shift budget between seats and AI usage each month without re-procurement.

Coverage One commitment covers GitLab Premium and Ultimate seats, GitLab Credits (for Duo Agent Platform, hosted runners, and artifact management), and future credit-metered capabilities at the published rate card. Larger commitments unlock better unit pricing, and reserved capacity costs less than on-demand usage.

Pricing model Monthly drawdown is based on provisioned seats and reserved or consumed GitLab Credits. Volume discounts apply automatically based on commitment size. Usage beyond your annual commitment bills at on-demand rates ($1 per credit; per-seat list price for seats). Cloud-connected deployments bill automatically through your AWS account.

Enterprise governance Track consumption in real time by capability, project/team, and deployment model. Forecast against your annual balance, configure budget alerts, and set policy-based guardrails per environment. Export usage data for FinOps, procurement, and internal chargeback.