Why GitLab Stock Soared 35% in August and Why It's Already Rocketed Higher

GitLab shares rebounded after August’s +34.9% surge as AI “SaaSpocalypse” fears eased. In its fiscal 2027 Q2 (ended July 31), GitLab reported revenue of $286.3M (+21% YoY) vs. $273.1M consensus and adjusted EPS of $0.25 (flat) vs. $0.18 consensus, with adjusted operating margin improving to 15% from 14% and RPO up 16% to $1.2B. Multiple analysts raised price targets in August (e.g., BTIG to $52 from $36; RBC to $46 from $29), supporting the rerating after the earnings beat.

Analysis

This is less an “AI kills software” story than a repricing of duration risk. Platforms that sit inside the workflow and security stack should see AI expand usage intensity, not vanish demand; the bigger second-order winner is the entire DevSecOps ecosystem, where more machine-generated code means more scanning, governance, and integration spend. The main losers are point tools with low switching costs and vendors whose value prop is mostly “assist the developer” rather than own the system of record.

Near term, the move is likely still partly a short-covering/multiple-reset trade, so the next 1-3 months matter more than the next 1-3 days. The key catalyst is whether peer software prints confirm that AI features are being monetized rather than used as a discounting tool; if not, GTLB’s re-rating can stall even if fundamentals remain healthy. A clean thesis break would be any slowdown in current-dollar RPO growth or a flattening of adjusted operating leverage, which would signal that AI optimism is outpacing actual budget capture.

The contrarian miss is that AI can be both a tailwind and a pricing threat: customers may accept AI-enabled workflows but demand lower per-seat pricing, compressing ARR quality even as usage rises. At ~high-40s to high-50s earnings multiples, the stock is now trading on execution perfection, so the reward/risk is better on dips than on breakout chasing. Longer term, if AI truly raises engineering throughput, the winners will be the vendors who own compliance, traceability, and deployment, not standalone copilots.

Key Decisions for Investors

• Do not chase GTLB after the rebound; wait for a 3-5% pullback or a test of the post-earnings breakout level before initiating a long. Target a 6-12 month hold only if management re-accelerates billings/RPO and operating margin keeps expanding; cut if current RPO growth decelerates for two straight quarters.
• Pair trade: long GTLB / short WCLD or a weaker SaaS basket for 1-3 months. The trade monetizes the market’s preference for workflow-embedded software over generic SaaS names that are more exposed to AI-driven seat compression; exit if GTLB underperforms the basket by ~8-10% after the next peer earnings cycle.
• For higher-conviction upside, use a 3-6 month GTLB call spread financed by selling farther OTM calls rather than outright stock. This keeps upside exposure to a continued re-rating while limiting damage if the AI enthusiasm proves to be a one-quarter multiple squeeze rather than a multi-quarter trend.