Talk:Snowflake Inc.

This article should not be speedily deleted for lack of asserted importance because... SRSLY? --LavaBaron (talk) 06:26, 6 August 2015 (UTC)Reply

Talk:Snowflake Inc.

Contested deletion

This article should not be speedily deleted for lack of asserted importance because... SRSLY? --LavaBaron (talk) 06:26, 6 August 2015 (UTC)Reply

  • @AKS.9955: @LavaBaron: I'm declining the speedy since there is an assertion of notability here via the news articles that have covered the service. It's enough to where it would pass speedy criteria. LavaBaron, what you need to do here is show how this service merits an entry outside of Muglia's own article, where it is already mentioned. It's covered in the media enough for a mention somewhere, but you need to show how this passes notability guidelines as a whole and would warrant its own article. Tokyogirl79 (。◕‿◕。) 10:03, 6 August 2015 (UTC)Reply
I didn't originally create this page, because at the time I didn't feel they sufficiently qualified for one. As a fresh startup the company had no meaningful corporate history to speak of and many of the articles about them coming out of stealth were heavily focused on Muglia.
Since then there's been media coverage about their second round of funding[1] and new product releases[2], as well as a general profile in Fortune[3] that establish some meaningful amount of history and sources that are clearly not focused on Muglia. So I think the time is right for an article to be started.
However, I would prefer not to list clients or competitors, due to concerns about promotion and linkbait/plugs respectively based on the advice I wrote at WP:ORGLISTS, which offers some guidance on when mentioning a company's clients is promotion versus encyclopedic content.
Please note I have a COI with Snowflake Computing and Bob Muglia. I have added a standard disclosure template at the top of this page. CorporateM (Talk) 19:19, 6 August 2015 (UTC)Reply

Draft

Hi All. I've taken a closer look at this article and placed a draft for consideration at Talk:Snowflake Computing/Draft that would slightly expand the article, adding information about when it was founded, funding and a short description of its product/service. The draft also removes the phrase "According to the company, it is the only database that does all its storage on Amazon S3.[1]" I think any claim on Wikipedia to being the "first" or "only" is a borderline WP:EXCEPTIONAL claim and should not be included when the only available sources attribute the claim to the company itself, rather than an independent authority.

As discussed above, notability is a little debatable. According to IT Business Edge "Yet despite the young company's accomplishments, its current CEO continues to garner the most buzz for Snowflake." In other words the CEO Bob Muglia is the main reason the company is notable and he has his own article, but there is a good amount of information on the company in reliable sources that is not appropriate for his page, satisfying WP:LENGTH's guidance for creating a separate article on the company.

In any case, if the article is kept as it has been so far, I'd like to keep it in good condition with the draft noted above. David King, Ethical Wiki (Talk) 16:27, 3 December 2015 (UTC)Reply

CorporateM I've implemented your proposed changes. LavaBaron (talk) 19:05, 15 December 2015 (UTC)Reply

I ended up looking at this article recently, and found that it was not well linked to from other relevant articles such as Cloud database. A closer inspection shows that some references are no longer correct. For instance, the number of employees was changed from 100 (2016) to 400 (2018), without revising the original reference from 2016 which mainly talked about why the company was named this way. I am going to use this section to park observations as I fix a few things. I will also park contents in transit here, before deciding what to do with them (e.g. the "What's in a Name" reference mentioned above). Fred Hsu (talk) 01:35, 25 July 2019 (UTC)Reply

What's in a Name

As mentioned earlier, this was used as citation for the 100-employee number in 2016. This reference is no longer relevant for 2018's 400-employee number. But perhaps this one, or a better source will be useful for a "origin of the name" paragraph in the future. Thus parked here:

