Options flow education · June 28, 2026

Options flow for cloud hyperscaler stocks: reading AWS, Azure, and Google Cloud revenue growth and AI infrastructure signals

Amazon, Microsoft, and Alphabet are three of the largest companies in the world, but institutional options positioning in each is driven primarily by one thing: the health and trajectory of their cloud segments. AWS, Azure, and Google Cloud have become the operating system of enterprise AI, and the quarterly revenue growth rates, margin trajectories, and AI workload signals from each segment are the dominant variables moving institutional positioning in AMZN, MSFT, and GOOGL options. Understanding how these cloud-specific signals translate into flow helps you read why smart money is positioning the way it is in the hyperscalers.

Amazon (AMZN) and AWS: the margin engine that drives the stock

AWS is the most profitable segment in Amazon by a wide margin, it accounts for roughly 60% of Amazon's total operating income despite being only about 15% of total revenue. This structural reality means AWS growth rate and margin trajectory are the dominant variables in AMZN options positioning, even though the retail business is far larger by revenue. When institutions buy AMZN calls, they are predominantly expressing a view on AWS. When they buy AMZN puts, it is often because AWS growth is decelerating or margins are compressing. Key signals to track:

Microsoft (MSFT) and Azure: growth rates, Copilot seats, and the AI monetization signal

Azure is unique among the hyperscalers in that Microsoft reports its growth as a percentage change rather than in absolute dollars, which makes year-over-year comparisons more volatile and gives individual quarterly prints more binary character. A 1-2 percentage point miss or beat on Azure growth (e.g., reporting 29% growth against expectations of 31%) can cause significant multi-percent moves in MSFT, making Azure the primary catalyst in MSFT options flow around earnings. The overlapping signals to watch:

Alphabet (GOOGL) and Google Cloud: profitability inflection as the new signal

Google Cloud has historically been the smallest of the three major hyperscalers but has been among the fastest-growing in recent quarters, and critically, it has turned operating-profit positive after years of operating losses. This profitability inflection is a structurally important new signal that changes the options flow dynamics in GOOGL. When a cloud segment transitions from loss-making to profitable, it expands the institutional buyer base (value investors who were previously excluded by unprofitable growth now have a fundamental entry point), which changes the character of call accumulation in GOOGL:

Cross-hyperscaler signals: NVDA earnings, capex announcements, and AI workload migration

The three hyperscalers do not trade in isolation, they share a common set of leading indicators that move all three simultaneously. Understanding these cross-name signals helps you recognize when flow in AMZN, MSFT, and GOOGL is driven by sector-level information rather than company-specific catalysts:

AWS, Azure, and Google Cloud: tracking the segment inside each hyperscaler

The single most important reframe for reading hyperscaler options flow is this: you are not trading Amazon, Microsoft, or Alphabet, you are trading AWS, Azure, and Google Cloud, respectively. Each parent company's stock is driven primarily by its cloud segment's revenue trajectory and margin dynamics, not by the consolidated headline numbers. Institutional analysts model each cloud segment in isolation and compare those segment-level results against consensus before taking options positions. Understanding how each segment is tracked gives you a structural edge in interpreting flow.

For Amazon, the critical variable is AWS operating margin, not total Amazon revenue. AWS contributes roughly 60% of Amazon's consolidated operating income while representing only about 15% of total revenue, which means a 1-percentage-point improvement in AWS operating margin has a much larger impact on consolidated earnings than a 5% swing in retail revenue. Institutional models therefore have a very tight focus on AWS-specific metrics: revenue growth rate, operating income line, and commentary around AI workload contribution to the margin mix. When AMZN options flow shifts bullish ahead of earnings without any obvious retail catalyst, the bet is almost always on an AWS margin print that is above the street model, not on a consumer spending recovery. Segment revenue surprise versus the AWS-specific consensus estimate, not the total Amazon revenue consensus, is the actual options catalyst.

