Hydrogen is being rebuilt as a framework-agnostic commerce SDK

On 17 June 2026, alongside the Spring '26 developer announcements, Shopify described the next version of Hydrogen in a sentence worth reading twice: it moves the commerce logic out of React Router into a framework-agnostic core.

Hydrogen has been a React framework since it existed. It was a React framework when it was its own runtime, and it stayed a React framework when it became a Remix stack and then a React Router one. The developer preview stops being one.

What is in the preview

The preview supports React Router, Next.js, SvelteKit, Nuxt, SolidStart and Astro, and on 30 July 2026 it added Vue bindings as @shopify/hydrogen/vue — an officially supported non-React binding. You install it with npx @shopify/hydrogen@preview setup.

The reframing is from "a way to build a Shopify storefront" to "the commerce parts, usable from the framework you already chose". Cart state, customer sessions, the Storefront API client, analytics, consent — the things that are genuinely hard and genuinely Shopify-specific — separated from the routing and rendering layer, which was never the interesting part and was always somebody else's opinion.

No general availability date has been stated. This is a preview with the behaviour disclaimers a preview carries, and nothing on an official page commits to a date. Treat any blog post that gives you one as unsourced.

The other three moves point the same way

On 30 June 2026 Hydrogen gained one-click deployment to Vercel — a one-click path to a host other than Oxygen, which Shopify's own self-hosting docs have long allowed. On 3 August 2026 Oxygen became available on development stores, which had previously required a paid plan; development stores have no public environments, so deploy URLs need a store login, but the practical effect is that a headless build can be demonstrated before a store starts billing.

And the release cadence itself is a signal. Hydrogen shipped stable versions in February and April 2026, and the April release carried real breaking changes — proxyStandardRoutes removed, the Storefront API proxy always enabled, backend consent mode on by default in place of the client-side tracking cookie. The July quarterly stable did not arrive.

What to do with this

If you run a Hydrogen storefront today: nothing is being taken away, but check two things. Whether you are on the 2026.4 line and have absorbed its breaking changes, and whether you completed the shopify_y / shopify_s tracking cookie migration — the Hydrogen deadline for that was 30 April 2026, and storefronts that missed it have unreliable visitor and session attribution.

If you are choosing an approach now: this is an argument for keeping commerce logic in one layer and framework code in another, whichever framework you pick. That separation is the direction Shopify is building toward, and a storefront written that way is portable into the new model regardless of what the new model finally looks like.

If you were waiting for a reason to consider headless with a non-React team: that reason now exists, in preview. It is not a reason to commit a production storefront to a preview.

The honest summary

Hydrogen has meant React since it existed, and a lot of architectural decisions were made because of that constraint rather than because of the store. The constraint is being removed. What replaces it is not finished, has no date, and should be read as a direction rather than a plan.

Directions are still worth reading. This one says the boundary Shopify considers durable is the commerce layer, not the framework.

Where this lands in practice is Next.js and React work today, and API work in every version of it.