Introduction
Imagine running a factory where every worker suddenly becomes ten times faster.
That sounds wonderful.
But now imagine that many of those workers are autonomous machines. They can build things, change things, and send those changes into production without waiting for a human.
Productivity rises. So does the risk of something going wrong.
Someone still needs to control the factory floor, inspect the work, enforce the rules, and keep a record of every decision.
That is the simplest version of the bull case for GitLab.
AI may change who writes the code. GitLab wants to remain the place where that code is planned, tested, secured, approved, and deployed.
What GitLab actually does
Building software involves much more than typing code.
Teams must store that code, test it, scan it for security problems, track changes, coordinate projects, and eventually release the finished product.
Historically, companies often bought a different tool for each job.
Think of it as a workshop assembled from several manufacturers. One company supplies the power tools. Another provides the security system. A third keeps the project schedule. Then someone has to make everything work together.
GitLab’s pitch is simpler: put the entire workshop under one roof.
One platform. One audit trail. One place to see what happened to the code from the moment someone planned a change until that change reached a customer.
For a startup, that can make development easier.
For a bank, pharmaceutical company, or other regulated enterprise, it can be essential. Those organizations need to know who changed the code, whether it passed security checks, and who approved its release.
GitLab can run in its own cloud or on a customer’s infrastructure. That flexibility helps it serve both modern software companies and large organizations with strict security requirements.
The direct AI opportunity
GitLab’s AI product is called the Duo Agent Platform.
These agents can help write, review, and test code inside the same platform customers already use.
Duo became generally available only two weeks before the quarter ended. Yet it immediately generated more new recurring revenue than GitLab’s two older AI products had produced together in any previous quarter.
Paid usage was running at an annualized rate of nearly $20 million by quarter-end.
That sounds exciting, but it comes with an important warning.
GitLab’s chief financial officer explicitly told analysts not to build that figure into their models yet. It represents only one quarter of data, and some of the demand could reflect excitement surrounding the launch.
That caution is healthy. The number is evidence of early demand, not proof of a durable revenue stream.
There are encouraging customer examples.
A top-10 American bank tested Duo and reported saving roughly 1.5 hours per coding task. The bank expects the number of active users to grow approximately twentyfold if the broader deployment proceeds.
GitLab is also selling Duo through the Amazon Web Services, Google Cloud, and Anthropic marketplaces.
That may sound like administrative detail, but enterprise purchasing can resemble airport security. Every additional checkpoint slows things down.
Selling through marketplaces customers already use removes checkpoints and makes the product easier to approve and purchase.
Most importantly, management assumes Duo will make no material contribution to its full-year revenue guidance.
The existing platform must therefore carry the forecast. If Duo adoption continues, that revenue could arrive on top of what management currently expects.
That is the AI optionality in the story.
The larger AI platform bet
GitLab is making a larger bet than simply selling its own coding agent.
It also wants to benefit when customers choose someone else’s.
Its proposed context service is called GitLab Orbit.
Think of an AI coding agent as a very talented new employee.
On its first day, that employee may understand programming, but it does not understand your company. It does not know why past decisions were made, how your systems connect, which policies must be followed, or what previous developers already tried.
That organizational memory is the context.
GitLab wants Orbit to supply it.
Outside tools such as Claude Code, Cursor, and Codex could plug into that context and pay GitLab based on usage.
If this works, GitLab would not need to win every competition for the best coding agent. It could become the tollbooth that different agents pass through to understand a customer’s software environment.
GitLab is also working with an unnamed AI lab on a major rebuild of Git, the underlying technology developers use to track changes to code. The goal is to support 100 times the current scale.
The identity of that AI lab has not been disclosed, but the partnership itself is meaningful.
An AI company has chosen to build foundational infrastructure with GitLab instead of simply routing around it.
The larger vision is one platform supporting three ways of developing software:
Humans writing code manually.
Humans working alongside agents.
Autonomous agents performing more of the work themselves.
Across all three, companies still need identity, security, permissions, and an audit trail.
In fact, those controls may become more important as machines gain more freedom to alter production software.
More autonomous workers can mean more productivity. They can also mean more doors that need locks.
The financial foundation
The financial results suggest GitLab does not need to wait for this AI vision to support the business.
Quarterly revenue reached roughly $264 million, growing 23% from the previous year. That was four percentage points ahead of guidance.
Management, however, is guiding to only 16% to 17% growth for the full year.
That gap matters.
The optimistic interpretation is that management has set a cautious bar while the underlying business is performing better.
The portion of signed business expected to become revenue within the next 12 months grew 24%.
New customer signings increased 30% and reached their highest absolute count in 10 quarters.
Existing customers are spending about 17% more than they were a year ago, while gross retention remains above 90%.
The large-enterprise business is particularly strong.
GitLab now has more than 1,500 customers spending at least $100,000 annually. That group grew 18% and represents more than three-quarters of total recurring revenue.
The largest customers are not merely experimenting with GitLab. They are building more of their software operations around it.
GitLab is also improving profitability.
Its adjusted operating margin reached 14%, approximately two percentage points better than a year ago.
Free cash flow was unusually strong at nearly $147 million. Faster customer collections helped that figure, so it should not be treated as a normal quarterly run rate.
The company also holds roughly $1.36 billion in cash and short-term investments. It repurchased approximately 2.4 million shares during the quarter and still has $350 million available under its buyback authorization.
That balance sheet gives GitLab room to invest while the market changes around it.
The technical setup
There is also a technical setup behind the fundamental story.
GitLab’s stock has spent roughly six months building a base. Within that larger pattern, buyers have repeatedly stepped in at progressively higher levels.
The area around $35 has become an important technical boundary.
A convincing move above that area would suggest the stock is leaving its base. Failure to hold the recent higher lows would weaken the setup.
The broader software sector has also been improving. Several software stocks have held up well even during weaker trading in the Nasdaq, suggesting that investors may be rotating back toward the sector.
None of this guarantees a breakout.
The chart simply provides a way to judge whether the market is beginning to agree with the fundamental thesis.
The counter-case
First, growth beneath the headline is uneven.
Bookings grew only 12%. Revenue from customers running GitLab on their own servers was flat, while smaller customers grew just 7%. The cloud and enterprise businesses are carrying more of the load.
Second, software seats remain under pressure.
Layoffs at GitLab’s customers are reducing seat counts, and price-sensitive customers represent about one-fifth of recurring revenue. GitLab’s shift toward usage-based pricing may help, but it has not yet been proven.
Third, the AI evidence is very early.
The Duo figures represent one launch quarter, and the company’s own chief financial officer has warned investors not to extrapolate them.
Fourth, execution risk is rising.
GitLab is cutting 14% of its workforce and exiting 22 countries while attempting an ambitious technical rebuild. A leaner organization could become faster, but it also has less room for mistakes.
And this is not a cheap stock in the traditional sense.
GitLab remains unprofitable under standard accounting rules and trades at more than 40 times forward adjusted earnings. The existing business must continue performing for the AI optionality to matter.
What to watch
There are six things worth monitoring from here.
First, revenue growth compared with management’s 16% to 17% guidance. If growth remains closer to the latest 23% result, the cautious-guidance argument becomes more credible.
Second, watch bookings, near-term contracted revenue, and new customer signings. Together, they tell us whether today’s demand can become tomorrow’s reported growth.
Third, watch the split between cloud and self-managed subscriptions, along with growth among smaller customers. The enterprise business is working. GitLab still needs a healthy pipeline beneath it.
Fourth, watch Duo—but do not extrapolate one launch quarter. The important evidence will be sustained usage, broader deployments, and recurring customer expansion.
Fifth, watch the restructuring. The bull case requires GitLab to improve efficiency without damaging sales or delaying its platform rebuild.
Finally, watch the $35 area and the relative strength of the broader software sector.
The chart should confirm the thesis, not replace it.
Bottom line
The GitLab story comes down to one question:
As AI agents write more software, does the platform surrounding the code become less important—or more important?
The bull case says more important.
When one human writes code, governance is useful.
When thousands of autonomous agents can write, test, and deploy code around the clock, governance becomes essential.
GitLab does not need to create every worker in the AI software factory. It needs to control the factory floor.
The existing business provides the foundation.
Duo provides direct AI revenue.
Orbit could allow GitLab to collect a toll from outside agents.
And its governance layer may become more valuable as software development becomes increasingly autonomous.
But this remains a growth-plus-optionality case, not a deep-value case.
The durable platform must keep compounding for the AI upside to matter.
This article is for educational and informational purposes only. It is not financial advice. Do your own research.