For Microsoft, Azure revenue is reported as a percentage growth figure rather than in absolute dollar terms, which creates a structurally different options dynamic. Because the percentage is what the street forecasts, even a 2-percentage-point miss or beat (e.g., 29% growth when 31% was expected) causes disproportionately large stock moves, the options market is pricing binary segment-level surprises against a consensus number that institutional traders have been refining through channel checks for weeks. Segment-level guidance changes, particularly when Microsoft management raises or lowers its forward Azure growth estimate in the guidance range, move MSFT more than headline beats, because the guidance update revises the forward revenue model across multiple future quarters simultaneously. A 1-point raise in Azure guidance midpoint implies compounding outperformance on the annual revenue line, which options models immediately capitalize at a growth-company multiple.

For Alphabet, the options-relevant inflection was Google Cloud's transition to positive operating income, which occurred meaningfully starting in 2023. When a cloud segment flips from burning cash to generating it, the institutional buyer base expands dramatically, value-oriented fund managers who previously had no fundamental basis to own the cloud-growth thesis now have a margin expansion story they can underwrite. This broadening of the buyer base is a structural tailwind for GOOGL call accumulation that does not disappear after a single quarter. Each successive quarter of improving Google Cloud operating margin widens the addressable institutional audience, which is why LEAPS call buying in GOOGL has remained elevated even in quarters where near-term revenue growth was in line rather than a blowout. The segment profitability trajectory, not just the growth rate, is the primary GOOGL flow driver at the institutional level today.

Across all three names, the practical lesson for reading options flow is to disaggregate headline revenue numbers from segment-level results before you interpret bullish or bearish positioning. A call sweep in AMZN into earnings that coincides with negative retail sentiment is not contradictory, it is a focused bet on AWS. A put purchase in GOOGL during a Search advertising strength period is not confused, it may be hedging a Google Cloud consensus miss. The segment is the signal; the consolidated headline is the noise.

AI infrastructure capex cycle and options flow

The AI infrastructure buildout cycle has created a new layer of options flow dynamics that did not exist before 2023. The hyperscalers are simultaneously the largest buyers of AI infrastructure (GPUs, networking, power, data center space) and the primary beneficiaries of AI cloud revenue, which means capex announcements from each company function as both a cost signal and a forward revenue signal, depending on how you model the capex-to-revenue conversion timeline. Understanding which lens institutions are applying at any given moment is critical for reading flow correctly.

The chain runs from capex announcement through GPU demand confirmation to cloud revenue leading indicator. When Microsoft or Amazon announces a multi-billion dollar AI infrastructure investment program, the immediate read by sell-side models is not margin headwind, it is forward revenue commitment. A hyperscaler does not build data center capacity speculatively; it builds in response to contracted or near-contracted enterprise demand. So a $10 billion capex announcement implies a revenue pipeline of approximately $15-20 billion over the depreciation life of those assets, at cloud-level margins. Options flow that appears bullish immediately after a hyperscaler capex announcement is pricing this revenue pipeline, not ignoring the depreciation cost. The error retail traders make is treating capex as a pure cost, institutions treat it as a deferred revenue signal.

Nvidia's order book is a 6-9 month leading indicator for hyperscaler AI revenue because GPU procurement takes that long to translate into operational data center capacity that generates cloud revenue. When NVDA reports strong data center forward guidance and growing order backlogs, institutional models immediately update their hyperscaler revenue forecasts for the quarters 2-3 periods forward. Options flow in AMZN, MSFT, and GOOGL often appears in the days following NVDA earnings as a result, not because of any company-specific news, but because NVDA's order book has updated the probability distribution on hyperscaler cloud revenue 6-9 months out. LEAPS in all three hyperscalers are particularly sensitive to this signal, as longer-dated options allow positioning for the full capex-to-revenue conversion timeline.

Sovereign AI cloud deals, government contracts for AI infrastructure and cloud services, have emerged as a discrete catalyst for MSFT and GOOGL call flow. Government AI procurement moves at a different cadence than enterprise procurement: it is longer-cycle, larger in average contract value, and creates highly visible backlog additions when announced. Microsoft's Azure Government cloud business and Google Cloud's public sector arm have both won significant sovereign AI commitments, and options flow in both names tends to accumulate call positions ahead of periods when sovereign contract announcements are expected. These deals also carry geopolitical optionality, allied government AI standardization on a particular hyperscaler's infrastructure creates multi-decade lock-in that is worth a significantly higher multiple than commercial cloud contracts.