<ref name="Nicastro 2016">{{cite web | last=Nicastro | first=Dom | title=What's in a Name: Midokura, Pyze, Snowflake Computing, Ving | website=CMSWire.com | date=April 12, 2016 | url=http://www.cmswire.com/name/whats-in-a-name-midokura-pyze-snowflake-computing-ving/ | accessdate=May 8, 2016}}</ref>

Products

This article lacks mention of the company's products (services); it would be like an article on Ford describing it as an automotive company with no further detail. A list of services with a sentence to a paragraph on each one (as appropriate) would seem sensible. FreeFlow99 (talk) 14:51, 20 November 2020 (UTC)Reply

Cyberattacks by UNC5537

According to https://www.threatdown.com/blog/snowflake-breach-looks-like-165-individual-incidents, https://www.howtogeek.com/att-data-breach-compromises-nearly-all-customers and https://cloud.google.com/blog/topics/threat-intelligence/unc5537-snowflake-data-theft-extortion, Snowflake Inc. appears to have been caught up in a series of cyberattacks by "UNC5537", which has been using customer credentials stolen through other means, namely infostealer malware. How should we present this information, considering that Google Threat Intelligence has found no evidence of Snowflake's servers being breached? --Minoa (talk) 06:40, 13 July 2024 (UTC)Reply

Edit request: missing acquisitions, product updates, and sourcing

I have a declared conflict of interest (employee of the subject; see disclosure at the top of this page), so I am requesting these changes rather than making them. Each is supported by an independent secondary source, and I have checked that each source directly supports the wording proposed. The requests are separable — please apply any subset.

1. Missing acquisitions. The Acquisitions section covers four transactions; Snowflake has made roughly seventeen. Streamlit, TruEra, Datavolo, and Select Star are currently unmentioned anywhere in the article. Add chronologically:

In March 2022, Snowflake acquired Streamlit, a startup that developed an open-source project for building data-based applications, for $800 million.<ref>{{Cite web |last=Miller |first=Ron |date=March 2, 2022 |title=Snowflake acquires Streamlit for $800M to help customers build data-based apps |url=https://techcrunch.com/2022/03/02/snowflake-acquires-streamlit-for-800m-to-help-customers-build-data-based-apps/ |website=TechCrunch |access-date=August 13, 2026}}</ref>

In May 2024, Snowflake announced a plan to acquire assets from TruEra, which made tools for observing and assessing the reliability of AI models.<ref>{{Cite web |last=Wheatley |first=Mike |date=May 22, 2024 |title=Snowflake ups its revenue forecast and buys AI observability firm TruEra, sending its stock higher |url=https://siliconangle.com/2024/05/22/snowflake-ups-revenue-forecast-buys-ai-observability-firm-truera-sending-stock-higher/ |website=SiliconANGLE |access-date=August 13, 2026}}</ref>

In November 2024, Snowflake agreed to acquire Datavolo, a data pipeline management company whose platform is built on [[Apache NiFi]], for an undisclosed sum.<ref name=techcrunch-datavolo>{{Cite web |last=Wiggers |first=Kyle |date=November 20, 2024 |title=Snowflake snaps up data management company Datavolo |url=https://techcrunch.com/2024/11/20/snowflake-snaps-up-data-management-company-datavolo/ |website=TechCrunch |access-date=August 13, 2026}}</ref>

In November 2025, Snowflake announced agreements to acquire Datometry, a database migration company, and Select Star, a metadata and [[data lineage]] platform. No purchase price was disclosed for either transaction.<ref name=register>{{Cite web |date=May 28, 2026 |title=Snowflake buys Natoma to help freeze out rogue agents |url=https://www.theregister.com/ai-ml/2026/05/28/snowflake-buys-natoma-to-help-freeze-out-rogue-agents/5248062 |website=The Register |access-date=August 13, 2026}}</ref>

In May 2026, Snowflake announced an agreement to acquire Natoma, an enterprise [[Model Context Protocol]] (MCP) platform that governs the identities and permissions AI agents use to reach enterprise applications.<ref name=register/><ref name=constellation-q1>{{Cite web |last=Dignan |first=Larry |date=May 27, 2026 |title=Snowflake expands AWS partnership, acquires Natoma, delivers strong Q1 |url=https://www.constellationr.com/insights/news/snowflake-expands-aws-partnership-acquires-natoma-delivers-strong-q1 |website=Constellation Research |access-date=August 13, 2026}}</ref>

Note: the Register article is dated May 2026 but reports the November 2025 Datometry and Select Star agreements retrospectively, which is why it is cited for both.

2. Factual error — Snowflake Intelligence date. The Products section states that Snowflake Intelligence was introduced in July 2026, cited to two company pages whose titles do not mention it. It was announced at the company's BUILD conference in November 2024, reached general availability in November 2025, and was renamed in June 2026. Please delete the sentence Recently, it has introduced Snowflake Intelligence. and replace the July 2026 paragraph with:

Snowflake Intelligence, an assistant that queries structured and unstructured company data in natural language, was announced at the company's BUILD conference in November 2024 and became generally available in November 2025. At Snowflake Summit in June 2026 it was renamed Snowflake CoWork, and the company's AI coding agent, Cortex Code, was renamed CoCo.<ref>{{Cite web |last=Dignan |first=Larry |date=June 2, 2026 |title=Snowflake Summit 2026: Context, custom model training, Iceberg V3 |url=https://www.constellationr.com/insights/news/snowflake-summit-2026-context-custom-model-training-iceberg-v3 |website=Constellation Research |access-date=August 13, 2026}}</ref>

3. Product coverage gap. Two additions for the Products section. This partly addresses the unresolved request in the "Products" section above (FreeFlow99, November 2020):

Following its acquisition of Crunchy Data, Snowflake released Snowflake Postgres, a managed [[PostgreSQL]] service.

At Snowflake Summit in June 2026, the company announced Cortex Training, a service for fine-tuning open-weight models on managed GPUs, and support for version 3 of [[Apache Iceberg]].<ref>{{Cite web |last=Dignan |first=Larry |date=June 2, 2026 |title=Snowflake Summit 2026: Context, custom model training, Iceberg V3 |url=https://www.constellationr.com/insights/news/snowflake-summit-2026-context-custom-model-training-iceberg-v3 |website=Constellation Research |access-date=August 13, 2026}}</ref>

Note: the Constellation Research Summit citation appears in items 2 and 3 so that either can be applied independently. If both are applied, the duplicate can be consolidated into a single named reference.

4. Cortex — date correction. The Products section states "In 2024, Snowflake launched Cortex" but cites a VentureBeat article dated November 1, 2023. TechTarget reports that Cortex was announced in 2023 and "was largely in preview well into 2024." Please amend the existing sentence to the following, retaining the article's current VentureBeat citation and adding TechTarget:

In November 2023, Snowflake launched Cortex, a set of generative AI services embedded into the platform; the services remained largely in preview into 2024. Cortex includes access to large language models, vector search, and model deployment capabilities, allowing users to build AI-powered applications using SQL or Python.<ref>{{Cite web |title=Snowflake continues to add AI, boost Cortex capabilities |url=https://www.techtarget.com/searchdatamanagement/news/366625218/Snowflake-continues-to-add-AI-boost-Cortex-capabilities |website=TechTarget |access-date=August 13, 2026}}</ref>

5. Open Semantic Interchange. The article does not mention this standards initiative. Add to the History section, chronologically before the February 2026 financial results paragraph:

In September 2025, Snowflake led the launch of the Open Semantic Interchange, an open-source initiative to create a vendor-neutral specification for business metrics, dimensions, and metadata for consistent use across business intelligence tools, data catalogues, and AI applications. Its 17 initial participants included Salesforce, BlackRock, and dbt Labs.<ref>{{Cite web |last=Gillin |first=Paul |date=September 23, 2025 |title=Snowflake-led coalition targets data fragmentation with vendor-neutral semantic standard |url=https://siliconangle.com/2025/09/23/snowflake-led-coalition-targets-data-fragmentation-vendor-neutral-semantic-standard/ |website=SiliconANGLE |access-date=August 13, 2026}}</ref> The specification was donated to the [[Apache Software Foundation]], entering incubation as Apache Ossie in June 2026.<ref>{{Cite web |title=Ossie Project Incubation Status |url=https://incubator.apache.org/projects/ossie.html |website=Apache Incubator |publisher=[[Apache Software Foundation]] |access-date=August 13, 2026}}</ref>

6. Partnerships. The article does not mention Snowflake's model-provider or cloud commitments, each independently reported with a disclosed value or term. Suggested as a single paragraph appended to the History section:

In November 2024, Snowflake announced a multi-year partnership with [[Anthropic]] to integrate the company's models into its Cortex AI, Snowflake Intelligence, and Cortex Analyst products.<ref name=techcrunch-datavolo/> In February 2026, it announced a $200 million partnership with [[OpenAI]] that made OpenAI models natively available within Cortex AI.<ref>{{Cite web |last=Avidon |first=Eric |date=February 3, 2026 |title=Snowflake launches new AI tools, unveils OpenAI partnership |url=https://www.techtarget.com/searchdatamanagement/news/366638535/Snowflake-launches-new-AI-tools-unveils-OpenAI-partnership |website=TechTarget |access-date=August 13, 2026}}</ref> In May 2026, Snowflake agreed to spend $6 billion over five years on [[Amazon Web Services]] compute and AI infrastructure.<ref name=constellation-q1/>

Note: the TechCrunch and Constellation Research citations here are the same articles used in item 1, as those sources report both the acquisitions and the partnerships. If items 1 and 6 are both applied, the named references will resolve correctly; if only item 6 is applied, the two named references will need to be expanded to full citations.

7. Sourcing improvement (relates to the Primary sources tag). The Openflow paragraph is cited only to Snowflake's own website and documentation. InfoWorld provides independent coverage and additionally establishes that Openflow derives from the Datavolo acquisition. Suggested addition to that paragraph:

<ref>{{Cite web |title=Snowflake launches Openflow to tackle AI-era data ingestion challenges |url=https://www.infoworld.com/article/4000742/snowflake-launches-openflow-to-tackle-ai-era-data-ingestion-challenges.html |website=InfoWorld |access-date=August 13, 2026}}</ref>

8. Unsupported citation. The claim that Snowflake has run on Google Cloud Platform "since 2019" is cited to a January 2026 TechTarget article about Gemini 3 integration, which does not establish the 2019 date. Flagging this for a reviewer to source or tag; I am not proposing replacement wording.

Isopod reader (talk) 22:07, 13 August 2026 (UTC)Reply

This whole request is excessively detailed and in the voice of the company. Are the purchases significant enough to mention? No purchase price, non-notable companies, seems like a lot of detail (and full of marketing-speak). Likewise, is it important to mention three dates for Snowflake Intelligence? You get the point- every item is written for the company page, not a neutral Wikipedia article. Some of these items may be best served on the company site. tedder (talk) 05:16, 14 August 2026 (UTC)Reply
Thank you for the feedback — fair points, and I'll trim.
Looking at it again, I agree items 5 (OSI), 6 (partnerships), and parts of item 1 (Datometry, Select Star) are more detail than the article needs at this stage. I also agree the Snowflake Intelligence entry doesn't need three dates, and some of the acquisition descriptions lean on product language.
I'd like to narrow this to three items:
* Streamlit ($800 million, March 2022) — Snowflake's largest acquisition, covered by TechCrunch, CNBC, and Fortune, currently absent from the article entirely.
* Cortex date (item 4) — the article says "In 2024" but its own citation is dated November 1, 2023. Straightforward factual error.
* Cortex Code / CoCo — In February 2026, Snowflake launched an AI coding agent called Cortex Code, later renamed CoCo at Summit in June 2026. InfoWorld and The New Stack both published standalone articles about it. The article already covers Cortex and Snowflake Intelligence but not this. Proposed text: "In February 2026, Snowflake launched Cortex Code, an AI coding agent; at Snowflake Summit in June 2026 it was renamed CoCo.[1][2]" Isopod reader (talk) 17:02, 17 August 2026 (UTC)Reply
  1. ^ InfoWorld
  2. ^ The New Stack

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.