06-reference/research

snowflake cortex ai gateway cloud availability ga

2026-11-14·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)

Snowflake never published targets for the Cortex AI Gateway, and it shipped anyway: Azure and GCP on 2026-10-16, core GA on 2026-11-03

The question

"Does Snowflake publish a target for Cortex AI Gateway availability on Azure and GCP, and a GA target for the gateway itself?"

Context: the 2026-10-02 brief found the gateway was the one non-GA pillar of the pinned essay "Agents don't need your data warehouse": open preview since 2026-09-15, AWS commercial regions only. This re-check asks whether that has a published trajectory, so the draft can hedge or cite it.

Headline: Both halves of the question have been overtaken by events. No forward-looking target was located for either milestone, and none is needed now. Snowflake shipped both without pre-announcing them: a release note dated 2026-10-16 extends the gateway to Azure and GCP commercial regions (plus AWS New Zealand), and a release note dated 2026-11-03 makes the gateway's inference, observability, and cost management generally available. "Tools for Cortex AI Gateway" and the new trace analytics stay in preview. The draft's gateway hedge is now stale in the other direction.

What we already know (from the vault)

What the web says

Watch items (one line each; search-result level, BCR pages not fetched, verify before citing):

Convergences and contradictions

Synthesis for RDCO

The draft's gateway sentence should flip from hedge to assertion, with one scoped caveat. As of 2026-11-14 the defensible line is: Cortex AI Gateway's endpoint, tracing, and cost controls went generally available on November 3, 2026, after reaching Azure and Google Cloud commercial regions on October 16; tool-calling through the gateway and trace analytics are still in preview. That restores the essay to three GA pillars instead of two-plus-a-hedge, and it removes the Azure/GCP-reader problem that motivated this question. The option "drop it until general availability" in essay v1's open items is now resolved: keep it, cite the 2026-11-03 note. The SnowPro post's "AI Gateway ... are previews" line needs the same fix.

Fix the entitlement wording in the same edit. "One place to grant model access" should become something like "one governed endpoint that every AI client reaches models through, with a trace and a spend line for each request." Model access is granted by model RBAC, which, per the watch item above, is becoming the only access mechanism as CORTEX_MODELS_ALLOWLIST retires. That is a stronger story for the essay anyway: grants decide who may use which model, the gateway records what they did with it, and ACCESS_HISTORY.agents_info records what data the agent touched.

Do not cite a per-cloud GA statement, because none exists. The honest framing is "generally available" with a pointer to the release note, not "GA on all three clouds." If an Azure- or GCP-heavy reader pushes back, the two release notes together are the answer, and the gap (no explicit government/China region statement) is small enough not to belong in a buyer-facing essay. For phData client work it does belong in a pre-engagement check.

Pattern for the research engine: Snowflake does not publish availability or GA targets; it publishes release notes. Questions shaped "is there a published target for X" will keep returning null. The cheaper standing move is to re-check the release-notes index for a named feature right before any draft citing it publishes, which is what turned this from a hedge into a citation.

Why this is in the vault

It decides one sentence in the founder-pinned essay [[2026-10-02-agents-need-your-definitions-v1]] (item 4 of its open list: keep or drop the gateway) and one line in [[2026-10-02-post3-snowpro-genai-cortex-v1]], both feeding the Nov-30 credibility push, and it closes the follow-up left open in [[2026-10-02-snowflake-semantic-views-cortex-gateway-agent-identity-audit]].

Open follow-ups

Related

Sources

Vault:

Primary (fetched 2026-11-14):

Primary (search-result level only, not fetched; verify before citing):

Secondary (not fetched, lower rank):