The capex-to-revenue conversion timeline creates a specific options positioning pattern: institutions go long LEAPS (12-18 month calls) when capex commitments are announced, rather than near-dated calls, because the revenue realization is quarters away. If you see a surge in long-dated call open interest in any hyperscaler immediately following a major capex announcement, that is the institutional bet on the revenue pipeline, not a near-term earnings trade. The peak of that revenue realization, when the data center capacity comes online and starts generating cloud compute revenue, is when you see the near-dated call volume spike and the LEAPS positions get rolled down to shorter durations, locking in the gain from the multiple expansion as forward revenue becomes current revenue.

Second-order beneficiaries of the AI capex cycle also generate options flow that functions as a read-through signal for hyperscaler positioning. Power generation and data center infrastructure companies, Vistra (VST), Constellation Energy (CEG), NRG Energy, and independent power producers with data center co-location exposure, see call flow that often precedes or coincides with hyperscaler capex announcements. When you observe unusual call accumulation in VST or CEG without obvious utility sector news, the institutional read is frequently that a hyperscaler has signed or is about to sign a significant power purchase agreement for a new AI data center cluster. This second-order signal can appear before the hyperscaler announcement is public, making power infrastructure flow a useful leading indicator for AI capex news in the hyperscaler names themselves.

Enterprise customer concentration and churn risk

Options flow in hyperscaler names around earnings is heavily influenced by institutional models of enterprise customer retention and expansion dynamics, the cohort analysis of cloud customer behavior that drives predictable revenue compounding. Each hyperscaler has a different enterprise customer profile and a different mechanism for expanding revenue within its installed base, and the risks and catalysts associated with each are distinct enough to generate different options positioning patterns even when macro conditions are identical.

AWS enterprise customers tend to exhibit very high retention rates once committed, the switching costs of rebuilding production workloads on a different cloud platform are substantial enough that enterprise churn is structurally low. What moves AWS revenue within the enterprise base is not retention but expansion: the rate at which existing customers increase their cloud consumption as they migrate more workloads and adopt higher-value managed services. AWS discloses "remaining performance obligations" (contracted but not yet recognized revenue) in its filings, and the growth rate of this RPO figure is the institutional proxy for enterprise expansion velocity. Rising RPO growth precedes call accumulation in AMZN; flat or declining RPO signals that existing enterprise customers are not expanding consumption, which generates defensive put positioning or reduced call activity ahead of the subsequent earnings print.

Azure's enterprise relationship is uniquely structured around the Microsoft 365 and Teams installed base, hundreds of millions of enterprise users already inside the Microsoft ecosystem who represent a built-in distribution channel for Azure AI upsell. Each major enterprise renewal cycle for M365 agreements is simultaneously an opportunity to expand Azure commitment and add Copilot seats. Options flow in MSFT ahead of major enterprise renewal windows, which correlate with fiscal year-end budget cycles at large enterprises, typically in Q1 and Q3 calendar-year, reflects institutional positioning for whether the upsell rate on renewals is meeting internal forecasts. When channel checks from Microsoft partner resellers (VARs and systems integrators who help enterprise customers negotiate M365 and Azure agreements) indicate that renewal conversations include significant Azure expansion commitments, MSFT call accumulation follows. When those same checks suggest budget pressure is causing enterprises to trim Azure commitments or defer Copilot seat purchases, put hedging or covered call writing appears in MSFT flow.

Google Cloud's enterprise positioning is frequently described as a diversification play, enterprises that are heavily committed to AWS and Azure sometimes choose Google Cloud for specific workloads as a hedge against vendor concentration and as leverage in price negotiations with their primary providers. This creates a "third cloud" dynamic where Google Cloud revenue can grow without necessarily taking share from AWS or Azure; it grows by capturing the marginal workload that enterprises deliberately place outside their primary relationships. When enterprise IT spending surveys show rising interest in multi-cloud architectures specifically for AI workloads (which are less legacy-infrastructure-dependent and therefore more portable), GOOGL call flow often appears as institutions position for Google Cloud's unique benefit from multi-cloud adoption trends.

