Oxygen: The Hosting Layer Built for Hydrogen Storefronts
Earlier this year, Shopify introduced Hydrogen, a React-based framework for building custom storefronts. Oxygen is its counterpart: the hosting platform designed specifically to deploy and serve those storefronts. Where Hydrogen made bold bets on technologies like React Server Components, Oxygen focuses on what happens after the code is written—getting storefronts online, keeping them fast globally, and integrating them cleanly with the Shopify ecosystem without requiring merchants to assemble third-party hosting infrastructure.
Oxygen sits between Shopify’s first-party services—the CDN, Admin API, and identity management—and third-party infrastructure from GitHub, Cloudflare, and Grafana. That collection is bound together by Oxygen-scoped services that handle developer tooling and observability.
Integrated by Design
The key differentiator for Oxygen is not raw hosting capability but integration with Shopify. The Hydrogen sales channel serves as the connector between the storefront framework, the hosting layer, and the shop admin. Through this channel, merchants create and manage custom storefronts, link them to administrative functions, and connect them to Oxygen. It follows Shopify’s standard Rails and React stack with the Polaris design system.
This integration extends to the request path. When a buyer hits a Hydrogen storefront hosted at myshop.com, a Gateway Worker running on Cloudflare receives the request. That worker validates authorization for both the shop and the specific storefront version before routing to a Storefront Worker running the hydrogen code. Worker chaining is enabled by Cloudflare’s Dynamic Dispatch API from its Workers for Platforms offering.
Reuse Over Reinvention
Shopify had a genuine choice: build its own infrastructure layer, control plane, and V8 isolates, or adopt an existing edge platform. The company briefly pursued a proprietary approach and found it workable. Ultimately, though, it chose Cloudflare’s worker infrastructure. The reasoning was straightforward—Cloudflare’s battle-hardened edge distribution guarantees storefront access within milliseconds globally, and adopting it removed significant upfront complexity around scale and security.
That decision let the team move faster and validate assumptions against real merchant demand. It also leaves room to revisit a proprietary runtime later if the business case supports it.
Rather than developing runtime infrastructure in isolation, Shopify worked with Cloudflare, Vercel, Deno, and others to establish WinterCG, a JavaScript runtimes community group. Shopify uses and contributes to Workers for Platforms with direct feedback loops to Cloudflare, treating the ecosystem as something to shape collectively rather than consume passively.
Developer Experience With Visibility
Oxygen is developer-facing software, so experience matters beyond deployment mechanics. While the platform manages infrastructure and distribution, it also surfaces runtime logs and metrics through an observability dashboard in the Hydrogen channel. Developers can troubleshoot production issues and track performance trends without leaving the Shopify admin.
The observability stack is distinctly different from Shopify’s internal tooling. Oxygen runs Grafana for dashboards and alerting, Cortex for metrics, Loki for logs, and Tempo for tracing. A Trace Worker on Cloudflare attaches to Storefront Workers to capture logging and metrics data, forwarding it to the Grafana stack. The Oxygen Observability Service pulls from Loki and Cortex on demand when the Hydrogen channel requests data.
That tooling choice served two purposes. Oxygen acted as a test bed for evaluating these tools at Shopify scale. And the external-facing metrics differ fundamentally from internal Shopify metrics, so a clean separation kept workloads from interfering while allowing merchants to connect their own monitoring tools if they wanted.
Production Use and Roadmap
Oxygen is in production with Allbirds, Shopify Supply, Shopify Hardware, and Denim Tears. It became generally available to Plus merchants in June 2022.
Near-term plans include composable, plug-and-play usage patterns and deeper development insights earlier in the lifecycle to shorten feedback loops. Longer-term, the team wants to reduce the number of surfaces developers must interact with, extend command-line control, and streamline Oxygen’s tools with the broader Shopify developer toolkit.
