惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
V2EX
量子位
博客园 - 司徒正美
IT之家
IT之家
V
Visual Studio Blog
Apple Machine Learning Research
Apple Machine Learning Research
博客园_首页
Google DeepMind News
Google DeepMind News
Last Week in AI
Last Week in AI
Microsoft Security Blog
Microsoft Security Blog
T
Tailwind CSS Blog
aimingoo的专栏
aimingoo的专栏
GbyAI
GbyAI
Vercel News
Vercel News
B
Blog
大猫的无限游戏
大猫的无限游戏
D
DataBreaches.Net
小众软件
小众软件
罗磊的独立博客
博客园 - 叶小钗
雷峰网
雷峰网
Martin Fowler
Martin Fowler
Hugging Face - Blog
Hugging Face - Blog
WordPress大学
WordPress大学

GitLab

Rate limits on GitLab.com are changing Optimize your team See who spent your AI credits and set fair caps per team New MCP tools help platform teams scale automation safely GitLab Duo CLI takes a task from goal to done When to use SAST versus an LLM security scanner GitLab Dedicated: Compliance for a new regulatory era How to calculate DevOps platform total cost of ownership GitLab Critical Patch Release: 19.3.2, 19.2.6, 19.1.8 Co-Create: Building GitLab with our users Prepare for the Cyber Resilience Act Bring your own model to GitLab Duo Self-Hosted with Microsoft Foundry GPT-6 Astra on GitLab: Faster runs, fewer tokens used GitLab’s internal playbook to foster AI-fluent technical teams Critical remote code execution in vm2, a widely used Node.js sandbox library GitLab compliance frameworks: Adhere to SOC 2 in minutes How to recognize your team with GitLab Achievements Making room for what GitLab Patch Release: 19.3.1, 19.2.5, 19.1.7 Git was built for humans — agents need an upgrade Scale software delivery without owning the runner fleet When code is abundant When your backlog outgrows your team, GitLab scales remediation Run agentic software delivery inside the boundaries you already trust Build custom flows in minutes with the Flow Creator agent GitLab 19.3 release notes From chaos to context: Building an AI dev workflow From OpenTofu to Argo CD: GitLab as your AWS control plane Avoid the massive end-to-end tax of default full history clones GitLab Critical Patch Release: 19.2.4, 19.1.6, 19.0.8, 18.11.11
GitLab Flex: Commit once, reshape your seats and AI spend
Talia Armato-Helle · 2026-06-10 · via GitLab

The agentic era made your needs harder to predict, and the way you buy software hasn't caught up. Six months out, you don't know how many seats you'll need, how much AI your teams will consume, or which new capabilities you'll want to turn on. Yet the contract you sign today fixes all three up front and won't budge until renewal. GitLab Flex was built to solve this predicament. It's one annual commitment you can reshape month to month across seats, AI usage, and new capabilities, without re-procurement.

Fixed contracts, moving needs

The shift to agentic software engineering introduced uncertainty on three fronts at once:

  • How many seats. The agentic era is changing who builds. Some companies are adding people who never worked in GitLab before so they can build directly on the platform, and want to grow seats. Others are reshaping their org structure and contractor mix around agents, which can push seat needs up or down. Your seat count six months out moves in both directions, and an annual contract locks you in with a single guess.
  • How much AI usage. Agent usage grows on its own curve of use cases, enablement, and technology advancements.
  • Which capabilities. New agentic infrastructure capabilities ship constantly. You can't know at signing which ones you'll want to adopt mid-year.

A traditional contract asks you to lock all three in advance and live with the guess until renewal. Guess high and you overpay for idle seats and capacity you never use. Guess low and adopting anything new means re-opening procurement cycles that stall the team right when it has momentum. Either way, the contract is fixed while your needs keep moving.

Annual budgets adapted monthly

