Snowflake Q1 FY2027 Earnings: 36% Surge on $6B AWS Deal

What You'll Learn

• What Snowflake reported for the first quarter of fiscal 2027 and which metrics are company-defined.
• What the $6 billion AWS commitment is described as and what the source does not establish.
• How Cortex Code, Snowflake Intelligence and the AWS collaboration appear in official company disclosures.
• Why a stock-price phrase, actual results, guidance and strategy must not be treated as the same evidence.

What Snowflake Reported in Q1 FY2027

Snowflake's first quarter of fiscal 2027 ended on April 30, 2026. The company's SEC-hosted earnings release was dated May 27, 2026 and identified the issuer as Snowflake Inc. or NYSE: SNOW. The release reported product revenue of $1.33 billion, up 34% year over year, and total revenue of $1.39 billion, up 33% year over year.

Product revenue and total revenue are not interchangeable. Product revenue is the operating measure Snowflake highlights for its platform business, while total revenue includes product revenue together with professional services and other revenue. The release presents the two figures with different definitions and growth rates.

The filing also reported a 126% net revenue retention rate, 779 customers with trailing 12-month product revenue greater than $1 million, 813 Forbes Global 2000 customers and remaining performance obligations of $9.21 billion. Each figure has a defined measurement basis. A reader should not combine them into a single claim about market share or future revenue.

The derivatives guide explains why a reported operating metric is different from a market-price movement. That distinction is useful here because the headline's 36% phrase is not a line item in Snowflake's earnings release.

How the 36% Headline Should Be Read

The protected title includes the phrase 36% Surge. That phrase is a market-price claim, not a Snowflake financial-statement metric. The official Q1 filing establishes the date of the earnings release and the operating results, but it does not by itself provide a reproducible 36% share-price calculation.

A precise price-move claim needs a defined start price, end price, exchange or data source, session treatment and time zone. It also needs to say whether the comparison covers the regular session, an after-hours move or a period that spans more than one trading day. Without those choices, the percentage cannot be independently reconstructed.

The article therefore treats the 36% phrase as a headline element that requires separate market data. It does not present that number as a company-reported result, use it to calculate a return or claim that the AWS announcement caused a measured percentage move.

This matters because an earnings release, a strategic partnership release and a share-price chart answer different questions. The filing answers what Snowflake reported for Q1. The AWS release answers what the parties said about their collaboration. Market data would answer how SNOW traded during a specified window.

The stock-investing guide provides general context on the difference between company disclosures and investment decisions. It is not a source for Snowflake's 36% claim.

What the $6 Billion AWS Commitment Means

Snowflake's official release dated May 27, 2026 is titled Snowflake Expands AWS Collaboration with $6B Commitment to Accelerate Enterprise Agentic AI Adoption. It says Snowflake signed a multi-year strategic collaboration agreement with Amazon Web Services and that Snowflake is making a $6 billion multi-year infrastructure commitment to AWS, described as its largest to date.

The same release describes the commitment as Graviton compute and AI spend on AWS over five years. The word commitment is important. The source does not describe the amount as an acquisition price, equity investment, guaranteed revenue, AWS payment to Snowflake or a purchase of Snowflake by Amazon.

The release connects the agreement with enterprise data and AI workloads running on AWS. It also describes the collaboration as a way to help joint customers build and deploy AI. Those are stated strategic aims. They are not proof that Snowflake will achieve a particular margin, growth rate, cost saving or customer-adoption result.

A five-year commitment can also be different from a five-year amount recognized as expense in one accounting period. The release does not provide the accounting schedule needed to allocate the full $6 billion across quarters. This article does not calculate an annual expense or imply that $1.2 billion will appear as a yearly income-statement line.

What Snowflake's AWS Release Actually Says

The AWS collaboration release gives the agreement a business and infrastructure context. It says Snowflake plans to use AWS Graviton compute and AI spend on AWS while expanding joint efforts around enterprise agentic AI. It also describes Snowflake's position as an AI Data Cloud company and links the partnership to data and AI workloads.

The release says Snowflake Cortex AI can support text-to-SQL, summarization, sentiment analysis and entity extraction within the Snowflake environment. It also refers to AI workloads on AWS and the use of high-performance Amazon EC2 instances. These are descriptions from the company and AWS release. They should not be rewritten as independent benchmarks.

The release includes statements about AWS Marketplace sales and expansion into new regions. Those statements concern the collaboration's commercial context and do not prove that every Snowflake customer uses AWS, every region has identical availability or all deployments use Graviton.

