Hydrogen development services
Hydrogen is Shopify’s React framework for headless storefronts. It gives you full control of the frontend while Shopify keeps running checkout — which is the right trade only when a theme genuinely cannot do the job.
Where we use Hydrogen
Hydrogen is part of the stack on this service. Each page covers how we work, what you get and what it costs to start.
Hydrogen in practice
Hydrogen is Shopify’s React framework for headless storefronts, deployed on their Oxygen edge hosting. You get complete control of the frontend while Shopify continues to run checkout, payments and orders — so you gain the freedom without inheriting the compliance burden.
The question is almost never whether Hydrogen can do something. It is whether the experience you want genuinely cannot be built in a Liquid theme, because a React application is meaningfully more expensive to maintain than a theme is. When the answer is a real product requirement, Hydrogen is the right tool. When it is a preference for React, a theme usually serves the business better.
What we build with Hydrogen
React storefronts on Hydrogen and Oxygen, with Shopify still handling checkout, payments and orders.
Stores where editorial content and the catalogue are equally important and a theme becomes the limiting factor.
Configurators, personalisation and interactions that need real application logic in the storefront.
Is Hydrogen right for you?
Ask usA good fit when
- Storefronts needing genuine application behaviour — configurators, personalisation
- Content-rich commerce where editorial and catalogue are equally important
- Brands with a frontend team already maintaining React
- Experiences spanning more than the storefront
Probably not when
- Standard stores — a theme is cheaper to build and to change
- Merchants without an ongoing development relationship
- Teams where marketing must be able to change everything themselves
What we run alongside Hydrogen
The rest of the setup, and why each piece is there. We keep this list short on purpose — every dependency is something someone has to maintain.
- Oxygen
- Shopify’s edge hosting — deployed globally with no infrastructure of yours to run.
- Storefront API
- The data layer: products, collections, cart, localisation.
- Customer Account API
- Login, orders and account management on a headless storefront.
- Metaobjects or a headless CMS
- So editors are not locked out of a headless build.
- Tailwind CSS
- One styling vocabulary across marketing sections and application screens.
Why Hydrogen
Let’s talkReact with commerce built in
Cart, product and localisation primitives are provided, so you are not rebuilding commerce fundamentals.
Hosted on Oxygen
Shopify’s own edge hosting, deployed globally with no infrastructure for you to operate.
Checkout stays Shopify’s
You gain frontend freedom without inheriting responsibility for payments and compliance.
What we get called in to fix
Get a second opinionEditors locked out
Headless builds where every content change needs a deployment, because nothing was mapped to editable content.
Slow product pages
Sequential API calls that should have been a single query, or should have been cached.
Cart logic reimplemented client-side
Pricing and discounts recalculated in the browser and disagreeing with checkout.
Abandoned headless builds
Storefronts nobody can maintain after the original team left — the most common failure, and an argument for choosing a theme.
Hydrogen or the alternative
The comparisons we are actually asked to make, answered the way we would answer them on a call.
Theme for most stores. Hydrogen when the storefront genuinely needs to behave like an application, and you have someone to maintain it.
Hydrogen for the supported path and Oxygen hosting. Next.js when the storefront is part of a larger site you already operate.
A hybrid — theme for the store, custom pages where needed — often gets most of the benefit for a fraction of the maintenance.
Hydrogen works well with:
GraphQL
JavaScript
Node.js
React
Shopify
TypeScriptGot an idea? Let’s make it real.
Tell us the short version
This could be the first step towards a new and successful collaboration. A one-line idea and a finished spec are both fine — tell us the problem, the deadline you’re working to and what’s in your way.
Keep looking
Frequently asked questions
A theme for most stores — cheaper to build and to change. Hydrogen when the storefront needs behaviour a theme genuinely cannot deliver.
Yes. It is a React application, so it carries the maintenance profile of one. That cost has to be justified by the experience.
Only if it is built for that — usually with metaobjects or a headless CMS. It is a design decision, not a default.
A frontend application to maintain: dependencies, deployments, hosting and someone who understands it. That ongoing cost is the main reason not to do it without a clear requirement.
Yes, and it is often the sensible answer — custom pages where they earn it, the theme everywhere else.