06-reference/research

snowflake intelligence vs cowork naming standard

2026-09-15·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
snowflakecoworknamingphdatadiscovery

Snowflake Intelligence or Snowflake CoWork: Which Name to Use With Clients in H2 2026

The question

"Post-rename, is 'Snowflake Intelligence' being fully retired or kept as a doc alias vs 'CoWork'? Confirm which name Snowflake SEs and RFPs will standardize on for H2 2026 so the DSA uses the client-current term."

Context: this is a naming question for phData discovery conversations. The earlier briefs already settle what the product is and which parts are GA. This brief covers only the name.

Headline: Snowflake has retired "Snowflake Intelligence" as the product name. It is not a documented alias. Every current Snowflake doc, billing and pricing page, and account-usage page we checked says "Snowflake CoWork". The old doc URL for the usage-history view now returns a permanent redirect (HTTP 308) to the CoWork page. The old name still appears in a few places: the SQL object and command names (the "Snowflake Intelligence Object", ALTER SNOWFLAKE INTELLIGENCE), the iOS App Store listing, one architecture-diagram alt text, and third-party content. Use this rule: say "Snowflake CoWork", recognize "Snowflake Intelligence", and type whatever the client's account actually shows.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The answer: retired as a brand, still present as residue in the product. Snowflake has not kept "Snowflake Intelligence" as a documented alias. No docs page calls it an alias, and the old URLs redirect instead of carrying both names. Snowflake has also not finished removing it from the product. The name remains wherever renaming would break customer code or needs a separate release process: the SNOWFLAKE INTELLIGENCE DDL keyword, the "Snowflake Intelligence Object" that agents are added to, and possibly the legacy account-usage view name. It also remains on the iOS App Store listing. This pattern is what you get when a marketing rename moves faster than the SQL surface. Renaming DDL keywords usually needs a behavior-change bundle and a deprecation window, and we found none announced. Expect the old name in SQL through H2 2026 even as it disappears from everything else.

What Snowflake SEs and RFPs will use in H2 2026: "Snowflake CoWork", with medium-high confidence. The pricing page and billing line say only "Snowflake CoWork". RFP answers and order forms are drafted from those documents, so a client's procurement team will see CoWork on invoices and in consumption reporting. The confidence is below "high" only because we could not see Snowflake's internal SE or partner-portal collateral directly. Clients will still bring the old name. Anyone who piloted the product in its first seven months under the old name, from GA on 2025-11-04 to the rename on 2026-06-02, has internal documents, tickets and budget lines that say "Snowflake Intelligence". Older RFPs copied from those documents will too.

The usage rule for the DSA:

Why this is in the vault

It gives the phData DSA/TAL role a dated, source-cited naming rule for discovery calls, SOWs and RFP responses. It also updates the 2026-07-07 brief's "Snowflake Intelligence, now CoWork" advice to CoWork-first, now that billing and docs have fully switched.

Open follow-ups

Related

Sources

Vault:

Web (all accessed 2026-09-15):