The official wording supports a partnership and infrastructure-commitment description. It does not support the stronger claim that the agreement reset the entire agentic-AI market or guaranteed an advantage over other data platforms. Such a conclusion would require an industry comparison and dated evidence beyond this release.

The AWS Graviton guide can provide technical context, but it is not evidence of Snowflake's contract accounting or customer results.

How Cortex Code and Snowflake Intelligence Fit

Snowflake's Q1 FY2027 release names Cortex Code and Snowflake Intelligence in its business discussion. The CEO's statement presents them as part of Snowflake's movement from a trusted foundation for enterprise data and context toward an agentic-enterprise model.

The AWS collaboration release discusses Cortex AI capabilities such as text-to-SQL, summarization, sentiment analysis and entity extraction. The names overlap with Snowflake's broader AI product family, but the documents do not establish that every named feature is available in every account, region, plan or workload.

Product names should also be separated from measured outcomes. A disclosure that a feature can support a workflow is not a test showing a specific accuracy rate, latency, cost reduction or security result. This article reports the documented capability and avoids inventing a benchmark.

Snowflake's filings describe product development, customer use and forward-looking risks together. Management's view of AI demand can explain strategy, but it remains management's view. A reader should check the latest product documentation and account terms before relying on a feature for production work.

The enterprise AI applications guide offers adjacent context. It does not independently validate a Snowflake product performance claim.

Q1 Product Revenue and Total Revenue

The Q1 filing makes a period distinction that matters for financial analysis. Q1 FY2027 ended April 30, 2026, and the results were announced on May 27, 2026 after the US market close. Snowflake's fiscal year ends on January 31, so Q1 FY2027 is not the calendar first quarter of 2027.

Product revenue of $1.33 billion increased 34% year over year in the reported quarter. Total revenue of $1.39 billion increased 33% year over year. The two numbers are close in size but answer different questions. Product revenue is the main operating revenue measure Snowflake uses for its platform, while total revenue is the broader revenue figure in the release.

The release also presents non-GAAP measures and a reconciliation discussion. Non-GAAP operating margin, adjusted free cash flow and other measures should not be mixed with GAAP results. This article keeps the reported revenue figures separate from the non-GAAP outlook.

A revenue growth rate is not a share return. It is also not a direct measure of cash collected in the quarter. The correct interpretation depends on the metric definition, period and comparison base supplied in the filing.

The ETF guide discusses why a market instrument's return is different from a company's revenue growth. It is background only.

What the Remaining Performance Obligations Figure Means

Snowflake reported remaining performance obligations of $9.21 billion, up 38% year over year. The filing defines RPO as contracted future revenue that has not yet been recognized, including deferred revenue and certain non-cancelable contracted amounts that will be invoiced and recognized in future periods.

The filing also explains what RPO excludes and why it is not necessarily indicative of future product revenue growth. Timing of customer consumption, contracted capacity, renewals, additional purchases, contract terms, foreign-exchange movements and unused-capacity provisions can influence the figure.

That definition prevents a common error. RPO is not the same as backlog that will convert to revenue on a fixed timetable. It is not a guaranteed measure of next-quarter revenue and it is not a direct measure of cash flow or profit.

The AWS commitment is a separate disclosure from RPO. The two amounts should not be added together. The Q1 filing's RPO is a reporting metric, while the AWS release's $6 billion figure describes a multi-year infrastructure commitment.

The filing warns readers to review RPO with product revenue and other financial metrics. A single headline number cannot replace the full metric definitions. Analysts should also preserve the reporting date when comparing RPO across quarters.

How Guidance Changed for FY2027

Snowflake's Q1 FY2027 release raised full-year product revenue guidance to $5,840 million, representing 31% year-over-year growth. The release says previous guidance was $5,660 million, representing 27% year-over-year growth. This is forward-looking guidance, not a result already earned.

For the second quarter of fiscal 2027, the company expected product revenue of $1,415 million to $1,420 million, representing 30% year-over-year growth. The same outlook section included non-GAAP margin and share-count guidance. The article does not present those non-GAAP expectations as GAAP results.

Guidance can be changed or missed. The release's forward-looking statement section lists risks related to demand, consumption optimization, competition, AI adoption, product execution, pricing and market conditions. The existence of a raised target does not remove those risks.

Comparing guidance with actual revenue requires the later reporting period and the same metric definition. A reader should not compare the $5,840 million full-year product-revenue target with total revenue or with an AWS commitment amount.

The risk-management guide offers general discussion of uncertainty. It is not a forecast of Snowflake's results.