GitLab Flex is one annual dollar commitment against a published rate card. From that single commitment you draw down platform seats, GitLab Credits, and eligible usage-based capabilities — across GitLab.com multi-tenant SaaS, Self-Managed (including air-gapped), and GitLab Dedicated single-tenant SaaS. The point is that the commitment flexes on exactly the three things you can't predict.

Adjust seats without waiting for renewal. When a team wraps a project and rolls off, you don't keep paying for idle seats until the contract comes up again. You can reallocate next month's reservations toward another team's seats, or toward AI usage inside the existing agreement.

Scale AI usage with predictable economics. Consumption draws from your annual commitment at the published rate. Usage above the full commitment bills on-demand at $1 per credit, so a busy month doesn't turn into a surprise. Larger commitments unlock better unit pricing, and reserved capacity costs less than unplanned usage.

Add new capabilities without new procurement. Eligible capabilities released after you sign land on the same rate card. When you want to turn one on, you draw it from the commitment you already have without the added steps of re-procurement.

If you've used consumption pricing elsewhere — cloud credits, observability credits — the drawdown will feel familiar. Here's what's different: With Flex, your seats and your usage live under the same commitment, so you can move budget between them. Most models keep seat licenses and usage credits in separate buckets you can't rebalance without going back to the table.

Stacked bar chart showing 12 months of GitLab Flex reservations. Platform seats and GitLab Credits shift proportions month to month within a fixed annual commitment, with an unreserved buffer that varies by month.One annual commitment. Monthly reservations across seats and usage-based GitLab Credits. Reshape spend as needs shift. No amendment required.

One agreement, any mix

A single Flex agreement can combine any of the following, all drawing from the same annual commitment:

  • Platform seats. GitLab Premium and Ultimate at published rates, with volume discounts tied to your commitment level. (The Flex volume discount is the starting point for seat discounts, automatically applied based on total commitment size. Seat discounting can go above the Flex discount level with additional approvals.)
  • GitLab Credits. Credit-metered capabilities like GitLab Duo Agent Platform, hosted runners, and artifact management, each at a published credit rate.
  • Every deployment type. GitLab.com, Self-Managed, Dedicated, and air-gapped, all under one agreement — so your mix can shift over the term without restructuring.

Image example of what a customer portal may look like with GitLab Flex reservations. Annual Commitment, Contract Term, and Monthly adjustment table shown to illustrate how the product will work. Actual layout and experience is subject to change.Adjust monthly reservations across seats and usage-based GitLab Credits. Reshape spend as needs shift. No amendment required. (The image above is illustrative of the product in a customer portal, actual layout and experience subject to change.)

Volume economics with spend controls

  • Larger annual commitments unlock better unit pricing across the rate card, and reserved capacity costs less than unplanned usage.
  • Subscription-level and per-user caps help your team stick to budgets along with admin controls at the project-group level.
  • Unreserved seats draw at the effective price, the same pre-negotiated rate as reserved seats.
  • Usage above the full Flex commitment bills at on-demand rates at $1 per credit or your negotiated per-seat price.
  • Cloud-connected customers are billed automatically; air-gapped customers are invoiced twice a year.

Keep your current plan through renewal

GitLab Premium and GitLab Ultimate remain available at direct seat pricing. Flex is the recommended structure for new agreements, but existing customers can continue on their current contract through renewal. With Flex, tier capabilities do not change: GitLab Premium and Ultimate features remain.

If you are approaching renewal and want to evaluate Flex, your account team can model both options against your current capabilities and AI usage so you can compare before committing.

Start with a model built for what comes next

The shift to agentic software engineering is not only a product shift. It is a budgeting and planning shift. GitLab Flex gives organizations one agreement for platform and AI spend, plus a clearer operating model for managing both and a structure built to keep pace as needs change.

Customers can request orders with GitLab Flex now, with fulfillment rolling out throughout the quarter.

Request GitLab Flex

To explore the full set of platform innovations announced at Transcend, including GitLab Orbit, Agentic Git, and AI Governance, visit our What's New portal.