Hydrogen and Oxygen vs. Other Headless Commerce Vendors?
Hydrogen and Oxygen are a BUILD for a Plus merchant staying on Shopify, and free hosting is not the reason. Shopify lists Oxygen at no extra charge on every paid plan from Starter to Plus, so hosting is not a Plus benefit. The Plus case is the 1000 points/second Admin API ceiling, Plus-only checkout extensions and up to 25 Hydrogen storefronts. Replatform only when the commerce backend is the constraint.
Your profile — see how the verdict shifts
- Confidence
- High — Shopify's Hydrogen fundamentals page, re-read on 2026-09-05, lists Oxygen at no extra charge on paid Shopify plans: Starter, Basic, Grow, Advanced, Plus and Pause and build. Oxygen is therefore not a Plus entitlement, and any pitch that prices it as one is wrong. Searching the App Store for bigcommerce, commercetools, netlify, vercel, salesforce-commerce and adobe-commerce found no competing headless vendor a Shopify merchant can install: the listings that carry those names are migration and import tools for merchants moving to Shopify, and Vercel and Netlify have no listing at all, which is expected of hosting platforms. The real alternative is a self-hosted framework against the Storefront API, or leaving Shopify's commerce backend entirely. The Plus-specific arguments verified the same day are the 1000 points/second Admin API calculated-query ceiling against 100 on standard plans and 200 on Advanced, checkout UI extensions on the information, shipping and payment steps being Plus-only, and the Plus plan page's allowance of up to 25 custom React storefronts built with Hydrogen.
- Reference scenario
- $20M–$100M GMV · Shopify Plus · one brand rebuilding a Liquid storefront in React · agency or in-house React bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| No React bench | WAIT | A Hydrogen storefront is a React runtime someone has to staff every week. Without that bench, a Liquid theme is the cheaper and more honest answer, whoever hosts it. |
| React bench, one Shopify storefront | BUILD | Hydrogen on Oxygen is the shortest path: Shopify maintains the runtime, hosting is included on every paid plan, and the deploy flow ships through the Hydrogen sales channel. |
| Existing Next.js platform and design system | DEPENDS | Moving a working pipeline onto Oxygen buys you free hosting and costs you your middleware, previews and CI conventions. Price that migration against a year of the hosting it replaces. |
| Several commerce backends in one storefront | DEPENDS | Hydrogen is built around Shopify's Storefront API. When Shopify is one source among a PIM, a marketplace feed and a subscription backend, a framework you own composes them more cleanly. |
What Hydrogen vs. Competing Headless Vendors Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Customer experience | High | A React storefront rendered at the edge removes the theme-era script waterfall, so product and collection pages paint sooner for shoppers on slow connections. |
| Operational efficiency | High | Oxygen removes the hosting workstream entirely: no CDN contract to negotiate, no edge runtime to patch, and deploys ship through the Hydrogen channel. |
| Revenue — indirect | Medium | A faster, fully controlled storefront lifts conversion at the margins, while checkout stays Shopify's and performs identically in either lane. |
| Data & insight | Medium | A custom storefront exposes request-level telemetry a theme never surfaced, though the commerce records themselves stay in Shopify either way. |
| Revenue — direct | Low | The runtime choice moves no revenue on its own; merchandising, catalog quality and checkout do the work here. |
Spend ceiling: Hosting is the cheapest line in a headless rebuild, and it is the line vendors argue about. Size the budget to the front-end rebuild and to the app surfaces that stop working when the Liquid theme goes away. If a comparison turns on the hosting invoice, the comparison is measuring the wrong thing.
What buying enables (top apps)
- + Framework freedom: Next.js, Astro or SvelteKit against the Storefront API, using the component library and CI your team already runs
- + One storefront over several backends, composing Shopify with a PIM, a headless CMS and a search vendor behind an API layer you own
- + Host features Shopify does not ship, including per-branch preview environments wired to your pipeline and edge middleware you control
What building additionally unlocks
- + Hosting at no extra charge on every paid Shopify plan, which deletes a recurring infrastructure line from the storefront budget
- + Up to 25 custom React storefronts on Plus, so sub-brands and market storefronts share one commerce backend and one deploy channel
- + A runtime versioned against the same Storefront API releases your admin already follows, with no third-party SDK in between
- + Deploys, preview environments and storefront routing managed from inside Shopify, so one team owns commerce and front end together
Find Your Verdict in 3 Questions
Does the storefront need commerce data from a backend other than Shopify?
Yes: Your verdict: BUILD on your own framework and host — a composable stack earns its hosting bill when Shopify is one source among several.
No: Go to question 2.
Does your team already run a production Next.js or Remix platform with its own pipeline and middleware?
Yes: Go to question 3.
No: Your verdict: BUILD on Hydrogen and Oxygen — hosting is included on every paid plan and the starter is the shortest route to production.
Would porting that platform to Oxygen cost more than a year of the hosting it replaces?
Yes: Your verdict: BUILD on your existing stack — keep the pipeline and point it at the Storefront API.
No: Your verdict: BUILD on Hydrogen and Oxygen — the hosting line disappears and Shopify maintains the runtime.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | Hydrogen ships a starter, a CLI and a one-command deploy; a self-hosted stack adds infrastructure setup before the first page renders. | ||
| Recurring fees | Oxygen is listed at no extra charge on every paid Shopify plan; a self-hosted stack bills hosting, CDN and edge compute every month forever. | ||
| Maintenance & upgrades | Both lanes track Shopify's versioned Storefront API, and both absorb framework upgrades; Hydrogen's own foundations have moved more than once. | ||
| Switching & exit | Neither lane strands data, because commerce records stay in Shopify and the front end is your code either way. | ||
| Risk | |||
| Vendor risk | Oxygen concentrates the storefront on the vendor you already depend on; a third-party host spreads risk but adds a second roadmap you do not control. | ||
| Security & compliance surface | Oxygen sits inside the platform certified Level 1 PCI DSS and SOC2; a self-hosted edge runtime is a perimeter you configure, monitor and attest to. | ||
| Platform-deprecation exposure | Shopify versions the Storefront API on a published cadence, and Hydrogen's docs still name a Node.js floor of v16.20 that the wider ecosystem left behind. | ||
| Value | |||
| Fit to requirement | Hydrogen fits a Shopify-only storefront exactly; a framework you choose fits a storefront that also reads a PIM, a CMS and a search vendor. | ||
| Time to market | The Hydrogen starter plus the Hydrogen channel is the shortest documented route from an empty repository to a live storefront on Shopify. | ||
| Performance & scale | Oxygen runs at Shopify's edge and a top-tier host runs at its own; real parity, and page weight decides more than the runtime does. | ||
| Data ownership & AI-readiness | Both lanes read the same Storefront API; the difference is where request logs, cache keys and edge configuration live and who can query them. | ||
| Focus & opportunity cost | Oxygen deletes the infrastructure workstream, which is a whole quarter your team spends on merchandising instead of on a CDN contract. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Hydrogen and Oxygen | Native — First-party Shopify stack. Shopify's docs list Oxygen at no extra charge on paid Shopify plans: Starter, Basic, Grow, Advanced, Plus and Pause and build, so hosting is not a Plus entitlement. The Plus plan page separately allows up to 25 custom React storefronts built with Hydrogen. Current docs name a toolchain floor of Node.js v16.20+ and npm v8.19+, and deploys run through the Hydrogen sales channel (verified Sep 2026). | Hosting included at no extra charge on every paid Shopify plan (verified Sep 2026); the rebuild itself is a project cost | A Shopify-only storefront rebuilt in React, with no hosting contract to sign |
| Self-hosted framework on a third-party host | Live — Platform integration; no App Store listing. Next.js, Remix or Astro against Shopify's Storefront API, deployed to a host you contract with directly. Vercel and Netlify publish no Shopify App Store app, which is expected of hosting platforms rather than a red flag. What you gain is your existing pipeline, preview environments and edge middleware; what you pay for is the hosting Oxygen includes. | Billed by your host on its own plans; confirm the current rate card before you model it (Deploi estimate for the mid-market range: $500–$3,000 a month, illustrative) | Teams with a production React platform already running, or a storefront reading several backends |
| Competing headless commerce platforms | Live — Platform integration; no App Store listing. commercetools, BigCommerce, Salesforce Commerce Cloud and Adobe Commerce are commerce backends you move to, not apps you install alongside Shopify. Their App Store listings are migration and import tools running the other direction, toward Shopify. Choosing one is a replatform of the commerce backend, not a storefront decision. | Quote-based enterprise licensing; no public per-store price | Merchants whose constraint is Shopify's commerce model itself, not the storefront layer |
| Custom storefront on the Storefront API (build lane) | Build lane — The same React storefront either lane produces: routes, cart, search, merchandising and every surface a theme app extension used to render, written against Shopify's Storefront API. Hosting is the only variable between the two lanes, and it is the smallest line in the estimate. | $60,000–$180,000 one-time plus upkeep (Deploi estimate, illustrative) | Any merchant with the bench to run a React storefront in production |
The Build Path
- Hydrogen starter on Oxygen: Scaffold from Shopify's Hydrogen starter, install the Hydrogen sales channel, and deploy with the CLI. Shopify's current docs name Node.js v16.20+ and npm v8.19+ as the toolchain floor; run a modern LTS anyway and treat the published floor as a minimum, not a recommendation.
- Route parity and redirects before cutover: Shopify's migration guide is explicit: assign checkout.example.com to checkout, publish the same products to both the Online Store channel and the Hydrogen storefront so shared carts work, set redirects for every customized route, and update feed rules to the Hydrogen domain. Skipping the feed rules is how paid traffic lands on a dead URL.
- Rebuild the surfaces your theme was renting: Theme app extensions integrate with Online Store 2.0 themes. A Hydrogen storefront has no Liquid theme, so reviews, upsells and personalization widgets become React components against each vendor's API, or subscriptions you cancel. Inventory that list before the estimate, not during the build.
- Own framework on your own host: The alternative build: Next.js or Remix against the same Storefront API, deployed through the pipeline you already run. Identical commerce integration, identical rebuild scope, plus a hosting, CDN and edge-compute bill. Worth it when the pipeline and middleware are load-bearing for other properties.
- Effort band
- $60,000–$180,000 for a full storefront rebuild — Deploi estimate (illustrative); lands in the $75K+ contact-form band
- Typical timeline
- 3–6 months to a production cutover (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $9,000–$36,000/yr (Deploi estimate, illustrative) for Storefront API version bumps, framework upgrades and the app surfaces you now own. Oxygen hosting adds nothing to that line on any paid Shopify plan.
- What you own — and what you take on
- You own: the front end, routing, caching strategy, and every surface an app used to render into your theme. You take on: a React runtime to staff and Hydrogen's own framework churn, which has already moved foundations more than once.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $70,000–$200,000 | $60,000–$180,000 |
| Years 1–3 (recurring) | $45,000–$120,000 (hosting, CDN, edge and upkeep) | $27,000–$108,000 (upkeep only) |
| 3-year total | ≈$115,000–$320,000 | ≈$87,000–$288,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Left column is a self-hosted headless stack: the same storefront rebuild plus hosting, CDN and edge compute billed monthly by a third-party host.
- † Right column is Hydrogen on Oxygen: the same rebuild with hosting at no extra charge on every paid Shopify plan; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Hosting, CDN and edge-compute bills scale with traffic, and a drop day is exactly when they spike
- — Two version cadences to reconcile: your host's runtime and Shopify's Storefront API, each moving on its own schedule
- — Replatforming the commerce backend rather than the storefront is the version of this decision that costs a year, not a quarter
- — Enterprise headless platforms quote per contract, so the number you budget against is not public and not comparable
On the build path
- — Hydrogen's foundations have changed more than once, and each move is a real upgrade project on a working storefront
- — Shopify's Hydrogen docs still publish a Node.js v16.20+ floor, so treat the stated toolchain as a minimum you exceed deliberately
- — Every theme app extension your storefront rendered stops existing; each becomes a component you build or an app you cancel
- — ~$9,000–$36,000/yr upkeep (Deploi estimate, illustrative)
What Merchants Say
Teams describe the Oxygen pitch landing as a cost saving, then finding hosting was never the expensive part: the storefront rebuild and the app surfaces lost with the theme were.
The recurring complaint from dev leads is the upgrade tax, not the runtime: the framework's foundations moved, and a storefront that worked needed a migration sprint nobody had budgeted.
If You Change Your Mind Later
If you bought and outgrow it
Leaving a third-party host moves the deployment, not the product: Storefront API queries and React components port to Oxygen largely intact, and commerce data never left Shopify. What you stop paying is the hosting contract, and what you give up is the middleware you wrote for that platform.
If you built and want out
Leaving Oxygen is a redeploy rather than a rebuild, because a Hydrogen storefront is a React application reading the same Storefront API from any runtime. You give up the Hydrogen sales channel's deploy flow and Oxygen preview environments, and you pick up a hosting bill you did not have.
When This Answer Changes
We're watching for:
- ▸ Shopify changing Oxygen's inclusion, since today's docs list it at no extra charge on Starter, Basic, Grow, Advanced, Plus and Pause and build
- ▸ Another Hydrogen foundation change, which is the single largest maintenance risk in this lane
- ▸ Shopify moving the 25-storefront Plus allowance or the 1000 points/second Admin API ceiling, either of which changes the multi-storefront math
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Is Oxygen hosting a Shopify Plus benefit?
No. Shopify's Hydrogen documentation lists Oxygen at no extra charge on paid Shopify plans: Starter, Basic, Grow, Advanced, Plus and Pause and build. Hosting is therefore not a reason to choose Plus, and not a Plus-specific argument for Hydrogen. The Plus-specific arguments are the 1000 points/second Admin API ceiling, Plus-only checkout UI extensions, and up to 25 Hydrogen storefronts.
Can a Hydrogen storefront run somewhere other than Oxygen?
Yes. A Hydrogen storefront is a React application reading Shopify's Storefront API, and nothing in that contract requires Oxygen. Hosting elsewhere means paying roughly $500–$3,000 a month for hosting, CDN and edge compute (Deploi estimate, illustrative) that Oxygen includes. Teams still do it when an existing pipeline and edge middleware are worth more than the hosting line.
What does a Hydrogen rebuild actually cost?
A Hydrogen storefront rebuild costs $60,000–$180,000 one-time, plus roughly 15–20% of build cost per year in upkeep (Deploi estimate, illustrative), over 3–6 months. Oxygen hosting adds nothing to that number on any paid Shopify plan. The line most budgets miss is app replacement: every widget a theme app extension rendered becomes a React component you build or a subscription you cancel.
Your Next Steps
If you're going with BUILD(matches your selected profile)
- Inventory every app that renders through a theme app extension today, and mark each one rebuild, replace or cancel
- Install the Hydrogen sales channel and stand the starter up against a staging store before scoping anything
- Map route parity from the Liquid theme, including customized routes, and write the redirect table first
- Assign checkout.yourdomain.com to checkout and publish products to both the Online Store channel and the Hydrogen storefront
- Update paid-feed rules to the Hydrogen domain before cutover, not after the first click loss
If you're going with BUY
- Model twelve months of hosting, CDN and edge compute at your real traffic, then compare it to the migration cost of moving to Oxygen
- Confirm which team owns runtime patching and incident response on the host you choose
- Pin the Storefront API version explicitly and diary the upgrade, since nothing on your host will do it for you
- Keep the storefront code portable: no host-specific middleware in the commerce path
Official Docs & Sources
- Hydrogen fundamentals and Oxygen plan availability — shopify.dev
- Hydrogen — shopify.dev
- Headless commerce overview — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Cart Transform vs. a Bundle App: Who Owns Pricing?
Overriding a bundle line's price, title and image with Cart Transform's lineUpdate works only on development stores or Shopify Plus; bundle apps cover the rest.
Should You Run a Custom Cart Transform Alongside an App's?
Shopify caps cart transform functions at one per app rather than one per store, and runs every app's function, so a custom one can sit beside a bundle app's.
Branding API vs. the Free Checkout Editor: Do You Need Code?
The free checkout and accounts editor covers most branding on every plan; Plus API overrides add precision, and the Checkout Blocks branding editor ends 2026-12-31.
Checkout Extension Network Access: What Shopify Actually Allows
Checkout UI extensions declare four capabilities in the extension TOML file, and network_access is the one Shopify makes you request before publishing.
Should You Build or Buy Your Shopify Scripts-to-Functions Migration?
A Scripts-to-Functions migration is a build for any store whose checkout logic still earns money — unported rules have already gone silent.
Ready to price a headless rebuild honestly?
We scope Hydrogen migrations the way the money actually falls: the storefront rebuild, the app surfaces you lose with the theme, and the hosting line that turns out to be the smallest number on the page.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.