See all services Shopify Plus Partner
API Developer

Deploy Hydrogen to Oxygen From Trial Plan Stores

Oxygen hosting no longer requires a paid plan. Trial stores can deploy Hydrogen storefronts, so headless evaluation can happen on the real runtime instead of a laptop. Deployment URLs stay login gated.

Executive summary

What changed

Deploying a Hydrogen storefront to Oxygen previously required the store to be on a paid plan. That requirement is gone. A store on a trial plan can now push a Hydrogen build to Oxygen and receive a working deployment URL.

One constraint carries over. Trial plan stores do not include public environments, so every deployment URL requires a store login. The deployment is real and runs on the same edge network, but it is not anonymously reachable.

Why it matters

The interesting part is sequencing, not cost. Most headless evaluations stall at the same point: the prototype runs locally, performance numbers come from a developer machine, and the business case is built on inference. Deploying to the actual runtime during evaluation replaces that inference with data. You can measure time to first byte on a real category template, watch how the edge cache behaves under repeat requests, and confirm that environment variables and secrets flow through the pipeline before anyone signs a contract. We covered the architectural trade offs in more depth in our note on Hydrogen and Oxygen in enterprise headless commerce.

The login requirement sets the boundary. A trial deployment is suitable for internal review, developer QA, and stakeholder demos where people have store access. It is not suitable for public beta, third party performance audits, or anything that needs an anonymous crawler to reach the page.

Role-specific impact

Use-case example

Real-world scenario

A wholesale distributor is deciding whether to replatform its 2,000 SKU catalogue onto Hydrogen or stay on a heavily customised theme. Previously the team would have argued the point in a slide deck. Instead they open a trial store, scaffold a Hydrogen project, and deploy to Oxygen in an afternoon.

They rebuild one collection template with real product data and measure it. Server response on that template comes back at roughly 210 ms from the edge, against 780 ms on the current theme under the same conditions. That single measured figure does more for the business case than a month of discussion, and it cost one developer day on a store that is not yet paying for anything.

Implementation checklist

  1. Create a dedicated trial store for the evaluation and keep it separate from any production store.
  2. Scaffold the Hydrogen project and link it to the trial store with Shopify CLI.
  3. Deploy to Oxygen and confirm the deployment URL resolves after store login.
  4. Rebuild one or two representative templates with real catalogue data, not placeholder content.
  5. Record baseline metrics: time to first byte, cache hit behaviour, and page weight on those templates.
  6. Identify which QA steps require anonymous access and schedule a paid plan before you reach them.
  7. Document environment variables and secrets so the pipeline transfers to production without rework.

FAQ

Q: Does this change how Oxygen is billed on a paid plan?

A: No. The change concerns eligibility to deploy. Paid plan behaviour, including public environments, is unchanged.

Q: Can we share a trial Oxygen URL with an external stakeholder?

A: Only if they can log in to the store. Trial plan stores have no public environments, so deployment URLs are always login gated.

Resources

Shopify documentation: Hydrogen supported plans.

Need guidance? Talk to Makro.