Cloud pricing dynamics create options flow that is counterintuitive if you are not tracking the competitive rationale. When AWS or Azure announces price reductions on compute or storage services, the initial read is margin compression, and put hedging sometimes appears immediately after pricing announcements. But experienced institutional analysts read cloud price cuts differently: a price cut is a competitive offensive move designed to accelerate workload migration from on-premise and from competing hyperscalers. The revenue impact of attracting a new enterprise workload that runs for five years significantly exceeds the margin sacrifice from the price cut itself. Options flow in the announcing hyperscaler often shows a split response: short-dated puts (pricing the near-term margin miss) alongside longer-dated calls (pricing the workload capture over the contract life), creating a time-spread structure that reflects the difference in time horizons between the cost and the benefit.

Enterprise discount program (EDP) renewal windows are a frequently overlooked options catalyst. AWS, Azure, and Google Cloud all offer multi-year enterprise discount agreements that lock in volume commitments in exchange for pricing concessions. These EDPs typically run 1-3 year terms and renew in clusters based on when the original agreements were signed. When a cohort of large EDP agreements comes up for renewal in the same quarter, it creates a binary outcome: the enterprise either renews (often at higher committed spend, generating a backlog increase) or renegotiates downward or switches providers (generating a backlog decrease and future revenue risk). Options flow in hyperscaler names that is clustered 4-6 weeks before a major earnings print sometimes reflects institutional positioning ahead of an EDP renewal quarter that channel checks suggest will be either strong (call accumulation) or weak (put hedging). These renewal windows are not widely publicized but experienced analysts track them by reading the timing patterns in RPO disclosures across multiple quarters.

Competitive dynamics, options flow as a relative value signal between hyperscalers

Some of the most precise institutional options positioning in the hyperscaler space takes the form of relative value trades rather than directional bets on a single name. When smart money believes Azure is taking market share from AWS in AI workloads, the trade is not simply "buy MSFT calls", it is "buy MSFT calls funded by selling AMZN calls" or "buy MSFT calls alongside AMZN puts," constructing a position that profits from the spread in growth rates rather than from the absolute direction of the cloud sector. Recognizing this relative positioning is important because it explains flow patterns that appear contradictory when viewed on a single-name basis.

Market share shift signals become visible when hyperscaler earnings results are compared across the same calendar period. Each quarter, AWS, Azure, and Google Cloud all report results within a few weeks of each other, and the sequential read-through from one set of results to the next creates a relative positioning opportunity. If Azure reports first and delivers a significant growth acceleration, AMZN options flow in the days before AMZN's print will reflect institutional repositioning based on whether investors expect AWS to match the acceleration or lag it. The asymmetry is that a confirmed market share shift, where Azure accelerates while AWS decelerates in the same quarter, has a larger relative impact on AMZN put positioning than any AWS-specific negative news would, because it implies a structural rather than cyclical issue.

Azure AI services adoption rate versus AWS AI services adoption is the current primary battleground for relative positioning. Microsoft's Copilot products and Azure OpenAI Service have a well-documented enterprise adoption advantage from the OpenAI partnership and the M365 distribution channel. AWS counters with Bedrock (a managed LLM service) and its own custom silicon (Trainium, Inferentia) for training and inference cost optimization. The relative positioning trade between MSFT and AMZN in AI services is tracked through quarterly enterprise AI adoption surveys from research firms like Gartner, IDC, and Forrester, when these surveys show Azure AI winning disproportionately at enterprise accounts, MSFT calls alongside AMZN puts is the institutional expression of that data. The surveys are typically released in the weeks before or after hyperscaler earnings, which is when the relative flow pattern is most visible.