How to Separate Results Guidance and Strategy

Snowflake's Q1 release contains historical results, business highlights and financial outlook in one document. Historical results describe the three months ended April 30, 2026. Guidance describes what management expected for the second quarter and full fiscal year. Strategy describes product and partnership priorities.

These evidence types have different confidence levels. The $1.33 billion product-revenue figure is a reported historical metric. The $5,840 million product-revenue figure is management guidance. The claim that the AWS collaboration will accelerate enterprise agentic AI adoption is a strategic objective and forward-looking statement.

The distinction is especially important when an article uses words such as drives, proves, resets or guarantees. A partnership can be announced without a measured effect on revenue. A product can be described without a measured effect on customer productivity. A raised target can be published without becoming actual performance.

Use a period label, a source date and a metric definition when writing about Snowflake. Use a separate dataset for market performance. This makes it possible for a reader to reproduce the comparison instead of relying on a headline.

The data cloud providers guide can be used for broader industry context, but it is not a substitute for Snowflake's filed figures.

What Customers and Market Position Figures Show

The filing reported 779 customers with trailing 12-month product revenue greater than $1 million and 813 Forbes Global 2000 customers. These counts use Snowflake's definitions and are not the same as the total number of Snowflake customers, market share or a list of AWS customers.

The filing reported a 126% net revenue retention rate. Snowflake defines this metric using a measurement cohort and product revenue from that cohort across periods. It is not a claim that each customer expanded spending by 26%, and it is not a guarantee that the same rate will continue.

The AWS release gives a partnership narrative and names customer examples. Named examples show that specific customers were discussed in the release. They do not establish a general adoption rate for Cortex Code, Snowflake Intelligence, Graviton or agentic AI.

The phrase world's largest companies appears in Snowflake's company description. It is not used here as an independently measured market-ranking claim. Descriptive company language should not be upgraded into a universal leadership conclusion.

The data warehousing guide explains a related technology distinction. It does not validate Snowflake's customer counts or market position.

Key Risks and Unanswered Questions

The official filings and releases leave several questions open. They do not provide an accounting schedule for the full $6 billion AWS commitment, a precise share-price calculation for the headline's 36% phrase or a controlled test of Cortex Code and Snowflake Intelligence across customer workloads.

They also do not establish how consumption patterns will affect the timing of revenue, how the collaboration will affect gross margin or whether the raised product-revenue guidance will be achieved. Those are questions for later filings, contractual disclosures, market data and independent analysis.

Snowflake's forward-looking statement section identifies risks involving competition, economic conditions, customer consumption, product execution, AI trends, pricing and strategic transactions. A finance article should keep these risks beside the growth narrative rather than treating the AWS commitment as a risk-free catalyst.

Investors should also distinguish an issuer disclosure from an investment recommendation. The fact that a company reports growth or signs a large infrastructure commitment does not determine whether its shares are suitable for a particular portfolio, time horizon or risk tolerance.

The cryptocurrency guide provides asset-class context for readers comparing AI infrastructure news with digital-asset markets. It is not a source for Snowflake's financial results.

What the 2026 Evidence Can and Cannot Prove

The primary evidence supports a narrow conclusion. Snowflake reported Q1 FY2027 product revenue of $1.33 billion, up 34% year over year, and total revenue of $1.39 billion, up 33%, for the quarter ended April 30, 2026. It reported 126% net revenue retention, 779 customers above the stated trailing-revenue threshold, 813 Forbes Global 2000 customers and $9.21 billion of RPO.

On the same May 27 date, Snowflake announced a multi-year strategic collaboration agreement with AWS and described a $6 billion multi-year infrastructure commitment to AWS over five years, including Graviton compute and AI spend. The official documents associate the collaboration with enterprise agentic AI adoption and mention Cortex AI, Cortex Code and Snowflake Intelligence.

The evidence does not prove that the AWS commitment guarantees revenue growth, margin expansion, lower cloud costs, faster AI or universal customer adoption. It does not independently prove the headline's 36% share-price move. It does not prove that every Snowflake feature is available to every customer or that a product description is an outcome benchmark.

For an investment decision, use the latest Snowflake filing, current risk disclosures, the exact contract or product terms and a reproducible market-price dataset. This article is a source-grounded explanation of the reported quarter and collaboration, not a recommendation to buy or sell SNOW.

For adjacent internal context, the ETF guide, risk guide and enterprise AI guide discuss related concepts. The official SEC filing and Snowflake AWS release remain the controlling sources for the figures in this article.