Shopify and Vercel are rebuilding Hydrogen as an open, runtime-agnostic foundation. Hydrogen now dep…
Hydrogen Goes Runtime-Agnostic: What That Actually Solves
Shopify and Vercel are rebuilding Hydrogen as an open, runtime-agnostic foundation. Hydrogen now deploys straight to Vercel, it is open source, and it works across frameworks: Svelte, Nuxt, Next.js, or your own setup. That is a real improvement, and it clears exactly the criticism that has followed Hydrogen since launch. What it does not clear is the layer one level up: the frontend layer you still rebuild for every storefront.
What was actually announced
The core points from Vercel's briefing on the rebuild:
- Hydrogen is runtime-agnostic. Oxygen is no longer the only path to production. Deploying to Vercel is a first-class option.
- Hydrogen is framework-open. React-only is no longer a built-in assumption. It is a commerce foundation that different frameworks can sit on top of.
- Open source as the base. Developers and agents get a shared foundation instead of rewriting the commerce layer for every storefront.
- Agents are part of the design. The rebuild explicitly accounts for the fact that humans are no longer the only ones building storefronts.
For Shopify teams that used to pick between a Liquid theme and a custom build with no way back, this is a serious third option. Anyone who has looked at the cost side of that choice will see it quickly: we ran the numbers in Shopify Frontend Cost: Theme vs. Headless, and the rebuild moves exactly one line item in that math, the runtime commitment.
Why this is genuine progress
For two years we have heard the same sentence in discovery calls: "With Hydrogen we're glued to Shopify. If we ever want to switch, we start from zero." The rebuild takes half the sting out of that sentence. The runtime is no longer part of the deal. A team starting on Hydrogen today is not automatically locked to a single hosting layer tomorrow.
That Shopify is doing this openly and as open source, rather than keeping the runtime as a retention mechanism, is the right call. We mean that without irony: this is the move the market needed, and it came from the market leader.
What the rebuild does not solve
Runtime-agnostic is not the same as backend-agnostic. And neither one is frontend management yet.
1. The backend is still fixed. Hydrogen is Shopify commerce logic. If your B2B business runs on an ERP-adjacent system, your DACH brand on Shopware, and your marketplace on something else again, a runtime-free Shopify frontend helps you with exactly one of those. The question of one frontend across several backends stays open.
2. The frontend layer still gets built per storefront. An open-source foundation takes the commerce layer off your plate, not the storefront on top of it. Navigation, campaign pages, editorial workflow, locale handling, design-token discipline across several brands: all of that is built again in every project. In our projects, that is the part that eats the weeks, not the Storefront API call.
3. Editorial and marketing are not addressed. The rebuild is a developer and agent story. It says nothing about how a content manager ships a campaign page on Thursday evening without filing a ticket. Treat the frontend layer as a code artifact and that work lives in the engineering backlog permanently.
4. More choice means more decisions. Svelte, Nuxt, Next.js, your own framework, Vercel or elsewhere: each of those axes is now your decision and your maintenance. For a team with platform capacity, that is a win. For a team of three, it is work nobody put on the plan.
Where Laioutr comes in
Laioutr is a Frontend Management Platform (FMP): a control layer for the commerce frontend that sits above the backend instead of being part of it. Concretely, against the four points above:
Backend-agnostic as architecture, not as a promise. Our orchestration layer talks to more than 50 backends, Shopify included. You keep Shopify as the commerce engine and get the same storefront layer that also runs on Shopware or commercetools. The technical shape of that is on Composability and Orchestration.
The frontend layer as a product, not a project. Sections, blocks, component library, and deployment come as a platform, not as a repository template. The second storefront does not start from zero. For multi-brand and multi-market setups, that is the difference between weeks and quarters: Multi-Brand and Multi-Market.
Editorial without a developer ticket. Campaign pages, landing pages, and content changes happen in Studio, with preview and approval. Engineering reviews and extends, but is not the bottleneck: Content Management.
Consistency and performance as platform properties. Design tokens and themes apply across every storefront instead of drifting per repository (Brand Consistency), and Core Web Vitals are a measured part of the platform rather than the result of an optimization round at the end of a project (Performance and Core Web Vitals).
If you want to weigh "Hydrogen or frontend layer" concretely for your team, we wrote that up before the rebuild in Hydrogen vs. Laioutr: Which Frontend for Which Team?. The runtime row in it is now outdated by the announcement. The team and operations rows are not.
What you gain
- Runtime. Hydrogen after the rebuild: your choice, Vercel as a first-class path. With Laioutr as the frontend layer: your choice, EU hosting included.
- Backend. Hydrogen after the rebuild: Shopify. With Laioutr as the frontend layer: 50+ backends, Shopify included, replaceable.
- Second storefront. Hydrogen after the rebuild: a new project on a shared foundation. With Laioutr as the frontend layer: configuration on an existing platform.
- Campaign page. Hydrogen after the rebuild: pull request. With Laioutr as the frontend layer: Studio, with preview and approval.
- Operating model. Hydrogen after the rebuild: your team runs the layer. With Laioutr as the frontend layer: a platform, with updates and support.
FAQ
Is Laioutr an alternative to Hydrogen or a complement? An alternative at the frontend-layer level. You keep using the Shopify Storefront API as your data source, but you do not build the storefront as a separate Hydrogen project. Details on Headless Frontend for Shopify.
We already have a Hydrogen storefront. Was that wasted? No. Data model, Storefront API access, and content structure stay usable. The switch affects the presentation and control layer, not the commerce integration.
What does it cost? Pricing and tiers are on the Laioutr pricing page. For a comparison against a custom build, the cost breakdown in the theme-vs-headless post linked above is a better basis than a list price.
How long does it take? Median under 14 days for a first storefront with founder support. With several brands or markets it depends on your data, not on the frontend.
Does Shopify stay our backend? Yes, as long as you want it to. That is the whole point: the decision stays reversible without rebuilding the frontend.
Next steps
If your team is weighing whether the Hydrogen rebuild is the trigger for a rebuild of your own, book a 30-minute demo on Headless Frontend for Shopify. We will walk your stack with you, and we will tell you when Hydrogen is the right call for your case.
More from the Laioutr Platform
About the author: Marcel Thiesies is Co-Founder of Laioutr. He works with DACH teams every day on the question of which part of the commerce stack really needs replacing and which part just needs better control.