Google Cloud's competitive differentiation runs through its AI infrastructure hardware (TPUs, which are Google-proprietary and optimized for specific AI workloads), its open-source AI commitments (significant investment in open-source model ecosystems that appeal to enterprises wary of OpenAI dependency), and its data analytics heritage (BigQuery, Looker, and the broader data warehouse ecosystem that enterprises are converting into AI training data pipelines). These differentiation vectors appeal to a specific subset of enterprises, particularly those in financial services, healthcare, and life sciences, and options flow in GOOGL sometimes reflects institutional reads on whether Google Cloud is winning or losing in these specific verticals. When pharmaceutical or financial services companies announce major cloud AI partnerships (which is public information), GOOGL call flow sometimes appears simultaneously as the market updates the Google Cloud vertical penetration thesis.

Third-party cloud cost optimization platforms, Datadog for observability, CloudHealth (VMware) and Apptio for cost management, and similar tools, generate usage data that is a leading indicator for hyperscaler cloud growth and potential churn. These platforms have visibility into enterprise cloud spending patterns across AWS, Azure, and Google Cloud simultaneously. When Datadog reports strong cloud infrastructure monitoring growth in its earnings, it is a read-through for hyperscaler volume growth because Datadog's revenue is proportional to the number of cloud instances being monitored. Options flow in hyperscaler names sometimes appears immediately after Datadog earnings for this reason, not because of any business relationship between the companies, but because Datadog's results function as a third-party channel check on overall cloud infrastructure demand. Conversely, when cost optimization platform usage spikes (suggesting enterprises are aggressively cutting cloud spend), it is an early warning signal for hyperscaler growth deceleration that precedes put accumulation.

Developer survey data, particularly the annual Stack Overflow developer survey, JetBrains developer ecosystem survey, and GitHub Octoverse report, functions as a longer-cycle leading indicator for hyperscaler relative positioning. Developers choose which cloud platforms to build on based on tool quality, documentation, pricing, and AI assistant quality; those choices today become enterprise cloud spending patterns 12-24 months from now as the projects they build go into production. Institutional investors who track developer survey data systematically can observe multi-quarter trends in cloud platform preference shifts before those shifts appear in revenue. When three consecutive developer surveys show increasing adoption of AWS developer tools relative to Azure tools, AMZN LEAPS accumulation is a rational institutional response to a signal that the street is not yet pricing into near-term models.

Regulatory and antitrust risk, the put flow layer in hyperscaler options

Alongside the bullish cloud growth thesis, a persistent layer of regulatory and antitrust risk creates a structural put flow component in hyperscaler options that is distinct from earnings-driven positioning. Regulatory risk in cloud is not abstract, it has specific enforcement mechanisms in multiple jurisdictions, concrete compliance cost implications, and the potential to structurally alter the business models that make hyperscaler cloud economics so attractive. Institutional risk managers hedge these exposures through options, creating a put flow pattern that reflects regulatory event risk rather than cloud revenue fundamentals.

The EU Digital Markets Act (DMA) compliance requirements represent the most concrete near-term regulatory risk for cloud bundling practices. The DMA designates large technology platforms as "gatekeepers" and imposes interoperability and unbundling requirements that directly challenge the hyperscaler model of tying cloud infrastructure, AI services, productivity software, and security products into integrated packages that create switching costs. Microsoft's bundling of Azure, Microsoft 365, Teams, and Defender into enterprise agreements is precisely the type of integration the DMA targets. Compliance with DMA unbundling requirements would structurally reduce the enterprise switching costs that maintain Azure's revenue retention rates, and options put positioning in MSFT ahead of major DMA enforcement decisions reflects institutional hedging of this structural risk, not just short-term price speculation.

FTC and DOJ cloud market investigations in the United States have focused on hyperscaler practices including egress fees (charges for moving data out of a cloud provider, which create financial lock-in), contract terms that disadvantage competing software vendors, and AI service bundling practices that leverage infrastructure dominance into AI market dominance. These investigations create binary event risk for all three hyperscalers simultaneously, a significant enforcement action against any one of them creates precedent that immediately reprices the others. Put spread structures in AMZN, MSFT, and GOOGL that appear unrelated to earnings timing are sometimes regulatory hedge positions, priced around the event dates of FTC/DOJ proceedings rather than earnings calendars.

