Cortex Training Entered Public Preview on 2026-10-30, Open Stage, AWS Only, No Named Regions and No Documented Edition Gate
The question
"Has Snowflake Cortex Training actually entered public preview, and in which regions, clouds and editions, per its feature doc preview banner and release notes?"
Context: this closes the first open follow-up from [[2026-09-14-snowflake-cowork-cortex-ga-vs-preview-matrix]], which could not find any Snowflake release note for Cortex Training and could not confirm region, cloud or edition caveats inside its research caps. The founder needs a ledger he can cite verbatim in a client conversation without being wrong.
Headline: Yes. Cortex Training entered public preview on 2026-10-30 per its own dated Snowflake release note, at the Open preview stage, and the feature doc banner reads "Available in all commercial Amazon Web Services (AWS) regions. Requires enablement." The docs name no individual regions, state no Snowflake edition requirement, and say nothing about cross-region inference. Two primary-source inconsistencies are worth knowing before quoting any of it: the "Open" badge contradicts the same page's "contact your account team to enable" instruction, and Cortex Training does not appear at all in Snowflake's central "Features currently in preview" table.
What we already know (from the vault)
- The parent brief closed 2026-09-14 with Cortex Training marked "Unconfirmed: public preview claimed by third parties, not confirmed by Snowflake", with no release note found and region/edition caveats explicitly unresolved. [[2026-09-14-snowflake-cowork-cortex-ga-vs-preview-matrix]]
- The Pupius four-axis audit recorded Cortex Training as announced at Summit 2026 "without a GA date", and read it as Snowflake's bet that general models stay insufficient on enterprise data. [[2026-09-12-pupius-four-axis-snowflake-data-ai-strategy]]
- The product-boundary brief flagged Cortex Training (with Cortex Sense) as the piece blurring the clean two-layer Snowflake Intelligence / Cortex AI picture, and listed this exact GA-vs-preview question as its own open follow-up. [[2026-07-07-snowflake-intelligence-vs-cortex-ai-boundary]]
- Snowflake already had a generally available fine-tuning surface before any of this: the SQL
SNOWFLAKE.CORTEX.FINETUNEfunction with CREATE / DESCRIBE / SHOW / CANCEL modes, captured in the SnowPro Gen AI study notes. Cortex Training is a different product with a different interface, not a rename. [[study-cortex-ai]] - Cortex feature statuses in this family have repeatedly turned out to be region-scoped and cross-region-inference-dependent, which is why the CoCo surface brief tracked cross-region inference as a first-class caveat. [[2026-09-13-cortex-code-client-deployable-surface-p3-p4]]
What the web says
All statuses below were observed 2026-11-05 on docs.snowflake.com. The feature doc and the get-started page were read as raw page text (Playwright), so the quoted banner wording is literal, not a fetch summary.
- The release note exists and is dated. "Oct 30, 2026: Cortex Training (Preview)" is listed on the current Snowflake feature-updates page and has its own note page. Body: "Cortex Training is now available in preview," a serverless service for customizing open-weight large language models, where the customer runs the training loop from their own workspace and Snowflake runs the GPU work. The note states: "This feature is available only in commercial Amazon Web Services (AWS) regions and requires enablement," and to enable it, "contact your account team." (release note; current feature updates, covering ~2026-09-24 to 2026-11-04)
- The feature doc banner, verbatim. The Cortex Training overview page carries a badge reading
PREVIEW FEATURE — OPENfollowed by: "Available in all commercial Amazon Web Services (AWS) regions. Requires enablement." A separate note on the same page reads: "Cortex Training is in preview. Model availability, APIs, and specifications on these pages are subject to change before general availability." (Cortex Training) - No named regions, no edition requirement, no privileges list. Searching the overview and get-started pages for "edition", "Enterprise", "Standard", "cross-region" and "privilege" returns zero hits. The get-started prerequisites are only: "A Snowflake account on Amazon Web Services (AWS) with Cortex Training enabled. To enable Cortex Training, contact your account team," a programmatic access token (PAT) for authentication, and Python 3.10 or later. (Get started with Cortex Training)
- Cortex Training is absent from the Cortex AI regional-availability matrix. The "Model availability for Snowflake Cortex AI" page is the per-cloud, per-named-region table, and its product columns are AI Functions, Cortex Inference, Cortex Agents / CoWork, Agent Evaluations, CoCo and Cortex Search. There is no Cortex Training column, and no Cortex Training row anywhere on the page. The named-region grids there (AWS US West 2 Oregon, AWS US East 1 N. Virginia, Azure East US 2 Virginia, and so on) therefore say nothing about Cortex Training. (Model availability)
- Cortex Training is also absent from the central preview-features table. The "Features currently in preview" table on the Preview features page contains rows dated as recently as November 2026 and zero occurrences of the string "Training". That page defines the three availability stages: Open means "enabled by default for all accounts"; On Request means "you must contact Snowflake"; Closed means invitation-only. It also states, generically, "Some preview features are available only in certain Snowflake editions or in specific cloud platforms or regions." (Preview features)
- Preview terms matter more than the badge. The same page carries: "Preview features are provided primarily for evaluation and testing purposes. They should not be used in production systems or with production data," and points to the Snowflake Preview Terms of Service.
- Shape of the product, for scoping conversations. Supervised fine-tuning (SFT) and reinforcement learning (RL), LoRA or full-parameter, driven from a client-side Python namespace
cortex_trainingplus acortex-trainingCLI installed fromgithub.com/snowflakedb/cortex-training, authenticated with a PAT. Checkpoints can be saved, resumed, and deployed to an OpenAI-compatible streaming endpoint. Framework integrations named are VeRL, SkyRL, Prime-RL and Unsloth, "at different stages of upstream acceptance," with current status available only from the account team. Billing is AI Credits for on-demand GPU, "metered per second, with no minimum"; reserved GPU capacity is an account-team conversation. (Cortex Training) - Separate product, separate region story. Snowflake's older Cortex Fine-tuning went generally available 2025-02-07, and a 2026-10-20 release note titled "Cortex Fine-tuning: New model training no longer available in AWS US East 1" shows that surface narrowing. That is a different service from Cortex Training; do not transfer its region list. (Release-note titles observed at search-result level only, not fetched: GA note; AWS US East 1 note)
The verified ledger (the five questions, each answered or explicitly unresolved)
| # | Question | Answer as of 2026-11-05 | Evidence | Confidence |
|---|---|---|---|---|
| 1 | Public preview, private preview, GA, or not released? | Public preview. Release-note label "(Preview)"; feature-doc badge PREVIEW FEATURE — OPEN. Not GA: the doc explicitly says specifications are "subject to change before general availability". Not private preview: it has a public release note and a public feature doc. |
Release note 2026-10-30; Cortex Training overview page | High |
| 2 | As of what date, per which release note? | 2026-10-30, per the release note "Oct 30, 2026: Cortex Training (Preview)" at /en/release-notes/2026/other/2026-10-30-cortex-training-preview. |
Same, plus the current feature-updates index | High |
| 3 | Which clouds, which named regions? | AWS only. Verbatim: "Available in all commercial Amazon Web Services (AWS) regions." No Azure, no Google Cloud. No individual region is named anywhere - not on the feature doc, not on the get-started page, and not on the Cortex AI model-availability matrix, where Cortex Training is not a column. Whether "commercial" excludes AWS US Commercial Gov, FedRAMP High Plus and DoD regions is not stated on these pages. | Feature doc banner; release note; model-availability page (absence) | High on "AWS only"; the per-region list is a documented absence, not a finding |
| 4 | Which editions? Any Enterprise-or-above gate? | The docs do not state this. No edition requirement appears on the Cortex Training overview or get-started pages. The only account-side prerequisites documented are an AWS-hosted Snowflake account, enablement by the account team, and a PAT. Not evidence that Standard Edition works - evidence that Snowflake has not published a gate. | Overview + get-started pages (keyword sweep returned zero hits for edition/Enterprise/Standard) | High that the docs are silent; unresolved on the actual entitlement |
| 5 | Any cross-region inference requirement? | The docs do not state this. Neither page mentions cross-region inference or CORTEX_ENABLED_CROSS_REGION. Cortex Training is also absent from the cross-region scope columns on the model-availability page, which cover AI Functions, Cortex Inference, Cortex Agents / CoWork, Agent Evaluations, CoCo and Cortex Search. Plausibly moot, since training runs in-region on AWS rather than routing inference across regions, but that is inference and not documented. |
Overview + get-started pages; model-availability page | High that the docs are silent; the reason is unverified |
Convergences and contradictions
- The parent brief's skepticism was correct, and the third parties were about five months early. Atlan called Cortex Training "public preview as of June 2026"; Snowflake's own release note puts preview at 2026-10-30. A conference announcement plus a vendor explainer was not evidence of preview status, exactly as the parent brief argued. The rule survives intact: the dated release note is the evidence.
- Primary-source contradiction inside Snowflake's own docs. The badge says Open, which Snowflake defines on its Preview features page as "enabled by default for all accounts." The same banner and the get-started prerequisites say the feature "Requires enablement" and that you must "contact your account team." That is Snowflake's definition of On Request, not Open. Behaviourally, treat Cortex Training as On Request: assume a client account cannot use it until the Snowflake account team switches it on.
- Second contradiction: it is not on the preview index. Cortex Training has a release note and a feature doc, but no row in the "Features currently in preview" table, which otherwise carries November 2026 entries. Either the index lags, or Cortex Training is being tracked outside the normal preview lifecycle. Either way, "it is not in the preview table" is not a safe argument in either direction, and the feature doc banner is the stronger citation.
- Convergence with the parent brief's contract rule. Nothing found today changes the parent's conclusion that Cortex Training is not a deliverable. Preview status is now confirmed rather than rumoured, and Snowflake's preview terms still say in writing that preview features "should not be used in production systems or with production data."
Synthesis for RDCO
The one-line version the founder can say out loud: "Cortex Training went to public preview on October 30, 2026, AWS commercial regions only, and it needs Snowflake to switch it on for your account." That sentence is fully backed by two primary sources with a date, which is the standard the parent brief set for anything said in a client conversation. Everything beyond it - which specific regions, which edition, whether cross-region inference matters - should be said as "Snowflake has not published that," not guessed. The negative findings are the valuable half of this brief, because they are the sentences a Deal Solutions Architect (DSA) would otherwise improvise under pressure. A client on Azure or Google Cloud is a hard no today, and that is the single most useful disqualifier here: it removes Cortex Training from scope for a large share of accounts with one documented line rather than a procurement cycle.
For a Statement of Work (SOW), the "Requires enablement" clause is the load-bearing risk, not the preview label. A preview dependency is a known pattern and can be papered over with a preview-dependency clause. An account-team enablement gate is different: it puts a Snowflake-internal approval on the critical path of a phData deliverable, with no published eligibility criteria, no stated turnaround, and no self-service path. Any pencilled Cortex Training scope needs enablement confirmed in writing on the client's account before the scope is signed, not after. The practical sequencing is: client asks their Snowflake account team to enable Cortex Training, enablement is confirmed, then phData scopes. Reversing that order is how a fine-tuning workstream stalls on something phData cannot escalate.
The architecture is a real differentiator worth understanding, even though it is not sellable yet. Cortex Training's split - client-side training loop on a laptop or CPU-only virtual machine, server-side GPU work on Snowflake, with weights never downloaded - is a genuinely different shape from both Cortex Fine-tuning (a SQL function, generally available, narrowing in region coverage) and from bring-your-own-GPU training in Snowpark Container Services (SPCS). It targets teams who already have a training script and want governed GPUs without moving data, which is a credible wedge for the "agents in production" positioning and a better conversation than a feature-availability debate. The per-second AI Credits metering with no minimum also makes a sandbox experiment genuinely cheap to propose. That argues for a hands-on experiment in an internal or sandbox account once enablement is available, specifically to have a first-hand answer about the edition and enablement questions the docs refuse to answer.
Correction discipline on the vault. The parent matrix row for Cortex Training now reads as stale rather than wrong: it said "unconfirmed public preview" on 2026-09-14 and that was accurate then. This brief supersedes that single row as of 2026-11-05, and should be the row cited going forward. The rest of the parent matrix is untouched and still the reference for the CoWork and Cortex Sense items.
Why this is in the vault
It closes the first open follow-up of [[2026-09-14-snowflake-cowork-cortex-ga-vs-preview-matrix]] with a primary-source, date-stamped answer, so the founder's phData DSA work can name Cortex Training's status, cloud restriction and enablement gate in a client conversation or SOW review without reaching for a third-party explainer. It also records two documented silences (edition, cross-region inference) so nobody fills them in by inference later.
Open follow-ups
- Does Cortex Training's "commercial AWS regions" phrasing include AWS US Commercial Gov, FedRAMP High Plus and DoD regions, or exclude them the way CoCo's "commercial accounts only" restriction does? The Cortex Training pages do not define "commercial".
- What is the actual Snowflake edition entitlement for Cortex Training? The docs publish none; the answer probably exists only in a Snowflake Service Consumption Table footnote or an account-team answer.
- What are the published eligibility criteria and turnaround for account-team enablement of Cortex Training, and can a partner such as phData request it on a client's behalf? This is the same unanswered question shape as Cortex Sense private-preview enrollment.
- Why is Cortex Training absent from the "Features currently in preview" table while carrying an Open badge on its feature doc? If the index is authoritative, the Open badge may be a documentation error; worth re-checking in a few weeks.
- Which base models does Cortex Training support, and at what sizes? The Models sub-page (
/user-guide/snowflake-cortex/cortex-training/models) was not read in this brief; the only model seen wasQwen/Qwen3-8Bin a get-started example. - Is Cortex Fine-tuning (generally available since 2025-02-07) being deprecated in favour of Cortex Training? The 2026-10-20 withdrawal of new model training in AWS US East 1 is a possible early signal and was only observed at release-note-title level.
Related
- [[2026-09-14-snowflake-cowork-cortex-ga-vs-preview-matrix]]
- [[2026-09-12-pupius-four-axis-snowflake-data-ai-strategy]]
- [[2026-07-07-snowflake-intelligence-vs-cortex-ai-boundary]]
- [[2026-09-13-cortex-code-client-deployable-surface-p3-p4]]
- [[2026-10-02-snowflake-semantic-views-cortex-gateway-agent-identity-audit]]
- [[study-cortex-ai]]
Sources
Vault:
- 06-reference/research/2026-09-14-snowflake-cowork-cortex-ga-vs-preview-matrix.md (parent brief, read in full)
- 06-reference/research/2026-09-12-pupius-four-axis-snowflake-data-ai-strategy.md (Cortex Training "announced without a GA date")
- 06-reference/research/2026-07-07-snowflake-intelligence-vs-cortex-ai-boundary.md (origin of the GA-vs-preview question)
- 06-reference/research/2026-09-13-cortex-code-client-deployable-surface-p3-p4.md (cross-region inference and commercial-accounts-only precedent)
- 06-reference/research/2026-10-02-snowflake-semantic-views-cortex-gateway-agent-identity-audit.md (prior Cortex preview-vs-GA audit pattern)
- 01-projects/certifications/snowpro-genai-c02/study-cortex-ai.md (the pre-existing generally available
SNOWFLAKE.CORTEX.FINETUNEsurface)
Web (all observed 2026-11-05):
- Snowflake Documentation, "Cortex Training" feature doc (read as raw page text via Playwright; source of the verbatim
PREVIEW FEATURE — OPENbanner): https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-training - Snowflake Documentation, "Get started with Cortex Training" (raw page text via Playwright; prerequisites list): https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-training/get-started
- Snowflake Documentation, release note "Oct 30, 2026: Cortex Training (Preview)" (fetched): https://docs.snowflake.com/en/release-notes/2026/other/2026-10-30-cortex-training-preview
- Snowflake Documentation, "Snowflake server release notes and feature updates" (fetched; confirms the entry and its date on the live index): https://docs.snowflake.com/en/release-notes/new-features
- Snowflake Documentation, "Preview features" (raw page text via Playwright; Open / On Request / Closed definitions, preview terms language, and the confirmed absence of any "Training" row): https://docs.snowflake.com/en/release-notes/preview-features
- Snowflake Documentation, "Model availability for Snowflake Cortex AI" (raw page text via Playwright; table columns enumerated, Cortex Training confirmed absent): https://docs.snowflake.com/en/user-guide/snowflake-cortex/model-availability
- Snowflake Documentation, "Feb 07, 2025: Snowflake Cortex Fine-tuning (General availability)" (search-result title only, not fetched): https://docs.snowflake.com/en/release-notes/2025/other/2025-02-07-cortex-finetuning
- Snowflake Documentation, "Oct 20, 2026: Cortex Fine-tuning: New model training no longer available in AWS US East 1" (search-result title only, not fetched): https://docs.snowflake.com/en/release-notes/2026/other/2026-10-20-cortex-finetuning-aws-us-east-1
No paywalled sources were encountered. Method notes: WebFetch summarised the release-note body under a quote-length limit, so the release-note wording above is a close paraphrase with short exact quotes; the feature doc, get-started, preview-features and model-availability pages were read as raw page text, so quotes from those four are literal. "The docs do not state this" means the keyword sweep over those raw page texts returned no hits on 2026-11-05; it is not proof that no Snowflake document anywhere states it.