Until now, Oxygen hosting required a paid plan. Going forward, you can deploy a Hydrogen storefront to Oxygen from a development store. Note that development stores have no public environment, so viewing the deployment URL always requires a store login.
Oxygen hosting required a paid plan. With only a development store, you couldn't try production-grade hosting for Hydrogen.
You can deploy from a development store to Oxygen, so you can validate the full stack including real hosting before signing up for a plan.
| Item | Previously | After this update |
|---|---|---|
| Deploying to Oxygen | Required a paid plan | Also possible from a development store |
| What you need to test | A store on a paid plan | development store |
| public environment | — (not stated in the article) | Not included on development stores |
| Viewing the deployment URL | — (not stated in the article) | On a development store,a store login is always required |
| Details on supported plans | Points you to the "supported plans" page. Specific plan names arenot stated | |
A public URL anyone can open without logging in. Just send the link to a client or an external reviewer and they can view it.The article mentions it by contrast, as something development stores don't include
A deployment URL is generated, but opening it requires logging in to the store every time.This means whoever you share it with must already have access to the store.
It's a short changelog, so here's what's missing from it among the things you'd need for a practical decision. The following areitems to confirm in the official docs rather than guess at.
The post only says to "see supported plans." It never states which plans qualify.
No mention of whether Oxygen usage on development stores is capped in any way.
No explanation of what's involved in switching from a development store to a paid-plan store.
Nothing about behavioral differences with the Hydrogen CLI or GitHub-integrated deploys.
No mention of whether you can point your own domain at a development store deployment.
It doesn't say whether stores you've already created can use this right away.
Validating a Hydrogen + Oxygen setup no longer requires the paid plan it used to. You can separate the technical validation phase from the contract phase.
Deployment URLs on development storesalways require a login. Review workflows and automated checks that assume a public environment can't be carried over as-is.
The post only points you to "supported plans." The specific plan requirements aren't stated. Verify them in the official docs before you quote anything.
Instead of a local dev server, you can check actual Oxygen behavior on a development store. Problems caused by local-vs-production differences surface earlier.
All the changelog actually states is"you can deploy from a development store"and"there is no public environment"— just those two points. Resource limits, billing, custom domains, and the path to production are allnot documented. Confirm them before they go into a proposal.