The CLOUD Act and data sovereignty requirements create a geographically specific put flow component in hyperscaler names with significant European revenue exposure. Enterprises in Europe are increasingly required by national law and EU regulation to ensure that their cloud data is stored and processed within EU borders and is not accessible to US government authorities under the CLOUD Act. Compliance with these requirements forces hyperscalers to build separate, isolated EU cloud infrastructure, which is a significant capex cost that generates no revenue premium over standard cloud services. Put hedges in MSFT and GOOGL sometimes reflect institutional assessment of the cost burden of CLOUD Act compliance and EU data residency buildout, particularly ahead of European Commission rulings on data transfer frameworks. However, this same regulatory requirement also creates a CAPEX opportunity: European region buildout, while costly, locks in long-duration enterprise cloud contracts with favorable renewal terms, which is why some institutional positions are call structures on the European region revenue acceleration rather than put hedges on the compliance cost.

Interoperability mandates, requirements that hyperscalers allow enterprise customers to move workloads and data to competing platforms without prohibitive technical or financial barriers, are the most structurally threatening regulatory development for the hyperscaler lock-in model. The current EU regulatory push includes both portability requirements (making it technically feasible to migrate workloads) and egress fee caps (eliminating the financial penalty for leaving a platform). If fully implemented, these mandates would reduce enterprise switching costs significantly, which would compress the revenue retention rates that underpin hyperscaler growth models. Options put flow in all three hyperscalers around interoperability mandate enforcement decisions reflects institutional hedging of the scenario where the lock-in premium in hyperscaler multiples is structurally reduced. The magnitude of this put flow, whether it is small hedges or large directional bets, is a useful signal for how seriously institutional investors are pricing the enforcement probability.

EU data residency requirements, counterintuitively, also create a CAPEX opportunity that generates long-dated call flow alongside the regulatory put hedges. Building out dedicated European cloud regions, data centers physically located within EU borders, staffed by EU citizens, isolated from US government access, requires significant upfront infrastructure investment but locks in enterprise customers in heavily regulated EU industries (financial services, healthcare, government) for long contract terms. When a hyperscaler announces a major European sovereign cloud region buildout, the options market's response is sometimes a barbell: near-dated puts pricing the capex cost, alongside longer-dated calls pricing the revenue locked in by the sovereign cloud commitment. This barbell structure is the options expression of the tension between regulatory compliance cost and the durable revenue stream that compliance unlocks in a regulated market.

Case studies: three hyperscaler options flow sequences

Abstract principles about cloud segment tracking and regulatory risk become most useful when grounded in specific historical flow sequences. The following three case studies illustrate how the signals described above translated into concrete options positioning with measurable outcomes, each representing a distinct type of hyperscaler options thesis that institutional flow expressed before the catalyst confirmed it.

BULLISH, MSFT Azure AI call accumulation before Q3 2024 earnings

Starting approximately six weeks before Microsoft's fiscal Q3 2024 earnings print, options flow in MSFT showed an unusual pattern of call accumulation concentrated in the $240 strike with 60-90 day expiration. The flow was notable for three characteristics: it arrived in sweep format (single large prints rather than small accumulated positions), the open interest buildup was concentrated at a strike that implied meaningful upside from the prevailing price, and the timing was specifically in weekly windows when enterprise AI survey data from Morgan Stanley and Goldman Sachs was published showing accelerating Copilot seat adoption at large enterprise accounts. The institutional thesis was straightforward: Azure growth had decelerated to 28% in the prior quarter, and the survey data suggested AI workload additions from Copilot deployment would re-accelerate growth to 31% or above. When Microsoft reported, Azure growth came in at 31%, the re-acceleration thesis confirmed, and Copilot AI seat expansion surprised materially above the consensus model. The $240 calls, purchased six weeks before earnings at a premium that implied roughly 4% upside as the breakeven, returned approximately 280% as MSFT moved through $240 and above on the earnings reaction. The key reading signal was the call accumulation pattern clustering specifically around enterprise AI adoption survey publication dates rather than arriving uniformly across the pre-earnings period, a timing signature consistent with institutional models updating on channel check data rather than generic directional speculation.

BEARISH, GOOGL put flow before Q4 2022 earnings

The Q4 2022 earnings cycle for Alphabet produced one of the most clearly telegraphed put flow sequences in the hyperscaler space. Beginning approximately four weeks before the earnings print, GOOGL options showed elevated put buying in the $85-90 strike range (pre-split equivalent), with 30-day expiration concentrated at a premium level that implied approximately 8-10% downside as the breakeven. The institutional thesis that the flow expressed was twofold: first, YouTube advertising revenue was expected to miss consensus as digital advertising budgets were compressed by rising interest rate concerns and recession fears, and advertiser-specific channel checks from marketing agencies were showing sharply reduced video ad spending. Second, and more directly relevant to the cloud segment thesis, Google Cloud was still operating at a significant operating loss at that time, and the consensus model implied a Google Cloud revenue figure that CIO survey data suggested was aggressive given enterprise cloud budget freezes. When Alphabet reported, the result confirmed both concerns: YouTube advertising revenue missed by a meaningful margin, and Google Cloud revenue came in below the most bullish segment model. The stock fell approximately 9% on the earnings reaction. The $85 puts with 30-day expiry gained approximately 190% from the price paid to the post-earnings intrinsic value. The distinguishing signal was the dual catalyst structure, both advertising and cloud weakness in the same print, which the put flow implied by the size and strike selection: the $85 strike required both segments to disappoint simultaneously, which is a lower-probability event than a single-segment miss, suggesting institutional conviction in a broad disappointment thesis rather than a single-variable hedge.

MIXED, AMZN risk-reversal structure before Q1 2023 earnings

The Q1 2023 AMZN earnings cycle produced one of the more sophisticated options flow patterns in the hyperscaler space: a risk-reversal structure rather than a simple directional bet. In the four weeks before Amazon's Q1 2023 earnings print, flow showed simultaneous call buying in the $105-110 strike range and put selling in the $90-95 strike range, a classic risk-reversal that collected premium on the short put side to subsidize the call purchase, creating a defined-risk bullish structure at near-zero net cost. The thesis expressed by this structure was nuanced: AWS was expected to re-accelerate from the deceleration that had been the overhang on AMZN for several prior quarters, which the call side expressed. Simultaneously, Amazon's retail segment had been showing cost improvement from its logistics network restructuring, which reduced the probability of a catastrophic retail miss that would push the stock below $90, which the put-selling side expressed. When Amazon reported, AWS margins beat substantially (generating the operating income surprise that the calls were positioned for), and the retail segment produced better-than-expected operating efficiency. The call side of the risk-reversal returned approximately 145% as AMZN moved sharply above the $105 strike on the earnings reaction. The put-sell component expired worthless, allowing the full premium collected to be retained. This flow pattern, risk-reversals rather than simple calls or puts, is characteristic of institutional positioning that has high conviction on a primary thesis (AWS re-acceleration) while managing a secondary risk (retail miss) through the structure, rather than simply buying optionality in one direction. When you observe risk-reversal flow in a hyperscaler name ahead of earnings, it typically signals that a sophisticated participant is expressing a precise two-variable view on the quarter, not simply making a directional bet.

Summary

Options flow in AMZN, MSFT, and GOOGL is fundamentally cloud-segment positioning rather than whole-company positioning, AWS operating margins, Azure growth percentage, and Google Cloud profitability inflection are the primary variables driving institutional call and put accumulation in each name. NVDA earnings and data center capex announcements are the strongest leading indicators for all three simultaneously, as they confirm or disconfirm the AI infrastructure investment cycle that drives future cloud revenue. CIO surveys and enterprise spending data function as the channel-check layer that institutional analysts use to refine their cloud revenue models before each quarterly print, creating the pre-earnings flow patterns that appear in the options tape. Reading hyperscaler flow means tracking these cloud-specific signals alongside the cross-name AI infrastructure thesis, the whole-company fundamentals matter far less than the trajectory of the cloud segment driving each stock's multiple.

Track hyperscaler flow across AMZN, MSFT, and GOOGL

RadarPulse surfaces simultaneous call and put flow across the cloud hyperscalers, so you can see when institutional positioning is building across AWS, Azure, and Google Cloud before the quarterly prints confirm the thesis.

Join the waitlist